[00:08] <mariogrip> boiko: ping
[00:10] <boiko> mariogrip: pong
[00:11] <mariogrip> boiko: Hey, could you point me in the right direction, i'm trying to debug a problem with incoming calls not showing notification/ringing on Nexus 5 and Fairphone 2 ports.
[00:12] <boiko> mariogrip: sure, are you familiar with dbus-monitor and its output?
[00:12] <mariogrip> boiko: yes
[00:13] <boiko> mariogrip: ok, so first thing we can check that ofono is actually receiving and notifying the calls
[00:13] <boiko> mariogrip: dbus-monitor --system
[00:13] <boiko> mariogrip: let me find here what to look for in the output, just a second
[00:14] <mariogrip> got this: dest=(null destination) serial=673 path=/ril_0; interface=org.ofono.VoiceCallManager; member=CallAdded
[00:15] <mariogrip> http://paste.ubuntu.com/23736489/
[00:15] <mariogrip> boiko: ^
[00:15] <boiko> mariogrip: yep, so from ofono's point of view, all good
[00:15] <boiko> mariogrip: are you able to make calls from the phone?
[00:16] <mariogrip> boiko: yes
[00:16] <mariogrip> boiko: and also too add, it shows missed calls when i hang up
[00:16] <boiko> mariogrip: ok, so let's try now to collect some debug from dbus-monitor in the session bus
[00:17] <boiko> mariogrip: I'm interested in org.freedesktop.Notifications particularly if a Notify() method is called
[00:18] <mariogrip> boiko: no, nothing from org.freedesktop.Notifications http://paste.ubuntu.com/23736496/
[00:24] <boiko> mariogrip: oh, that one seems to be running on the system bus
[00:24] <boiko> mariogrip: is it?
[00:25] <boiko> mariogrip: (guessing as I see ofono stuff in there)
[00:25] <mariogrip> boiko: yes this was output of dbus-monitor --system yeah
[00:25] <boiko> mariogrip: dbus-monitor --session
[00:25] <boiko> mariogrip: ok, so the notification thing is on the session one, can you please run dbus-monitor --session?
[00:27] <mariogrip> boiko: here: http://paste.ubuntu.com/23736533/
[00:28] <boiko> mariogrip: is telephony-service-approver running there?
[00:29] <boiko> mariogrip: if not, can you try running it manually before receiving the call?
[00:29] <mariogrip> boiko: no it was not running, will try that
[00:34] <mariogrip> boiko: http://paste.ubuntu.com/23736552/ with that running
[00:34] <mariogrip> boiko: telephony-service-approver output this: USSDManager: Failed to connect signals
[00:35] <boiko> mariogrip: only that in the output? and still no notifications?
[00:36] <mariogrip> boiko: and Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0', still no org.freedesktop.Notifications
[00:37] <boiko> mariogrip: is mission-control-5 running?
[00:38] <mariogrip> yes pidof /usr/lib/telepathy/mission-control-5: 10094 9964 9289 7540 2340
[00:39] <mariogrip> boiko: ^
[00:40] <boiko> mariogrip: all those instances running as the same user?
[00:41] <mariogrip> boiko: jep all under phablet user
[00:42] <boiko> mariogrip: that's curious, there should only be one of that running
[00:42] <boiko> mariogrip: just as a test, can you kill them all and run mc-tool list ?
[00:43] <mariogrip> boiko: that ouputs ofono/ofono/account0
[00:44] <boiko> mariogrip: there is only one instance of mission-control-5 now, right?
[00:44] <mariogrip> boiko: yes, but there is many of telephony-service-* and telepathy-ofono
[00:45] <mariogrip> boiko: http://paste.ubuntu.com/23736589/
[00:46] <boiko> mariogrip: ugh, really?
[00:46] <boiko> mariogrip: did you build telephony-service, etc locally?
[00:47] <mariogrip> boiko: no, this is from system-server.ubuntu.com
[00:56] <boiko> mariogrip: ok, just asking cause all those instances might have been caused by tests ran at build time
[00:56] <boiko> mariogrip: so, you have multiple instances of telepathy-ofono too?
[00:56] <mariogrip> boiko: yes, did a reboot, not i have one of each
[00:57] <mariogrip> now*
[00:58] <boiko> mariogrip: ok, can you run telephony-service-approver by hand now and get the output of dbus-monitor --session?
[01:02] <mariogrip> boiko: what? now for some reason nothing comes out of dbus-monitor --session
[01:04] <boiko> mariogrip: that's weird, maybe that explains the multiple instances of the telepathy components (a problem with the session bus setup)?
[01:12] <mariogrip> boiko: yeah, found the problem, since im using adb with root i had to su my way into phablet and that messed with en dbus envs
[01:13] <mariogrip> boiko: now ran this from the terminal app to make sure its correct: http://paste.ubuntu.com/23736678/
[01:13] <boiko> mariogrip: ah ok
[01:13] <mariogrip> boiko: but still no org.freedesktop.Notifications
[01:13] <boiko> mariogrip: is telephony-service-approver running?
[01:14] <mariogrip> boiko: yes
[01:14] <boiko> mariogrip: running on the same env as the rest of telepathy
[01:15] <mariogrip> boiko: yes that got started at boot so that should be correct
[01:16] <boiko> mariogrip: for some reason mission-control-5 is not asking telephony-service-approver to dispatch the call
[01:16] <boiko> mariogrip: that would be a AddDispatchOperation entry in the dbus-monitor logs
[01:16] <boiko> mariogrip: let me remember how to get mission-control logs
[01:24] <mariogrip> boiko:  MC_DEBUG=1 maybe?
[01:24] <boiko> mariogrip: no, there is a dbus call to get the logs IIRC
[01:25] <mariogrip> oh ok
[01:25] <boiko> mariogrip: qdbus org.freedesktop.Telepathy.MissionControl5 /org/freedesktop/Telepathy/debug org.freedesktop.Telepathy.Debug.GetMessages
[01:25] <boiko> mariogrip: you might need to install qdbus-qt5
[01:35] <mariogrip> boiko: this is what i got out of that http://paste.ubuntu.com/23736752/
[01:36] <mariogrip> boiko: "mcd", 5, "add_dispatch_operation_cb: AddDispatchOperation /org/freedesktop/Telepathy/DispatchOperation/do0 (0x17150a0) on approver /org/freedesktop/Telepathy/Client/TelephonyServiceApprover failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the
[01:36] <mariogrip> reply timeout expired, or the network connection wa
[01:38] <boiko> mariogrip: yep, that explains why you are not getting the dialog, telephony-service-approver is not replying, but it should have listed the call on dbus-monitor though
[01:38] <boiko> mariogrip: I wonder if it might be an apparmor denial
[01:39] <mariogrip> i can try disabling apparmor
[01:47] <mariogrip> boiko: tried disabling apparmor, but now it does not even show missed calls after i hang up.
[01:49] <mariogrip> boiko: can we continue tomorrow? i have to go to bed. Thanks you so much for your help so far :)
[01:50] <boiko> mariogrip: good idea, it's getting late here too
[01:51] <boiko> mariogrip: ok, ping me tomorrow so that we can continue
[01:51] <mariogrip> boiko: Thanks :) I'll ping you tomorrow, see ya!
[01:51] <boiko> see you!
[09:05] <mariogrip> ogra_: do you know how i can set an apparmor profile to complain mode?
[09:08] <mariogrip> aa-complain does not seem to work on ubuntu touch
[15:24] <Taunka> hello!
[15:24] <Taunka> Can someone tell me please if is there any live image for Ubuntu touch please?
[15:40] <Taunka> Hi please?
[15:43] <dobey> !devices | Taunka
[15:43] <ubot5`> Taunka: You can find the full list of devices, official images, community images, and works in progress at https://wiki.ubuntu.com/Touch/Devices
[15:44] <Taunka> Hi sir
[15:45] <Taunka> I just want to put a live in my usb drive
[15:45] <Taunka> to test it and see if I can install it
[15:45] <Taunka> nothing more
[15:49] <Taunka> Someone, please?
[15:49] <k1l_> so you mean unity8 and mir on a pc?
[15:50] <k1l_> https://wiki.ubuntu.com/Unity8Desktop
[15:53] <Taunka> I don't know k1l_
[15:54] <Taunka> I just have a 2in1 computer/tablet
[15:54] <Taunka> And I hwant to see if I can use touch there
[15:54] <Taunka> Very confusing
[15:54] <Taunka> I always used ubuntu but this time is getting very hard
[15:54] <Taunka> I can't find a live image!
[15:56] <dobey> Taunka: there is no such live image
[15:56] <dobey> Taunka: if you have a PC you just use the standard ubuntu ISO
[15:56] <dobey> Taunka: if it's an android based tablet, it needs custom image built for the device
[15:56] <Taunka> dobey: this laptop/tablet has android and windows 10
[15:57] <Taunka> What do I do
[15:57] <Taunka> Please
[15:57] <dobey> i don't know. if you can boot an ISO from a USB, then grab the standard ubuntu ISO and write it to a USB and then boot that
[15:58] <Taunka> yes I can
[15:58] <Taunka> but that will be just Ubuntu
[15:58] <Taunka> not touch
[15:59] <dobey> they are the same thing. you just have to grab the 16.10 ISO and run the Unity8 session
[15:59] <Taunka> I have to install Unitiy8 first with apt-get
[15:59] <Taunka> then will ahve Unity8 session?
[16:00] <dobey> yes
[16:01] <dobey> it's going to be a little different from what is currently on actual phone/tablet images, but the overall experience is the same
[16:01] <Taunka> ok very good help dobey thank you
[16:01] <Taunka> will try
[16:09] <Dev^Null4> hey all trying to flash a htc desire and I am getting the following message Device a11_ul not found on server what can I do..
[16:11] <dobey> Dev^Null4: there's no port for that on the server
[20:35] <mariogrip> boiko: ping
[20:36] <boiko> mariogrip: pong
[20:36] <mariogrip> boiko: Do you have time to debug some more?
[20:36] <boiko> mariogrip: yep
[20:37] <mariogrip> boiko: I tried setting mc5 in apparmor complain mode, but there is no different
[20:37] <boiko> mariogrip: no denial messages in logs?
[20:37] <mariogrip> boiko: no
[20:38] <mariogrip> boiko: nothing at all
[20:38] <boiko> mariogrip: now that's weird
[20:43] <mariogrip> boiko: this is the only denial: apparmor="DENIED" operation="open" profile="/usr/bin/media-hub-server"
[20:47] <boiko> mariogrip: so, the only explanation would be that telephony-service-approver is stuck for some reason, can you gdb it, and print a backtrace a couple seconds before you place the call?
[20:47] <mariogrip> boiko: and its really weird that this is an issue on both nexus 5 (this device have worked before) and fairphone 2
[20:47] <mariogrip> boiko: will try that
[20:48] <boiko> mariogrip: are you using rc-proposed?
[20:48] <mariogrip> boiko: yes
[20:48] <mariogrip> same happens on stable
[20:48] <dobey> well no more weird that photo sharing was only not working on nexus 5 before
[20:49] <mariogrip> dobey: yeah, but the telephone did get incoming calls right
[20:49] <dobey> well, now that you have it running on android 5, those two things have swapped places :)
[20:50] <mariogrip> dobey: but android should not have anything to do with it when ofono is working correctly....
[20:51] <dobey> well android should have absolutely nothing to do with thumbnailer and photo sharing, either :)
[20:51] <mariogrip> dobey: have you tried the 4.4 version recently? does that work?
[20:52] <mariogrip> dobey: that i blame apparmor for
[20:52] <dobey> no, i've been using cyanogenmod for a while now
[20:52] <mariogrip> dobey: oh ok
[20:52] <mariogrip> dobey: well cm is dead now :(
[20:53] <dobey> well, the services are dead. but i think people still do ports, you just have to flash manually to upgrade
[20:54] <mariogrip> its all http://lineageos.org/ now, CM wont even get updates at all so
[20:57] <dobey> well, not like i got system updates frequently anyway
[20:59] <dobey> and there's some stuff i needed to use which only works on android, and i didn't want to run stock "put all your stuff on google's servers" stuff
[21:00] <mariogrip> yeah, we need more apps
[21:01] <dobey> well, not just apps. but yeah
[21:02] <dobey> need working and reliable system and hardware too
[21:04] <mariogrip> system and hardware is getting there
[21:05] <mariogrip> boiko: you talked about Notify() but who should be the sender for that? is that *-approver
[21:06] <boiko> mariogrip: yep, it is the approver
[21:06] <mariogrip> boiko: ok will try hooking up gdb
[21:08] <dobey> hopefully we can get working snap based device images soon.
[21:09] <boiko> mariogrip: I'll go for dinner, will be back in ~1 hour
[21:09] <mariogrip> boiko: ack
[21:11] <mariogrip> dobey: humm, seems like ubports is not going the snap way tho, we will probobly go our own way with some inspiration for sailfish. we will support snap apps.
[21:11] <mariogrip> snap will be "too hard" at this point
[21:11] <dobey> too hard?
[21:11] <mariogrip> but at a later point we probobly will
[21:13] <mariogrip> First we need to see who canonical does this with there devices before we deside, but looking at iot side it seems to be a mess with android
[21:14] <mariogrip> and also if we go the mer/sailfish way we can work together with them on hardware enablement
[21:15] <dobey> i'd expect there will be a kernel/android snap, core snap, u8 snap, and other snaps on top