[00:10] <robru> why :sobs:
[08:29] <popey> sil2100: would you mind if I added to https://wiki.ubuntu.com/Touch/ReleaseNotes/OTA-11 "Wireless display support (aethercast)"  the text " - turbo [Meizu Pro 5] only for now"  ?
[08:35] <popey> sil2100: also, I heard we were going to land aethercast in the M10, but that hasn't happened for OTA-11, right? (cc morphis)
[08:35] <morphis> popey: yes
[08:35] <morphis> popey: its planed for OTA 12
[08:35] <popey> ok
[08:35] <morphis> popey: but it could be that you can enable it manually
[08:36] <morphis> abeato: did you merge all changes for aethercast on M10 into OTA 11 on the device tarball side?
[08:36] <popey> morphis: how? from the command line?
[08:37] <morphis> popey: yes
[08:37] <popey> i have rc-proposed on my m10 and the system settings option doesn't allow wireless display
[08:37] <Saviq> popey, aethercastctl in terminal
[08:37] <morphis> popey: setprop ubuntu.widi.supported 1
[08:37] <Saviq> or that ;)
[08:37] <morphis> and restart settings
[08:38] <morphis> popey: or yeah, aethercastctl on the terminal is a way too :-)
[08:38] <morphis> popey: but its not very stable if it works
[08:38] <morphis> also a lot slower than on turbo
[08:38] <abeato> morphis, all there, but I reverted the property used to show the option in system settings
[08:39] <morphis> abeato: ok
[08:39] <popey> ok
[08:39] <morphis> popey: do you already saw my answer on https://bugs.launchpad.net/aethercast/+bug/1585534 ?
[08:40] <popey> morphis: yeah, will try and reproduce later today and gather that data
[08:40] <morphis> popey: thanks
[08:41] <popey> do i have to run aethercastctl as root?
[08:42] <popey> "Failed to scan:GDBus.Error.org.aethercast.Error.NotReady: Not ready" morphis
[08:42] <morphis> popey: no, as normal user
[08:42] <morphis> but "enable" first
[08:43] <popey> oh
[10:20] <Saviq> sil2100, hey, did you see bug #1586541 ? looks like the lttng backport wasn't complete
[10:28] <sil2100> Saviq: hey! I'll take a look, I basically only backported the upstream version of ust - I guess we need to port a bit more
[10:28] <Saviq> sil2100, yeah, packaging could use some love it seems
[10:29] <sil2100> I guess it's as tsdgeos mentioned, ltt-control needs back-porting as well, this could have been a bit more obvious that the two are no longer compatible
[11:01] <Saviq> trainguards, can you please add cimi to ~ci-train-users? thanks
[11:01] <Mirv> Saviq: ok
[11:01] <Mirv> Saviq: he is already
[11:01] <Saviq> Mirv, oh
[11:02] <Mirv> Saviq: since Feb
[11:02]  * Saviq couldn't find him
[11:02] <Mirv> https://launchpad.net/~ci-train-users/+members
[11:02] <Saviq> cimi, you can make a silo yourself, then
[11:02] <Saviq> Mirv, yes, sorry, my eyes playing tricks on me
[15:10] <dbarth> rvr: i approved the merge proposals that were blocking those 2 silos
[15:12] <rvr> dbarth: Great, unblocking
[15:44] <kdub> so, for the mir landing (silo 69), should I switch to triple landing? or still xenial + v-o?
[15:51] <Saviq> kdub, yes, everything should triple-land by now
[15:52] <Saviq> rvr, hey, any update on the unity8 landing?
[15:53] <kdub> Saviq, thanks, will transition to triple landing
[15:53] <rvr> Saviq: Testing :)
[15:54] <Saviq> rvr, ack :)
[16:38] <rvr> ltinkl: ping
[16:59] <ltinkl> rvr, pong
[17:00] <rvr> ltinkl: Hi
[17:00] <rvr> ltinkl: I'm checking https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1581498
[17:00] <ltinkl> rvr, yup, any prob?
[17:00] <rvr> ltinkl: Do you know how can those notifications be triggered from command line?
[17:01] <ltinkl> rvr, hmmpf, maybe there's a way, but I tested with the SIM PIN unlock screen + USB debugging prompt
[17:03] <Saviq> rvr, you can install python-notify and use those examples https://bazaar.launchpad.net/~unity-api-team/unity-notifications/trunk/files/head:/examples/
[17:03] <Saviq> ltinkl, for reference ↑
[17:04] <ltinkl> Saviq, rvr: yup, and using UT Tweak Tool from Open Store, you can re-enable the USB debugging promtp
[17:05] <ltinkl> rvr, Tweak Tool -> System -> ADB settings
[17:05] <rvr> ltinkl: Let me see
[17:15] <rvr> ltinkl: Thanks, UT Tweak did the trick
[17:17] <ltinkl> rvr, when testing the fullscreen notifications (actually just the SIM PIN dialog), you should see the other (USB) notification go under it
[17:19] <rvr> ltinkl: Yeah, I can't see the USB dialog
[17:19] <ltinkl> rvr, you should see it once you dismiss the SIM dialog
[17:19] <rvr> ltinkl: Right
[17:19] <ltinkl> rvr, good :)
[17:19] <rvr> I took a look to the screenshots, and seemed fixed :)
[18:42] <Saviq> rvr, so no verdict on unity8 silo today?
[21:07] <robru> yep, get your builds done now, train is going offline at UTC 1, that's 4 hours from now, for a big rollout.
[21:15]  * mterry hugs robru for comment support
[21:28] <Saviq> robru, looks like the train should look at response code... https://requests.ci-train.ubuntu.com/#/ticket/1426
[21:29] <robru> Saviq: it is correctly noticing the http request has failed and is saving the error message to the ticket, the issue is just that it's a big html dump in a text field. I'll have to clean that up
[21:31] <Saviq> robru, right, I meant that maybe it should ignore the err and just say that it was 503
[21:31] <Saviq> ?
[21:32] <robru> Saviq: yeah. Can you file a bug? I'm gearing up for a huge rollout
[21:33] <Saviq> robru, ack, doing
[21:34] <robru> Saviq: thanks
[21:36] <Saviq> robru, bug #1587651
[21:36] <robru> Thanks