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