[07:54] <Saviq> ltinkl, hey, can you please rebase screenshot on top of lp:~unity-team/unity8/externalMonitor
[07:55] <Saviq> and dednick, could you please rebase touch tracing on top of lp:~dandrader/qtmir/multimonitorNext
[07:56] <dednick> Saviq: ok
[08:52] <dednick> Saviq: is there a new unity-api branch?
[08:53] <dednick> Saviq: nevermind. pre-req of pre-req of pre-req...
[09:05] <dednick> Saviq: i've merged it, but i've added the pre-req at https://code.launchpad.net/~nick-dedekind/qtmir/remove-dpkg-CMAK_INSTALL_PREFIX/+merge/274222.
[09:05] <dednick> Saviq: and i've updated the landing request for that MP.
[10:17] <tsdgeos> Mirv: do you know why we have an ancient gammaray?
[10:20] <Mirv> tsdgeos: just because it has (had, not relevant anymore) ubuntu changes so it doesn't get auto-synced from Debian, and no-one has bothered updating or requesting a sync from sponsors
[10:20] <tsdgeos> :/
[10:33] <cimi> pstolowski, what do you prefer for sharing the mimetypes from the preview sharing?
[10:33] <cimi> pstolowski, like a string?
[10:38] <pstolowski> cimi, yes, string. i'm currently discussing some aspects of that with tsdgeos. i'm not thrilled by shell doing such remapping, just raising the issue
[10:38] <tsdgeos> Mirv: any way we can fix that for wily or is it too late already?
[10:40] <pstolowski> cimi, tsdgeos if content hub will never use mime types, it's pointless to do any remapping. would be good to know what future holds for c-h
[10:41] <tsdgeos> i agree
[10:41] <tsdgeos> pstolowski: personally i think it's better if the scope just gives us what the content hub uses for now and if it ever changes, well the scopes may need to do some fixing
[10:41] <tsdgeos> or in that case we may do the "fake mapping" the other way around
[10:42] <tsdgeos> for a while
[10:42] <tsdgeos> but otoh Saviq says we may use mimetypes at some point in the content-hub
[10:42] <tsdgeos> so undecided
[10:42] <tsdgeos> Saviq: do you think we should get mimetypes for now and do a giant switch to contenthub.types? looks flacky to me
[10:43] <Saviq> tsdgeos, pstolowski, let's confirm the content hub plans maybe
[10:43] <Saviq> as using mimes makes total sense to me
[10:44] <Saviq> but maybe I don't know something
[10:52] <pstolowski> tsdgeos, mapping from c-h types to mimetypes to handle 'old scopes' after c-h changes will not be possible imo. we will need to fix scopes then
[10:54] <Saviq> dednick, thanks
[10:55] <Saviq> dednick, not sure which landing req you updated though? the abandoned one? (I updated https://requests.ci-train.ubuntu.com/#/ticket/445)
[11:00] <Saviq> pstolowski, tsdgeos https://code.launchpad.net/~stolowski/unity-api/scope-activate-action/+merge/273557 will conflict with the MPs from https://requests.ci-train.ubuntu.com/#/ticket/445
[11:01] <Saviq> might wanna rebase on mousePointer
[11:01] <ltinkl> Saviq, https://code.launchpad.net/~lukas-kde/unity8/rotateScreenshots/+merge/274235 resubmitted
[11:01] <Saviq> ltinkl, ack
[11:01] <Saviq> here's hoping it's the last conflict before we can land this silo finally
[11:02] <pstolowski> Saviq, no worries, i've 3 silos in the pipeline for shell plugin, unlikely to land this week
[11:02] <Saviq> ack
[11:02] <Saviq> pstolowski, yeah, you kinda dropped silo 35 on us ;)
[11:02]  * Saviq needs to pay attention as to what's going on
[11:06] <pstolowski> Saviq, indeed... sorry about that. mzanetti knew about it
[11:06] <Saviq> nw
[11:07] <Saviq> pstolowski, truth be told the train needs to do a better job at handling conflicts
[11:08] <Saviq> I'd venture to say you should be able to declare requests as dependencies for another, which should base the changes on top of code from the other silo, add the PPA as a dependency in the downstream silo etc.
[11:09] <Saviq> we could then, in theory, have multiple silos for the same project queued one after the other
[11:10] <pstolowski> +1...
[11:10] <Saviq> I even proposed that some time in the past
[11:37] <Mirv> tsdgeos: it'd need FFE bug filed and approved before feature freeze on Thursday.. release team might have better things to do. but if you follow the devel version it can be synced as soon as wily+1 opens easily.
[12:31] <tsdgeos> Mirv: i remember our plan was to swtich to w+1 soon so i guess persoanlyy i can live with it
[12:33] <Mirv> tsdgeos: for phone certainly, yes, and if you-as-a-dev are fine with it too then there's no problem. it's rolling.
[12:34] <Mirv> Saviq: I wonder if anyone on the team has any cycles to play with Qt 5.5? or would you rather wait for 5.5.1 which will hopefully get released this week? it'd be useful to look around + run qmltests, but I'd also like to have a proper solution for bug #1493851 regarding unity8 (see last comment)
[12:34] <ubot5`> bug 1493851 in qtubuntu-media (Ubuntu) "Port to upstreamed versions of Audio Role patch" [High,In progress] https://launchpad.net/bugs/1493851
[12:56] <pmcgowan> alf, I have https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1502145 right now, anything to check?
[12:56] <ubot5`> Ubuntu bug 1502145 in unity-system-compositor (Ubuntu) "rc-proposed r140, krillin: screen does not blank after timeout expires" [Undecided,Confirmed]
[12:57] <alf> pmcgowan: Not really, I am preparing a new version of USC with more logging which will hopefully provide us with more info.
[12:57] <alf> pmcgowan: Which rc-proposed release do you have?
[12:58] <pmcgowan> alf, 136 on mx4
[12:58] <alf> pmcgowan: Also, have you noticed any pattern that could help me reproduce it, or is it completely random?
[12:58] <pmcgowan> probably fri or sat
[12:58] <pmcgowan> alf, this is the first I am seeing it
[12:58] <pmcgowan> alf, the phone has been up over 3 days I think
[12:59] <pmcgowan> alf, I changed the timeout value a couple days ago
[12:59] <pmcgowan> oh wait I had to reboot yesterday for a different issue
[13:00] <alf> pmcgowan: One thing I have no info about from previous occurences is FD status. Could you please pastebin the result 'sudo lsof -p'?
[13:01] <pmcgowan> alf, bad command?
[13:02] <Saviq> alf, IIUC https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1502145/comments/8 says there's something ("active") holding the lock
[13:02] <alf> pmcgowan: oops sorry, 'sudo lsof'
[13:02] <ubot5`> Ubuntu bug 1502145 in unity-system-compositor (Ubuntu) "rc-proposed r140, krillin: screen does not blank after timeout expires" [Undecided,Confirmed]
[13:02] <pmcgowan> got a lot of lsof: no pwd entry for UID 2000
[13:03] <pmcgowan> alf, thats a 12MB output?
[13:04] <alf> pmcgowan: right, all open files by all threads, better gzip it :)
[13:04] <kgunn> pmcgowan: does the power button toggle the screen on/off ?
[13:04] <kgunn> or stuck on?
[13:04] <Saviq> larsu, hey, is there an easy way to match :1.42 dbus name to a PID?
[13:05] <kgunn> pmcgowan: feels like we still have file handle leaks somewhere....
[13:06] <pmcgowan> kgunn, button works
[13:06] <Saviq> pmcgowan, kgunn, IIUC System State Requests:
[13:06] <Saviq>   Name: active, Owner: :1.42, State: 1
[13:07] <Saviq> means that thing requested the screen to be on... now to identify what "that thing" is
[13:07] <pmcgowan> alf, zip sent
[13:07] <Saviq> ltinkl, maybe you know how to map a dbus name to PID?
[13:08] <alf> Saviq: there is a dbus service for that, let me find the link
[13:09] <alf> Saviq: sudo dbus-send --print-reply=literal --system --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID string:":1.2"
[13:09]  * kgunn saves that in his crib sheet
[13:10] <Saviq> kgunn, can you run ↑ with :1.42
[13:10] <Saviq> pmcgowan, I meant ↑
[13:10] <Saviq> sry
[13:10] <alf> Saviq: I think you will find this is unity8 (from previous experience)
[13:11] <pmcgowan> Saviq,  uint32 1931
[13:11] <Saviq> pmcgowan, ps aux | grep 1931
[13:11] <pmcgowan> which is unity8
[13:12] <Saviq> ok let me see when do we hold that lock
[13:13] <alf> pmcgowan: Saviq: I don't think it tells us much though, because I get similar output on krillin right now (when the screen is on and not in greeter), and the screen turns off fine
[13:14] <Saviq> alf, orly
[13:14] <Saviq> I don't have it
[13:15] <alf> Saviq: ah, it's because I have an app open
[13:15] <Saviq> ah it's up when app is focused
[13:16] <alf> pmcgowan: Can you turn off the screen manually (power key) and rerun powerd-cli
[13:16] <pmcgowan> alf, none requests
[13:16] <Saviq> alf, owait, that's not a screen lock anyway, just a wakelock
[13:17] <Saviq> alf, powerd no longer handles display requests does it?
[13:17]  * Saviq can't see powerd-cli display on bright in powerd-cli list
[13:17] <Saviq> and no mention in either u-s-c or powerd logs
[13:18] <alf> pmcgowan: Saviq: Right. So I want to see if any app has requested a a keepDisplayOn from USC, but we will need the USC with enhanced logging I am preparing
[13:18] <Saviq> alf, right, but that means we can't get anything out of pmcgowan's phone atm
[13:19] <pmcgowan> so I use pretty basic apps, dialer, messaging, contacts browser authenticator
[13:19] <Saviq> alf, unless we gdb into it and dig in the data
[13:19] <pmcgowan> I dont run games or webapps
[13:19] <pmcgowan> camera
[13:19] <alf> pmcgowan: Saviq: yeah, that's what I was thinking, perhaps gdb into it and see if we can get how many keepDisplayOn requests there are
[13:20] <pmcgowan> alf, talk me through it
[13:20] <Saviq> right, powerd-cli won't help any more because it's u-s-c proxying it all
[13:21] <alf> pmcgowan: Would you be open to a reverse ssh, so I can ssh to it, or is this a private phone?
[13:21] <alf> pmcgowan: private == personal
[13:22] <pmcgowan> it is personal phone yeah
[13:22] <alf> pmcgowan: ok then, let me gdb in my own usc instance to provide accurate instructions
[13:24] <Mirv> tsdgeos: oh right regarding gammaray, at some point it seemed obvious Qt 5.5 would make it into 15.10 and therefore carry newer gammaray with it to the archives, but since that didn't happen it didn't get updated... once I had synced non-modified newer gammaray to the 5.5 PPA I didn't give a thought to it anymore.
[13:30] <Saviq> tsdgeos, can you please have a look at bug #1493851 re: unity8
[13:30] <ubot5`> bug 1493851 in qtubuntu-media (Ubuntu) "Port to upstreamed versions of Audio Role patch" [High,In progress] https://launchpad.net/bugs/1493851
[13:31] <Saviq> Mirv, when we get a fix for ↑ I can try it out on the phone and run our qml tsts
[13:31] <Saviq> +e
[13:31] <tsdgeos> Saviq: sure
[13:33] <Mirv> Saviq: thanks! note it's not being landed yet, so just for you to get a grip on how it's looking, and if you have time fix the unity8 bugs that are already filed (+ any not filed yet)
[13:33] <Saviq> yup
[13:35] <Saviq> tsdgeos, while at it (assuming you'll have Qt 5.5 installed), could you also have a look at bug #1502883 if it's an easy fix, otherwise we might find someone else to dig deeper
[13:35] <ubot5`> bug 1502883 in unity8 (Ubuntu) "Impossible to pull to refresh scopes with Qt 5.5" [High,Triaged] https://launchpad.net/bugs/1502883
[13:35] <alf> pmcgowan: ok
[13:35] <alf> pmcgowan: so first make sure you have unity-system-compositor-dbgsym installed
[13:35] <tsdgeos> Saviq: ok2
[13:37] <Saviq> pmcgowan, you'll need to add "main/debug" to /etc/apt/sources.list.d/extra-ppas.list after "main"
[13:37] <Saviq> apt/update and install what alf mentioned
[13:37] <pmcgowan> yeah its finding the wrong ersion just now
[13:37] <Saviq> pmcgowan, apt-cache policy unity-system-compositor{,-dbgsym}?
[13:38] <pmcgowan>  Candidate: 0.1.1+15.04.20150904-0ubuntu1
[13:38] <ltinkl> Saviq, update the unity-notifications leak fixes,  https://code.launchpad.net/~lukas-kde/unity-notifications/fix-1453958/+merge/274163, if you want to review that
[13:38] <pmcgowan> depends on same version of usc
[13:38] <Saviq> pmcgowan, and that's different from Installed:?
[13:39] <pmcgowan> Saviq,  unity-system-compositor-dbgsym : Depends: unity-system-compositor (= 0.1.1+15.04.20150904-0ubuntu1) but 0.1.4+15.04.20150930.1-0ubuntu1 is to be installed
[13:39] <Saviq> pmcgowan, ok you have outdated packages, how old is that image?
[13:39] <pmcgowan> Saviq, let me add what you said to the apt list
[13:39] <pmcgowan> Saviq, friday?
[13:40] <Saviq> that's weird, why would you have a u-s-c from a month ago then
[13:40] <alf> pmcgowan: Saviq: I think it's a matter of repository priorities
[13:41] <pmcgowan> Saviq, I have a new usc its not finding new dbg
[13:41] <pmcgowan>  0.1.4+15.04.20150930.1-0ubuntu1
[13:41] <pmcgowan> hmm
[13:41] <pmcgowan> oh thats fine
[13:41] <Saviq> isn't that from a silo?
[13:41] <pmcgowan> how would I know
[13:42] <Saviq> pmcgowan, paste the whole output from apt-cache policy please
[13:42] <pmcgowan> seems I installed it with dpkg hmm
[13:42] <pmcgowan> unity-system-compositor:
[13:42] <pmcgowan>   Installed: 0.1.4+15.04.20150930.1-0ubuntu1
[13:42] <pmcgowan>   Candidate: 0.1.4+15.04.20150930.1-0ubuntu1
[13:42] <pmcgowan>   Version table:
[13:42] <pmcgowan>  *** 0.1.4+15.04.20150930.1-0ubuntu1 0
[13:42] <pmcgowan>         100 /var/lib/dpkg/status
[13:42] <Saviq> pmcgowan, it just means it's no longer in any repo
[13:42] <Saviq> pmcgowan, oh ok, so u-s-c is 0930
[13:42] <Saviq> pmcgowan, just there's no dbgsym for it, yeah, add main/debug to the apt list
[13:43] <pmcgowan> ok
[13:43]  * Saviq got tricked by -dbgsym being outdated
[13:43] <Saviq> not the other way round
[13:45] <pmcgowan> installing
[13:46] <pmcgowan> alf, Saviq all set
[13:46] <Saviq> kgood, alf, all yours
[13:48] <pstolowski> cimi, hey, quick question about https://code.launchpad.net/~cimi/unity8/preview-sharing/+merge/273233
[13:49] <cimi> pstolowski, thanks
[13:49] <alf> Saviq: thanks
[13:49] <alf> pmcgowan: phablet-shell to the phone
[13:49] <pstolowski> cimi, it's not clear to me if uri can be a simple string, or if it needs to be an array even if I want to share a single uri?
[13:49] <alf> pmcgowan: (I guess you are already in)
[14:03] <cimi> pstolowski, maybe is better, no?
[14:04] <ltinkl> pstolowski, a side note, where QML expects a stringlist, you can always write a single string and it will convert it internally into the list with one item
[14:04] <dandrader> Saviq, are we landing anything before silo 22?
[14:04] <Saviq> dandrader, pstolowski is, and mir 0.17
[14:04] <Saviq> dandrader, both waiting for QA since Friday
[14:05] <dandrader> ok
[14:05] <pstolowski> ltinkl, cimi ah, cool then, i didn't know that, thanks
[14:06] <ltinkl> pstolowski, I think it's also true for (JS) arrays of strings, but you better double check :)
[14:08] <larsu> Saviq: busctl :1.42
[14:08] <Saviq> larsu, thanks :)
[14:08] <larsu> Saviq: --user for the session bus
[14:08] <Saviq> larsu, hmm unknown command
[14:09] <larsu> Saviq: oh man I'm tired. busctl status :1.42
[14:09] <Saviq> larsu, "status" works, or "list" for that matter
[14:09] <pmcgowan> Saviq, alf its the browser, must be the new play in background thing
[14:09] <Saviq> kgunn, "busctl" instead of the dbus-send :)
[14:09] <larsu> Saviq: ya. Also works the other way around - just pass a pid
[14:12] <pmcgowan> alf, seems you are off the hook, will talk to browser guys
[14:13] <alf> pmcgowan: great, I will continue on my logging improvements to make such issues easier to diagnose in the future
[14:13] <pmcgowan> alf, thanks
[14:13] <pmcgowan> alf, maybe add a dus api to query? dunno
[14:15] <alf> pmcgowan: sounds good
[14:29] <kgunn> Saviq: ack :)
[14:42] <pstolowski> cimi, approved your MP, leaving top-approval to your team
[14:45] <tsdgeos> it's weird how i change the status
[14:45] <tsdgeos> and it says "Michał Sawicz wants this branch merged"
[14:45] <tsdgeos> :D
[14:45] <pstolowski> "Albert Astals Cid (aacid): has code of mine" ? :)
[15:09] <Saviq> "Michał Sawicz has proposed merging lp:~aacid/unity8/filters into lp:unity8." HUH!?
[15:10] <Saviq> tsdgeos, ↑ ;) I think LP remembers who filed the MP in the first place, not who puts it in Needs Review, but the email scared me a little ;P
[15:11] <tsdgeos> yeah
[15:11] <tsdgeos> it's weird
[16:28] <mhall119> Saviq: is silo 22 is a good state for me to upgrade?
[16:30] <Saviq> mhall119, yes, should be good with all the latest bells'n'whistles
[16:30] <Saviq> (i.e. some minor fixes)
[16:32] <mhall119> no mir 0.17 yet?
[17:29] <davmor2> mhall119: QA is a little busy with the release
[19:49] <mhall119> bregma: if you have some way I cna test X apps on my phone, I'd like to try it out as well
[19:50] <bregma> mhall119, you could try using the -pd channel, it has some magic runes that cna be leveraged with a small blood sacrifice
[19:51] <bregma> if you have an N4 at least
[19:55] <mhall119> bregma: ubuntu-touch/rc-proposed/ubuntu-pd ?
[19:56] <bregma> mhall119, yes, that's the onw
[19:56] <bregma> *one
[19:56] <mhall119> cool, let me charge up my other N4 and I'll give it a try
[19:56]  * mhall119 goes off to try the latest silo22 builds
[20:09] <mhall119> Saviq: dandrader|afk: this mouse bug is killing the experience for me, has it been filed against Mir yet?
[20:09] <dandrader> mhall119, no, the closest thing is https://bugs.launchpad.net/bugs/1488417
[20:09] <ubot5`> Ubuntu bug 1488417 in qtmir (Ubuntu) "nexus4 window mode mouse motion bounded incorrectly with external monitor" [Medium,In progress]
[20:13] <mhall119> dandrader: hmm, that doesn't sound like the same thing
[20:14] <mhall119> sounds like the opposite, actually, that says the mouse can move beyond the screen's borders, where my problem is that the cursor won't go all the way over to the screen's left border
[20:14] <mhall119> or not reliably anyway
[20:15] <mhall119> also, clicking doesn't register when the cursor gets "stuck"
[20:15] <dandrader> mhall119, I know about the bug you're talking about
[20:15] <mhall119> it's almost like the input events are lost
[20:15] <mhall119> ok, just making sure
[20:20] <Saviq> kgunn, there are mouse fixes in Mir 0.17 right?
[20:20] <Saviq> dandrader, ltinkl found a small issue in mousePointer for unity-api and qtmir, if you're still working, could you please fix?
[20:21] <Saviq> oh
[20:21] <Saviq> you did
[20:21] <Saviq> dandrader, as you were
[20:21] <dandrader> Saviq, unity8 needed updating as well
[20:21] <Saviq> ack
[20:22] <dandrader> Saviq, I think multimonitor input will still be waky with mir 0.17....
[20:23] <Saviq> mhm
[20:24] <Saviq> ltinkl, so you can merge lp:~dandrader/qtmir/mousePointer into wheelEvent and we should be good again
[20:24] <ltinkl> Saviq, what about unity-api?
[20:25] <Saviq> ltinkl, it's fixed, you didn't have a branch for that did you?
[20:25] <dandrader> EOD
[20:25] <ltinkl> Saviq, nope
[20:25] <Saviq> ltinkl, then it's fine, dandrader fixed qtmir, unity-api and unity8
[20:25] <ltinkl> ok
[20:25] <Saviq> ltinkl, but your only conflict was in qtmir, so that's the only thing that needs merging (and I will rebuild them all when you do)
[20:25] <ltinkl> Saviq, on it
[20:30] <ltinkl> Saviq, hmm, this one conflicts again in many places and it looks like it's a step backwards
[20:30] <ltinkl> Saviq, to what it was before my first merge
[20:30] <kgunn> Saviq: there are mouse fixes in mir0.17
[20:31] <kgunn> uh...multimonitor fixes primarily
[20:31] <kgunn> so there is at least 1 lingering multimon bug i know of....but the bulk are fixed in that mir0.17 release
[20:33] <Saviq> ltinkl, ok, so we'll need to merge up the chain :/
[20:34] <Saviq> ltinkl, will let you know tomorrow then
[20:34] <ltinkl> Saviq, what about leaving it as-is and then fix it with a one liner in both unity-api and qtmir?
[20:39]  * ltinkl EOD too
[20:39] <ltinkl> cya tomorrow
[20:40] <mhall119> bregma: is there anything in the -pd channel now that isn't in the regular rc-proposed channels?
[20:40] <mhall119> something I cna play with
[20:44] <mhall119> I see some X apps, but they don't launch
[21:16] <bregma> mhall119, try installing this click upgrade onto the -pd: https://chinstrap.canonical.com/~townsend/puritine/com.ubuntu.puritine_0.2_armhf.click
[21:17] <bregma> it's not yet available in the store, these are early days
[21:17] <bregma> and it's not on the actual image, because it would blow the recovery partition during flashing