[05:12] <Mirv> mzanetti: you're making me into a framebuffer driver? :)
[05:14] <Mirv> I for one will be the first one to use mirvfb
[08:21] <mzanetti> Mirv: haha
[08:36] <tsdgeos> Saviq: so cleanup is gone, only clean-to-trunk as of now, right?
[09:01] <tsdgeos> meh, the autopilot tests are still too unstable :/
[09:08] <didrocks> Saviq: hey, are you going to implement Ricardo's fix or do you expect a fix in qmenumodel?
[09:22] <Cimi> tsdgeos, yeah
[09:22] <Cimi> tsdgeos, saw loads of failures on the isCurrent and on the index
[09:22] <Cimi> tsdgeos, will they be fixed with new tabs?
[09:23] <tsdgeos> has nothing to do with tabs
[09:23] <tsdgeos> MacSlow: ping
[09:24] <tsdgeos> Cimi: i have no idea why they showed up now since nothing changed in there
[09:24] <Cimi> tsdgeos, so they might be races
[09:24] <tsdgeos> yes
[09:24] <tsdgeos> same as for unlocking the greeter
[09:25] <tsdgeos> if you look at the video failure
[09:25] <MacSlow> tsdgeos, what's up
[09:25] <tsdgeos> it tries to unlock the greeter what seems to be a few milliseconds before it's there
[09:25] <tsdgeos> MacSlow: you gave me a unity-notifications thing to review yesterday that says "better with this MR", but that MR is not yet approved, what do you want me to do
[09:25] <tsdgeos> ?
[09:26] <MacSlow> tsdgeos, that would be nice *very.broad.grin*
[09:27] <tsdgeos> confused :D
[09:28] <tsdgeos> what me to review+approve? or wait?
[09:28] <MacSlow> tsdgeos, I asked you for this here lp:~macslow/unity-notifications/multiple-snap-decision-example right?
[09:28] <tsdgeos> yes
[09:29] <MacSlow> tsdgeos, mzanetti already did look over lp:~macslow/unity8/snap-decisions-states and commented (all issues fixed by now)
[09:29] <mzanetti> MacSlow: nope. on the list
[09:30] <MacSlow> mzanetti, well sure... I meant it's not totally fresh (like nobody took a look at it yet)
[09:30] <MacSlow> tsdgeos, then wait I guess
[09:30] <MacSlow> mzanetti, ^ ok?
[09:30] <mzanetti> oh... I read it as a question if I re-reviewed after the fixes already
[09:30] <mzanetti> so yeah. will try to get to it before your lunchtime
[09:31] <tsdgeos> ok
[09:32] <MacSlow> thx
[09:42] <Saviq> tsdgeos, yes, no cleanup
[09:43] <Saviq> didrocks, we need to chat whether we can do it lower level easily
[09:44] <didrocks> Saviq: as it's a blocker, can you get back to us quite quickly, please?
[09:44] <Saviq> didrocks, definitely
[09:44] <didrocks> thanks :)
[09:46] <Saviq> larsu, you know things about qmenumodel, don't you?
[09:46] <larsu> Saviq: not that much anymore, dednick pretty much took over
[09:47] <Saviq> larsu, yeah, but it's actually maybe more of a dbus question - https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1293478/comments/5
[09:47] <Saviq> larsu, Qt 5.2 decided that "1" is a double, not an int in QML
[09:48] <tsdgeos> Saviq: so what's in for me, anything you want me to look in the clean-to-trunk branch or go back to having a look at the split branch by mterry?
[09:49] <Saviq> larsu, we can do what Ricardo wrote there and pray that this'll work (i.e. JS respecting the type), or actually handle this lower level (now that I think of it - maybe it should simply be the sound indicator that accepts doubles?)
[09:50] <didrocks> Saviq: on other note
[09:50] <didrocks> Saviq: I don't think we should get the transition to new scope
[09:50] <didrocks> before getting a promotable image
[09:51] <Saviq> didrocks, that's ok, I expected this
[09:51] <didrocks> Saviq: can you punt them out? (we still want the other fixes for the indicator thingy)
[09:51] <Saviq> didrocks, I just wanted to get a silo, can back it out (or force unlock or something)
[09:51] <didrocks> and maybe the workaround in unity8 if the sdk team don't think it shuld be lower
[09:51] <didrocks> sure
[09:51] <larsu> Saviq: but then next time qt decides that -1 is an int again we break again?
[09:51] <didrocks> that's fine if you reconcile the conflicting silo then
[09:52] <Saviq> larsu, well, it should just accept both?
[09:52] <Saviq> didrocks, yeah, I'll take care of rebasing / merging and such
[09:53] <larsu> Saviq: action groups don't work like that. Parameters are of a fixed type, so that implementing an action doesn't involve a lot of type checking
[09:53] <larsu> Saviq: we could amend qmenumodel that it knows about the type and does the cast for us
[09:54] <Saviq> larsu, right, so that was my other idea, do you know how much work that'd be? I remember talking to dednick about this before and it seemed like a significant amount?
[09:54] <larsu> Saviq: I'd trust him on that, he did most of the action work in qmenumodel
[09:54] <larsu> Saviq: is he out of office?
[09:55] <Saviq> larsu, should be around afaict
[09:55] <Saviq> just late
[09:55] <Saviq> ok, looks like we'll get the workaround in for now
[09:56] <Saviq> didrocks, ↑
[09:57] <Saviq> tsdgeos, so, only thing would be test stability, we did go green at some point with the cleanup branch, but that doesn't seem to happen any more :/
[09:57] <tsdgeos> Saviq: ok, let me see what the clean-to-trunk results are
[09:58] <Saviq> tsdgeos, one weird thing I noticed was that "Desktop Nexus 10" tests were running a small geometry window in a few cases
[09:58] <tsdgeos> yeah
[09:58] <tsdgeos> now that you mention
[09:58] <tsdgeos> didn't realize but those videos for N10 look like regular
[09:58] <Saviq> tsdgeos, https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/3533/? seem like actual failures, although no idea how new scopes could affect it
[09:59] <Saviq> tsdgeos, and well... qmltests locking up...
[09:59] <Saviq> tsdgeos, the 90 min limit, I mean
[09:59]  * Saviq goes into meeting
[09:59] <tsdgeos> Saviq: we still don't know if they are locking up or just initial sync took ages
[10:00] <tsdgeos> and that's why they go to 90min
[10:02] <didrocks> Saviq: great!
[10:02] <didrocks> Saviq: so…
[10:02] <didrocks> bad news
[10:02] <didrocks> blame davmor2
[10:02] <didrocks> there is a crash of unity8 if you search in the music scope
[10:02] <didrocks> he's starting bisecting
[10:03] <davmor2> didrocks: it's my job to break stuff, don't blame me when I do :P
[10:05] <Saviq> tsdgeos, right, mzanetti should be able to increase that, but maybe we can find some timestamps in the log (probably not)
[10:05]  * mzanetti reads backlog
[10:05] <tsdgeos> Saviq: adding timestamps is trivial
[10:05] <mzanetti> meh... phone call.. will take a bit
[10:05] <tsdgeos> it's just a plugin
[10:06] <Saviq> sil2100, elopio, KUDOS
[10:06] <tsdgeos> we have it in kde jenkins, we just have to convince the right people to install it :D
[10:06] <davmor2> Saviq: it crashes unity8 on music and home scope, we are assuming because the home scope is also showing music
[10:06] <Saviq> tsdgeos, we tried that already, didn't we ;)
[10:07] <tsdgeos> Saviq: sure, but being repetitive sometimes has some success :D
[10:07] <Saviq> davmor2, didrocks, sounds like album art provider, then
[10:07] <Saviq> tsdgeos, file a bug with ubuntu-ci-services-itself
[10:07] <didrocks> Saviq: right
[10:08] <davmor2> Saviq: could be
[10:08] <tsdgeos> Saviq: good news, testShell just hanged in here in the same place it hangs on the CI machines
[10:10] <Saviq> tsdgeos, oh good
[10:10] <didrocks> davmor2: I don't get a crash though
[10:10] <didrocks> but as popey and you are getting it, can be the format the UK providers are sending unity8 a bitmap
[10:11] <didrocks> Saviq: FYI, popey didn't reproduce it on latest promoted image, maybe you were safe-guarded against that
[10:11] <davmor2> didrocks: how much music do you have on the device I think popey and I have over 4GB
[10:12] <didrocks> davmor2: ah, I only have the online providers
[10:13] <popey> 1.3G    /home/phablet/Music
[10:13] <davmor2> popey: so just me with over 4 GB then :)
[10:13] <Saviq> didrocks, https://bugs.launchpad.net/unity8/+bug/1268172 btw
[10:14] <didrocks> Saviq: I think you'll need davmor2's crash file?
[10:14] <Saviq> and then https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1262711
[10:14] <Saviq> didrocks, I can try and reproduce locally after adding some music to my device
[10:15] <Saviq> didrocks, we had those before, never managed to get rid of them, was hoping 5.2 would help - but maybe it did not
[10:15] <didrocks> Saviq: excuse for running your torrent! :p
[10:15] <Saviq> or it's a different one
[10:15] <didrocks> Saviq: seems to be a different one or popey has different music on the two devices
[10:15] <popey> i also have had a long standing crash when just expanding the music scope
[10:16] <Saviq> popey, yeah, look up ↑↑
[10:16] <didrocks> popey: can you try to copy your music from latest proposed to promoted?
[10:16] <davmor2> biab
[10:16] <tsdgeos> Saviq: and now it's even crashing :-S
[10:16] <popey> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1262711
[10:16] <popey> ah yes
[10:16] <didrocks> popey: if it's a dedicated music crashing it, I think unity8 is trying to teach you good music tastes :p
[10:16] <popey> didrocks: i have same music on all devices
[10:17] <didrocks> ok, so Saviq, a safeguard seems to have been removed during the transition (or other formats…)
[10:20] <Saviq> didrocks, yeah, we know it to be pretty random
[10:21] <mzanetti> re
[10:21] <mzanetti> Saviq: so, should I increase the timout for jenkins jobs?
[10:21] <davmor2> didrocks, Saviq, popey: okay so with 238(first image after popey's working one) search is working on home and music with no music on the actual device, I'm transferring music over now so I'll retry once that is done
[10:22] <Saviq> mzanetti, no, tsdgeos reproduced the failure locally
[10:22] <mzanetti> ack
[10:22] <didrocks> Saviq: I can trigger the crash as well now, tried the same configuration on latest promoted image and it wasn't the case
[10:22] <didrocks> davmor2: yeah, seems you need to transform the same music
[10:23] <tsdgeos> Saviq: i was suggested that in the future we run our processes thorugh annotate-output if we want timestamps
[10:24] <Saviq> didrocks, so Qt 5.0 vs 5.2?
[10:24] <didrocks> Saviq: that or (hopefully) one of the 2 unity8 landings
[10:24] <didrocks> which will make it way easier to corner
[10:25] <Saviq> wouldn't count on it :/
[10:27] <didrocks> Saviq: I have a regular string search failing here
[10:27] <didrocks> Saviq: I'm trying to pop out music slowly
[10:27] <didrocks> to see if I can track down to an album/music
[10:27] <Saviq> didrocks, thanks
[10:27] <didrocks> yw ;)
[10:31] <davmor2> Saviq: That's why I've started on the 5.2 image, next I'll move to the first of the unity landings
[10:31] <Saviq> davmor2, thanks
[10:35] <didrocks> Saviq: hum… can't get a nice reproducer, I will suggest that we start from the crash file rather
[10:36] <didrocks> sometimes it crashes with the same string, sometimes not
[10:43] <Saviq> didrocks, I saw recently that the 30s timeout wasn't enough... :/
[10:43] <Saviq> didrocks, at times, at least
[10:43] <didrocks> Saviq: do you want me to attach the CoreDump? There are 37 threads…
[10:43] <didrocks> Saviq: (gdb) bt full
[10:43] <didrocks> #-1 0xaf1004f8 in ?? ()
[10:43] <didrocks> No symbol table info available.
[10:43] <didrocks> warning: Unable to restore previously selected frame.
[10:43] <didrocks> doesn't seems yummy :/
[10:43] <MacSlow> mzanetti, answered your question in the MR-comment
[10:47] <tsdgeos> Saviq: so i have a fix for that lockup i think, shall i commit to clean-to-trunk?
[10:47] <Saviq> tsdgeos, yes please
[10:48] <Saviq> didrocks, try increasing the kill timeout to 60 in /usr/share/upstart/session/unity8.conf
[10:48] <Saviq> didrocks, maybe the crash is truncated again
[10:48] <tsdgeos> pushed
[10:49] <davmor2> Saviq, didrocks, popey: so 238 has the issue on home but I believe that is the expanding on the music section.  On the music scope it is finding music no issues
[10:49] <davmor2> didrocks: do you happen to know what image had the first landing on unity8 after 238?
[10:50] <didrocks> Saviq: hum, can be
[10:50] <didrocks> davmor2: hum, why do you need to upgade more, if 238 has the same issue?
[10:51] <didrocks> as you have the crash on home
[10:51] <davmor2> didrocks: 238 has the issue on home which is different it is expanding the music section which is the known bug, musci search is working fine on the music lens
[10:52] <didrocks> davmor2: are you sure you don't have the issue at all on 238?
[10:52] <didrocks> it's really random for me
[10:52] <davmor2> didrocks: ah no I do see it now
[10:53] <davmor2> didrocks: so it looks like initial search adele didn't trigger it but mea did so I'll try that again now
[10:55] <davmor2> didrocks: yeap retried mea and it died again I have a theory I am about to try it out
[10:55] <didrocks> ok
[10:55] <didrocks> davmor2: I couldn't get something tight enough to find a particular music triggering it
[10:55] <didrocks> can be the number as well
[10:57] <davmor2> didrocks: search for something in the carousel over searching something that isn't
[10:58] <davmor2> meh nope just proved that theory wrong
[10:58] <didrocks> davmor2: yeah, no :/
[10:59] <didrocks> davmor2: mind updating the bug that Saviq pointed at?
[10:59] <didrocks> Saviq: I can't make it recrash now…
[10:59] <davmor2> ah that was the mir locking up so it might be that my theory was right
[10:59] <Saviq> didrocks, after increasing the timeout? great
[11:00] <didrocks> Saviq: yeah, it's clearly the timeout increase that fixed it… hem hem :p
[11:02] <davmor2> Saviq: which of the 2 bugs do you want updating?
[11:03] <Saviq> davmor2, whichever one fits more - one is for opening preview, the other for expanding the list of music
[11:03] <Saviq> davmor2, although IIUC you're describing something completely different
[11:04]  * Saviq loves Dell... complained yesterday about my keyboard dying, have a new one in my hands already
[11:04] <davmor2> Saviq: yeah I'll open a fresh one if it turns out it linked we can always link them
[11:05] <Saviq> davmor2, indeed
[11:09] <Saviq> larsu, do you know anything about the volume indicator?
[11:10] <larsu> Saviq: yes
[11:10] <Saviq> larsu, so, I'm looking at "if you use the slider to change volume, using buttons then won't reach you 0% or 100%"
[11:11] <Saviq> larsu, it looks like it becomes 0.5 - 1 → -0.5, rejected
[11:11] <Saviq> larsu, and same at the other end
[11:12] <larsu> Saviq: interesting. Let me have a look
[11:13] <larsu> Saviq: hm, the code looks right to me. It clamps after doing the calculation
[11:14] <Saviq> larsu, on the "volume" action, too?
[11:14] <Saviq> larsu, that's what we activate with -1 / +1
[11:14] <larsu> ya
[11:15] <larsu> let me try it out
[11:15] <Saviq> larsu, you probably won't be able to due to the int vs. double issue
[11:15] <larsu> Saviq: I'm trying on the dbus interface directly
[11:15] <Saviq> larsu, ah ok
[11:17] <larsu> Saviq: works fine here
[11:17] <Saviq> larsu, ok, I'll dig more to see what's happening
[11:17] <larsu> does unity check the current value before activating the action?
[11:17] <Saviq> larsu, no
[11:17] <larsu> hm, weird
[11:17] <Saviq> larsu, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1293478/comments/7 is what Ricardo said
[11:17] <Saviq> larsu, I didn't have time to repro, so let's leave it for now
[11:18] <larsu> okay
[11:25] <tsdgeos> Saviq: the nexus10 being weird is something that happens in trunk too
[11:25] <tsdgeos> in autopilot i mean
[11:26] <tsdgeos> let me bisect
[11:26] <Saviq> tsdgeos, yeah, right, forgot to mention that I saw that outside of new scopes...
[11:28] <Saviq> didrocks, ok, added row 51 with just small fixes to unity8, can we get a silo (overriding the lock)?
[11:29] <didrocks> Saviq: giving to you even a luxury silo (number 7!)
[11:30] <didrocks> (I turned ready to yes)
[11:30] <Saviq> didrocks, right, thanks
[11:30] <Saviq> yay, I don't have to scroll 3 times to get to my silo ;P
[11:34] <tsdgeos> Saviq: weird, even going back one month in unity8 i get that bad shaped N10 :S
[11:39] <davmor2> Saviq: bug #1294605 I've added the 2 crash files I see and I'll try to get a full BT on them now if I can
[11:42] <Saviq> davmor2, you might need to increase the kill timeout in /usr/share/upstart/sessions/unity8.conf
[11:42] <Saviq> davmor2, I saw 30s not being enough
[11:42] <Saviq> tsdgeos, I'm feeling 5.2
[11:43] <Saviq> biab
[11:43] <davmor2> Saviq: will do
[11:45] <tsdgeos> Saviq: you think 5.2 is causing the sizing thing?
[11:45] <tsdgeos> may be
[11:49] <Cimi> with new js, maybe
[11:52] <Cimi> tsdgeos, what's the magic cmake declaration that puts qml files inside qtcreator project dir?
[11:52] <Cimi> I'm trying to do the same with the wizard
[11:53] <tsdgeos> Cimi: see src/CMakeLists.txt
[11:54] <davmor2> Saviq: changing the 30 to 60 makes things searchable again with no more crash
[12:07] <Saviq> davmor2, lol
[12:07] <davmor2> Saviq: home scope is searchable now too
[12:08] <Saviq> davmor2, not like that can have any impact, but didrocks reported exactly the same ;)
[12:08] <didrocks> Saviq: don't even dare propose that as a fix! :)
[12:08] <davmor2> Saviq: and if I drop down the music section that is no longer crashing either
[12:09] <Saviq> didrocks, :D
[12:09] <davmor2> Saviq: do it i dare you ;)
[12:09] <didrocks> well, actually, that can be useful for CI or other people reporting
[12:09] <didrocks> but clearly not what's going to fix it :)
[12:10] <davmor2> Saviq: I can also preview music too so fixes that also :D
[12:11] <davmor2> didrocks: but it fixes it ;)
[12:11] <didrocks> pffff :p
[12:11] <davmor2> didrocks: 3 bugs gone from one setting change it has to be a fix right :D
[12:11] <didrocks> sure sure
[12:12]  * davmor2 picks up a tissue to wipe the tears from his eyes from laughing so much :)
[12:13] <davmor2> didrocks: so now we know where the issue evolved from can I update to latest and do some daily testing, or Saviq do you need anything else?
[12:13] <Saviq> davmor2, no, thank you, we'll have to dig into that
[12:15] <davmor2> didrocks: right I'm updating to current then and starting the daily testing then
[12:28] <Saviq> larsu, can you give me a dbus-monitor command to monitor the things going back and forth between unity and the sound indicator so we can see what's going on at the slider bounds?
[12:30] <seb128> Saviq, try "gdbus monitor --session --dest com.canonical.indicator.sound --object-path /com/canonical/indicator/sound" ?
[12:31] <Saviq> seb128, thanks
[12:32] <seb128> Saviq, wait to see if that does what you want before thanking me ;-) (I didn't follow the details)
[12:32] <Saviq> seb128, that's a start :)
[12:32] <larsu> Saviq, seb128: that only gives you signals from indicator-sound
[12:32] <seb128> larsu, I was unsure if you were at lunch so I replied with what I knew :p
[12:32] <larsu> if you want method calls as well, use `dbus-monitor destination=com.canonical.indicator.sound`
[12:32] <larsu> seb128: thanks :)
[12:33] <Saviq> larsu, thanks!
[12:35] <Cimi> Saviq, will test https://code.launchpad.net/~saviq/unity8/workaround-lp1293478/+merge/211702 when CI will build the package :)
[12:35] <Saviq> Cimi, k
[12:35] <Saviq> Cimi, actually you can grab silo 007
[12:35] <Saviq> Cimi, it's there already
[12:35] <tsdgeos> Saviq: yeah, defenitely qt, want me to have a go at fixing it?
[12:36] <Saviq> tsdgeos, would rather you do the crash / lockup first
[12:36] <tsdgeos> Saviq: the qml one? that's done
[12:37] <tsdgeos> or should be
[12:37] <Saviq> tsdgeos, ah ok
[12:37] <tsdgeos> has it run again?
[12:39] <Saviq> tsdgeos, can you check the autopilot upstart tests that failed in desktop jenkins?
[12:39] <Saviq> tsdgeos, that seemed not flaky, 'cause failed on both scenarios
[12:39] <Cimi> Saviq, you mean https://launchpad.net/~ci-train-ppa-service/+archive/landing-007 ?
[12:39] <Saviq> Cimi, yes
[12:39] <tsdgeos> Saviq: do you have the url at hand?
[12:40] <Saviq> tsdgeos, https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/3533/?
[12:41] <mhr3> Saviq, were ap tests run on the new-scopes silo?
[12:41] <tsdgeos> oki, that was new-scopes right?
[12:42] <Saviq> tsdgeos, yes
[12:42] <Saviq> mhr3, they are in -ci, I didn't get around to yet
[12:43] <mhr3> Saviq, how does it look
[12:43] <Saviq> mhr3, positive
[12:43] <Saviq> mhr3, just two failures tsdgeos is looking at now, unrelated to new scopes
[12:43] <Saviq> mhr3, but we were green at some point, so we just need to get back to that
[12:44] <tsdgeos> Saviq: so these two tests fail if you don't have scopes running
[12:45] <tsdgeos> so i had the scope-registry stopped, run them -> fail
[12:45] <tsdgeos> manually started it -> works
[12:46] <tsdgeos> there's something out there that is making it not auto start the scopes i guess
[12:46] <mzanetti> anyone still has Qt 5.0 around?
[12:47] <tsdgeos> nope
[12:47] <Saviq> mzanetti, do you need it on phone or desktop?
[12:47] <mzanetti> doesn't matter
[12:47] <mzanetti> desktop more easily
[12:47] <mzanetti> something is broken in the right edge stuff which was definitely working last week
[12:47] <tsdgeos> nice, now i stopped the scope-registry and also passes ^_^
[12:47] <mzanetti> and going back revision by revision doesn't fix it
[12:48] <tsdgeos> ah no false alarm, still fails
[12:48] <tsdgeos> Saviq: so how do we make sure scope-registry is running for that test to succeed?
[12:48] <Saviq> tsdgeos, upstart should take care of that
[12:49] <Saviq> awesome, my mako just started remounting every 5 s
[12:49]  * Saviq gains a nautilus window ever 5s
[12:49] <Saviq> *every
[12:50] <Saviq> tsdgeos, if we have "restart" anywhere, we need to change it into stop/start
[12:50] <Saviq> tsdgeos, bug #1294230
[12:52] <tsdgeos> Saviq: maybe the wrong unity8.conf is being used?¿
[12:52] <Saviq> tsdgeos, weird, looking at that test it should be fine
[12:52] <Saviq> tsdgeos, there should be no "wrong unity8.conf" nowhere
[12:53] <tsdgeos> Saviq: well at least for me locally there's the system one and the one of new-scopes
[12:53] <tsdgeos> that are different
[12:54] <Saviq> tsdgeos, yes, but upstart won't use it unless you copy it to ~/.config/upstart/
[12:54] <Saviq> tsdgeos, which you probably should in your case
[12:54] <tsdgeos> Saviq: right, so is using the system one that doesn't do "emits scope-ui-starting"
[12:54] <tsdgeos> so it makes sense it fails, no?
[12:54] <Saviq> tsdgeos, but for otto this should "just happen"
[12:54] <tsdgeos> right
[12:54] <tsdgeos> otto is a different matter
[12:54] <Saviq> tsdgeos, yeah, but on otto it shouldn't matter, since the thing is installed
[12:54] <Saviq> or should be, at least
[12:55]  * Saviq reinstalled trusty yesterday with nvidia-prime... no idea how/why but (dying) battery life improved like twice...
[12:56] <tsdgeos> Saviq: other than that maybe we need to wait a bit to give time for the scopes to load
[12:56] <tsdgeos> going for lunch
[12:56] <tsdgeos> will try that later
[12:56] <Saviq> enjoy
[13:11] <mhr3> tsdgeos, yea, the timeouts to wait for scope startup are pretty low, but seems to work mostly ok
[14:03] <tsdgeos> Saviq: any idea what's this? https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/3546/console
[14:04] <tsdgeos> just general jenkins flakyness?
[14:14] <MacSlow> tsdgeos, the branch lp:~macslow/unity8/snap-decisions-states is approved, but jenkins still needs to settle... so it'll probably still take a bit before you can more easily review/test lp:~macslow/unity-notifications/multiple-snap-decision-example
[14:15] <tsdgeos> ok, thanks :)
[14:22] <tsdgeos> Saviq: you said yesterday that otto wasn't being reinstalled between runs or something? maybe that's the cause of https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/3533/ ?
[14:28] <Saviq> tsdgeos, yeah, that's just jenkins going crazy
[14:28] <Saviq> tsdgeos, that got fixed, and it wasn't otto but devices
[14:28] <tsdgeos> ah _D
[14:28] <tsdgeos> ok
[14:28] <tsdgeos> not that then
[14:56] <Saviq> rsalveti, larsu so, looking at dbus monitor the backend actually does set the volume to 0.0/1.0, it's just the slider that doesn't update: http://paste.ubuntu.com/7120192/
[14:57]  * Saviq files another bug
[14:58] <Saviq> dednick, can't assign to you: bug #1293478
[14:58] <dednick> Saviq: yeap. looking at it now
[14:59] <dednick> looks like that code was overlooked. Didnt know we still used it
[15:01] <Saviq> dednick, how long for a fix do you think? should we merge the workaround or drop it?
[15:02] <dednick> Saviq: hour or 2 probably.
[15:02] <dednick> "hopefully" . if the fix works
[15:02] <Saviq> didrocks, wdyt ↑ land unity8 workaround or wait for proper fix in qmenumodel (volume up/down)
[15:03] <Saviq> sil2100, btw, how did we not see a meaningful error message for the temp app do you think?
[15:06] <sil2100> Saviq: you mean, in the case of url-dispatcher? :)
[15:06] <Saviq> sil2100, yes
[15:06] <Saviq> sil2100, sounds like we should improve the test somewhere to get a meaningful error
[15:06] <sil2100> Saviq: I have no idea, actually once you open up the whole console log you can see the error message ther
[15:07] <Saviq> sil2100, oh
[15:07] <sil2100> Saviq: but the big console log file is for all the tests being ran on the CI infra
[15:07] <sil2100> Saviq: so it's a big big file - and I was not aware that not all stderr is not being collected
[15:08] <Saviq> sil2100, what was the actual issue? couldn't execute url-dispatcher 'cause it wasn't there or?
[15:09] <sil2100> Saviq: it was simply not there - we couldn't reproduce it locally since we were installing unity8-autopilot
[15:09] <sil2100> Saviq: so yes, in the end the infra was doing things differently - but this time not phablet-test-run was the problem, but the actual test setup ;
[15:09] <sil2100> ;/
[15:09] <Saviq> sil2100, the command, you mean? so url-dispatcher-tools?
[15:09] <sil2100> Yep
[15:09] <Saviq> sil2100, so yeah, test should bail out when trying to exec it, shouldn't it...
[15:10] <sil2100> Saviq: well, the test is not written like that... it assumes it's there, and just executes it from the system shell
[15:10] <sil2100> Saviq: it assumes it's there as it's a dependency of the test package
[15:10] <Saviq> sil2100, doesn't matter, a call to a non-existent executable should raise
[15:11] <sil2100> It seems it wasn't thought that someone would actually execute the test without that - maybe we should fix that anyway
[15:11] <Saviq> sil2100, let me mention... bug #1262879 again
[15:12] <tsdgeos> Saviq: ha, -geometry applies only to qwidgets (no idea why)
[15:12] <Saviq> tsdgeos, hmm are we not parsing it explicitly? should we be?
[15:12] <tsdgeos> Saviq: we trusted Qt to do it
[15:13] <sil2100> Saviq: not sure if it should raise, as it's done by os.system()
[15:13] <Saviq> tsdgeos, sounds like a bad idea :)
[15:13] <tsdgeos> Saviq: but since there's no documentation on what the -geometry applies (or i can't find it) not sure we can blame them for changing the behaviour
[15:13] <Saviq> sil2100, probably that's the wrong thing - should use Subprocess.check_call
[15:13] <sil2100> Saviq: so it's like, executes a command, cannot find it, noop
[15:14] <Saviq> sil2100, yup, that's what I'm saying is wrong - should use check_call so that it bails out if the dispatcher fails for whatever reason
[15:14] <sil2100> Saviq: indeed - now that you mention it we should basically first check if it's there and bail out gracefully
[15:14] <sil2100> Maybe even skip the test then
[15:14] <Saviq> sil2100, no, ask for forgiveness, not permission :)
[15:14] <Saviq> sil2100, nope, it should fail
[15:15] <sil2100> ;)
[15:15] <Saviq> sil2100, or well, there's plenty of things we could do - use liburl-dispatcher or whatever, assuming there're py bindings for it
[15:15] <Saviq> sil2100, or call dbus directly
[15:15] <Saviq> whatever we do, it should fail if url-dispatcher fails
[15:15] <Saviq> I'll make it happen
[15:16] <Saviq> tsdgeos, ;)
[15:16] <sil2100> Saviq: thanks!
[15:32] <tsdgeos> Saviq: https://code.launchpad.net/~aacid/unity8/windowgeometry/+merge/211760
[15:33] <Saviq> tsdgeos, so Qt was swallowing -geometry?
[15:33] <Saviq> s/was/started/
[15:33] <Saviq> yay
[15:34] <Saviq> it's interesting that they eat args that they don't read anyway...
[15:34] <Saviq> grr
[15:35] <tsdgeos> Saviq: they read
[15:35] <Saviq> tsdgeos, just ignore ;)
[15:35] <tsdgeos> to apply later
[15:35] <tsdgeos> but the later is only in QWidget
[15:35] <Saviq> tsdgeos, yeah, understand
[15:47] <Saviq> Cimi, top-ack https://code.launchpad.net/~saviq/unity8/workaround-lp1293478/+merge/211702 ?
[15:48] <Cimi> Saviq, saw the packages, I'm upgrading the phone
[15:48] <Saviq> Cimi, thanks
[15:48] <Saviq> Cimi, verify fixes for bug #1293478 and bug #1283191 please
[15:57] <tsdgeos> mterry: does that QProcess in Upstart.cpp work? seems like it shouldn't to me
[15:57] <mterry> tsdgeos, why not?
[15:57] <tsdgeos> you're not passing arguments and environment properly
[15:57] <tsdgeos> i.e. via setArguments/setProcessEnvironment
[15:58] <tsdgeos> oh it seems you can actually pass the arguments in the start call
[15:58] <tsdgeos> i think to remember that wasn't supported
[15:59] <tsdgeos> good it works now :)
[16:00] <mterry> tsdgeos, ah.  I guess I did it the quick and simple way
[16:00] <tsdgeos> mterry: if it works, that's fine :-)
[16:01] <tsdgeos> mterry: maybe use startDetached to save some memory?
[16:01] <tsdgeos> i.e. no need to keep the QProcess around for ever if we're not going to use it, no?
[16:02] <mterry> tsdgeos, yeah I suppose
[16:03] <Saviq> dednick, NeedsFixin: https://code.launchpad.net/~nick-dedekind/unity8/lp1283191/+merge/211307/comments/499910
[16:04] <dednick> Saviq: eh?
[16:05] <dednick> serverValue = 0?
[16:05] <Saviq> Cimi, ↑
[16:05] <Saviq> dednick, volume 0?
[16:05] <dednick> Saviq: ok. sounds a bit suspicios.. will take a look
[16:06] <Saviq> dednick, no it doesn't
[16:06] <Saviq> dednick, I mean that when you use vol buttons
[16:06] <Saviq> dednick, to change the volume to 0
[16:06] <Saviq> dednick, the slider doesn't get the news
[16:06] <Saviq> dednick, 'cause serverValue goes undefined
[16:06] <Saviq> because of object && 0 || undefined [16:07] <dednick> eh...
[16:07] <Saviq> since 0 evaluates to false
[16:07] <dednick> stupid.
[16:07] <Cimi> why it does?
[16:07] <Saviq> Cimi, bool(0) is generally false, no?
[16:07] <Cimi> dednick, menuData.actionState >= 0 ?
[16:08]  * Saviq is worried this will bite us in other places where actionState is numeric
[16:08] <Cimi> Saviq, I thought it meant menuData.actionState was not null
[16:08] <Saviq> Cimi, null == 0
[16:08] <Saviq> Cimi, null !== 0
[16:09] <Saviq> Cimi, so 0 || undefined [16:09] <Saviq> Cimi, as does null || undefined
[16:09] <Saviq> Cimi, and >= 0 is bad, too, as it might be negative
[16:10] <Cimi> Saviq, negative volume?
[16:10] <Saviq> Cimi, dednick I think typeof menuData.actionState == "number"
[16:10] <Saviq> Cimi, that's not a volume widget
[16:10] <Saviq> Cimi, that's a generic slider widget
[16:10] <Cimi> ok
[16:11] <Saviq> dednick, but we need to review the factory for such quirks
[16:11] <Cimi> Saviq, null in JS is 0?
[16:11] <dednick> Saviq: yeah. why it's not working.
[16:11] <dednick> it's just because we changed 0.0 to undefined
[16:11] <Saviq> Cimi, it *is* not, it *equals*
[16:11] <Cimi> Saviq, just to avoid approving those things in future reviews
[16:11] <Cimi> but I see now
[16:12] <Saviq> Cimi, http://stackoverflow.com/questions/359494/does-it-matter-which-equals-operator-vs-i-use-in-javascript-comparisons
[16:12] <Saviq> equality vs. identity
[16:14] <Cimi> thank you
[16:14] <Cimi> I usually use [16:20] <dednick> Saviq: fied
[16:20] <dednick> *fixed
[16:20] <Saviq> dednick, thanks
[16:21] <didrocks> Saviq: unity8 for now
[16:21] <didrocks> Saviq: back from exercising :p
[16:21] <didrocks> Saviq: then going to qmenumodel
[16:21] <Saviq> didrocks, yeah, almost there, except we had a fix of the fix to get in... kicking the build now
[16:21] <didrocks> and drop the workaround
[16:21] <didrocks> ok ;)
[16:21] <didrocks> a fix to fix the fix? :p
[16:22] <Saviq> didrocks, yup
[16:22] <Saviq> dednick, can you please add tag: to the other entries in _data()
[16:22] <Saviq> dednick, and you can probably use it for the label instead of the additional label:
[16:26] <Cimi> wifi is bad on the phone
[16:26] <Cimi> when it boots it's down
[16:26] <Cimi> then I enable and it's still down even if the indicator says connected
[16:26] <Saviq> Cimi, do you have "reconnect to previous networks" enabled in wifi settings?
[16:27] <Cimi> Saviq, I had
[16:27] <dednick> Saviq: done
[16:28] <Cimi> it's just off
[16:28] <Saviq> Cimi, maybe bug #1288537
[16:28] <Cimi> says connected but it's not
[16:28] <Saviq> dednick, thanks
[16:28] <mhr3> Trevinho, i'm getting unity to hang when closing windows by opening the window spread and middle clicking, known?
[16:29] <mhr3> Trevinho, not always though
[16:30] <mhr3> Trevinho, and it does hang completely, i can move mouse and lock the screen, but that's all, ignores any other input
[16:31] <Cimi> also
[16:32] <Cimi> indicators say wifi is on, but if from indicators I click on wifi settings, it goes into system settings where I see all the wifi access points but the first wifi switch is off, might be related to that bug
[16:34] <Saviq> mhall119, I'm afraid I won't be able to attend the Engineering Live call... at least for the next 3 months, have places to be at that time :|
[16:34] <Cimi> seb128, I'm having issues with wifi, things are weird here
[16:34] <seb128> Cimi, desktop?
[16:35] <Cimi> seb128, phone
[16:35] <seb128> Cimi, talk to Wellark
[16:35] <Cimi> seb128, I can't get the phone to connect
[16:35] <mhall119> Saviq: that's okay
[16:35] <seb128> Cimi, or to cyphermox
[16:35] <Cimi> as soon as I touch I see the icon connected
[16:35] <Cimi> but nothing happens
[16:35] <Cimi> says it's ok but it's offline
[16:37] <Saviq> didrocks, do I always have to do FORCE_REBUILD if there's new commits in a branch?
[16:37] <Cimi> Saviq, I'm reflashing
[16:38] <didrocks> Saviq: no, this isn't needed, why?
[16:38] <Cimi> Saviq, give me another 30 mins
[16:38] <Saviq> didrocks, http://162.213.34.102/job/landing-007-1-build/42/console :/
[16:38] <didrocks> Saviq: did you try the two first options? :p
[16:38] <Cimi> oh wow
[16:38] <didrocks> Saviq: either use "ignore step"
[16:38] <Cimi> is trusty-proposed down now?
[16:38] <didrocks> or in packages to rebuild, set "unity8"
[16:38] <Saviq> didrocks, right, so they're somewhat ambiguous...
[16:39] <didrocks> Saviq: better wording welcomed
[16:39] <didrocks> Saviq: basically, the idea, is to avoid you to shoot on our feet
[16:39] <Saviq> didrocks, well, "FORCE_REBUILD" should do that... force rebuild, no?
[16:39] <didrocks> it happened in the past that people click "build" when they wanted to only rebuild some parts
[16:39] <didrocks> so some components
[16:39] <Saviq> didrocks, "ignore step" I don't understand at all...
[16:39] <Saviq> didrocks, which step?
[16:39] <didrocks> Saviq: the 3 steps: build, publish, m&c
[16:40] <didrocks> Saviq: so, basically, the idea is:
[16:40] <Saviq> didrocks, well, yeah, I'm trying to build, so there's no previous step...
[16:40] <didrocks> listen please :p
[16:40] <Saviq> didrocks, am, sorry
[16:40] <didrocks> 1. if you have a build succeeding, so that you don't screw your work, we prevent you from rebuilding everything
[16:40] <didrocks> -> this is a safety net for you
[16:41] <didrocks> 2. if you want to build after a successfull build everything (all components of your MP), you use "ignore step", which ignore the step checking (and yeah, I'll welcomed a new naming)
[16:41] <didrocks> 3. you can as well just want to rebuild component A and B of your set (if your set is A, B, C and D for instance)
[16:42] <didrocks> in that case you use "packages to rebuild with "A B"
[16:42] <didrocks> to only rebuild those
[16:42] <didrocks> C and D stays the same in the ppa
[16:42] <Saviq> didrocks, so "ignore step" relates to publish, too, does it?
[16:42] <Saviq> not to m&c, as that's too late, I'd think?
[16:42] <didrocks> Saviq: yeah, it says "force running this job, even if it's not the logical order"
[16:42] <didrocks> like you can force trying to publish without having a successful build
[16:43] <didrocks> and so on
[16:43] <didrocks> force rebuild, as per parameter description is only for: "Force rebuilding components associated to a MP even if there is no diff with dest or if latest version in destination archive isn't in targeted branches.
[16:43] <didrocks> "
[16:43] <Saviq> didrocks, not sure what is "diff with dest"
[16:43] <didrocks> Saviq: like you force rebuilding your component
[16:43] <didrocks> so we apt-get source from distro
[16:44] <didrocks> (if dest == distro, default)
[16:44] <Saviq> didrocks, got it
[16:44] <didrocks> and diff with your source branch
[16:44] <Saviq> didrocks, ok, I'll digest that and come back with what I think would be better
[16:44] <Saviq> didrocks, in theory I read those descriptions before, but obviously failed to understand them
[16:44] <didrocks> Saviq: yeah, I think it's this "ignore step" which isn't clear
[16:45] <Saviq> didrocks, that for sure, the description for force could probably be improved, too
[16:45] <didrocks> but yeah, so the failure if you try to rebuild a successfull build is really to protect you :)
[16:45] <Saviq> didrocks, that's fine
[16:45] <didrocks> errors like that with "oh crap" happened in the past :p
[16:45] <didrocks> Saviq: sure, always better from a fresh eye :)
[16:47] <Saviq> didrocks, only I expected it to check whether new commits happened, really
[16:48] <didrocks> Saviq: that would be nice, quite a lot of work with the current architecture though
[16:48] <Saviq> didrocks, thought so
[16:48] <didrocks> Saviq: but will worth a bug report (can probably have a look), description enhancement needs to come first though
[16:48] <didrocks> Saviq: as I need to check as well if there is new/removed MP (it's not only the commit numbers)
[16:49] <Saviq> didrocks, right, but those requires reconfiguration, does it not?
[16:49] <didrocks> Saviq: was just thinking about that, so step is back to 0
[16:49] <didrocks> (there are just numbers)
[16:49] <didrocks> and so, will work
[16:49] <didrocks> I just need to track for every MP the commit number
[16:49] <didrocks> and check that when you rerun
[16:50] <Saviq> didrocks, maybe enough to just try and merge MPs and see if anything changed? or are you not keeping the branch around?
[16:50] <didrocks> Saviq: but then, what should it rebuilt? everything or just components with new commits?
[16:50] <didrocks> like if there is an abi break, people may expect to rebuild everything :p
[16:50] <Saviq> didrocks, right
[16:51] <didrocks> Saviq: once you restart a landind for a component, I trash it
[16:51] <didrocks> but that's fixable
[16:51] <didrocks> I'm just wondering in term of "sane behavior"
[16:51] <tsdgeos> Saviq: i can reproduce unity8.shell.tests.test_emulators.GenericScopeViewEmulatorTestCase.test_open_preview failing quite reliably on the phone, but not desktop nor phone if i run it manually instead of thought autopilot
[16:51] <tsdgeos> autopilot seems to cause a higher cpu usage in unity8 than running stuff manually
[16:51] <tsdgeos> anyone feels the same?
[16:52] <Saviq> tsdgeos, well, introspection takes its toll probably
[16:52] <tsdgeos> yeah, somehow the LVWPH messes up and puts a category in the wrong place
[16:52] <tsdgeos> but only with autopilot
[16:52] <Saviq> tsdgeos, there's quite some dbus traffic
[16:52] <tsdgeos> if i use the same fake scopes and start unity8 in the phone
[16:52] <tsdgeos> it's all fine :/
[16:53] <tsdgeos> hard to debug
[16:53] <tsdgeos> given that autopilot seems to eat the unity8 output and send it to hyperspace :/
[16:53] <Saviq> tsdgeos, .cache/upstart/unity8.log
[16:53] <Saviq> tsdgeos, everything's there
[16:54] <Saviq> tsdgeos, there's a long-standing bug that ap should proxy it into stdout/stderr under -v, but didn't happen yet
[16:54] <tsdgeos> ok
[16:55] <tsdgeos> that ought to be enough to add some debugs to LVWPH and try to find out why the stuff ends up in the wrong place
[16:55]  * Saviq gtg, be back in ~3h
[16:55] <Saviq> o/
[17:01] <mterry> tsdgeos, I'm actually thinking I want to move that init start out of the plugin and into the data/unity8-greeter-wrapper file.  Will play with that
[17:01] <mterry> tsdgeos, (this is in reference to Upstart.cpp and QProcess)
[17:01] <tsdgeos> mterry: ok
[17:02] <tsdgeos> awesome, our jenkins job was killed while compiling
[17:02] <tsdgeos> https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-trusty/1430/console
[17:04] <elopio> tsdgeos, or Saviq: The demo-stuff PPA doesn't have all the packages anymore. How can I run the new-scopes branch?
[17:05] <mhr3> tsdgeos, landing-013
[17:05] <tsdgeos> elopio: regular distro packages should have all of it
[17:05] <tsdgeos> or as mhr3 says silo 13
[17:05] <mhr3> eh, elopio ^
[17:05] <tsdgeos> all of it (scopes wise (i think))
[17:06] <elopio> ok, I'll try the silo, because I'm getting the same error I was getting before I added the demo-stuff ppa.
[17:06] <elopio> thanks.
[17:06] <tsdgeos> elopio: also you may want to remove/purge the demo-stuff ppa
[17:06] <elopio> right, I'll try that too
[17:08]  * tsdgeos eods
[17:12] <kgunn> davmor2: were there 2 bugs for those "search for music" crashes ? i looked real quick in unity8 bugs but didn't see...
[17:12] <kgunn> if they are handy
[17:13] <kgunn> i can go dig if you have to dig :)
[17:13] <davmor2> kgunn: Yeah I think Saviq was having a quick look at them.  let me grab you the numbers though
[17:13] <kgunn> ta
[17:17] <davmor2> kgunn: https://launchpad.net/bugs/1294605 https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1262711
[17:19] <elopio> Saviq: I will work today on that fixture that launches a fake app, and closes it at the end.
[20:03] <Saviq> elopio, great, I never got to it today
[20:03] <Saviq> kgunn, there's one more: bug #1268172
[20:04] <Saviq> and no, I didn't have the time to even try and repro
[20:04] <elopio> Saviq: it's really simple: https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/launch_fake_app/+merge/211790
[20:04] <elopio> but I'll need a small change in autopilot to make it look good. It shouldn't receive the test case as a parameter, so it will take a little more.
[20:06]  * greyback eod
[20:06] <ted_> mterry, Is there a design for "split greeter" overall?
[20:06] <Saviq> elopio, cool
[20:06] <kgunn> my new favorite thing is flashing the phone....and checking only to realize, i didn't reboot into bootloader and its just been waiting
[20:07] <davmor2> kgunn: sadtrombone.com
[20:13] <davmor2> kgunn: my favourite one currently is forgetting to adb reboot bootloader before running a --bootstrap and then wondering why it isn't working
[20:13] <mterry> mzanetti, do you know how to convert an app url like settings:///system/bluetooth to an appid + url?
[20:15] <kgunn> davmor2: i know, its awesome
[20:17] <davmor2> kgunn: I do prefer the newer ubuntu-devices-flash over the older phablet-flash though on the whole :)
[20:18] <kgunn> then there's the class add repository, run apt update...and wonder why it no workie only to discover you forgot to port fwd the wifi
[20:25] <Saviq> mterry, you can't
[20:25] <Saviq> mterry, that's a url, hardcoded to open with the settings app
[20:26] <Saviq> mterry, why?
[20:26] <mterry> Saviq, yeah, I'm looking at url-dispatcher and looks like those special urls are all built-in there
[20:26] <mterry> Saviq, just split greeter stuff (split greeter fakes being url-dispatcher, so it can shuttle requests to session)
[20:27] <Saviq> mterry, oh, tricksies
[20:34] <Saviq> mterry, well, soon (ted_'s working on it, afaik), there will be a way to register an app for a url, but that will be per-user at least to some extent
[20:35] <mterry> Saviq, it's fine.  I'll just add some logic to unity-greeter-session-broadcast to be able to hand URLs as well as AppIds to sessions
[20:35] <ted_> mterry, Yeah, hopefully that'll land. Seems that we didn't get url-dispatcher into the touch FFE :-/
[20:35] <Saviq> mterry, maybe it should be just urls?
[20:35] <ted_> So now I'm fighting that battle.
[20:35] <Saviq> ouch
[20:35] <ted_> Seem to have progress on the idnicator-sound FFE though.
[20:35] <Saviq> mterry, appid:/// is, after all, url-dispatchable
[20:36] <mterry> ted_, do you want me to change UGSB to use URLs all the time or to handle both URLs and AppIds?
[20:36] <ted_> Uhm, good question.
[20:36] <mterry> Saviq, fair
[20:36] <ted_> I guess the question would be how the launcher works.
[20:36] <ted_> I didn't think it sent URLs
[20:37] <ted_> But if it's fine with it, I'm fine with just doing URLs.
[20:37] <ted_> We can also drop the Upstart job using the dbus bridge, because I'm pretty sure we can't do that in systemd.
[20:37] <ted_> It was on my TODO list to figure out for the migration.
[20:37] <mterry> ted_, launcher sends AppID, but I can change it to put appid:: in front
[20:38] <mterry> ted_, let's do the upstart change separately
[20:38] <mterry> ted_, I don't want to bundle these
[20:38] <ted_> mterry, Well you can just have the change be to URL dispatcher to listen to the system bus.
[20:38] <mterry> ted_, fair sure
[20:38] <ted_> mterry, Then the job is obsolete
[20:39] <ted_> Which is a Good Thing™
[20:39] <mterry> ted_, I'm just saying a separate change from url stuff
[20:39] <Saviq> ted_, it does deal in urls, or at least will, when we land everything
[20:39] <Saviq> ted_, file:/// for .desktop files and appid:/// for clicks
[20:39] <Saviq> erm, make that applications:/// for .desktop files
[20:39] <ted_> Ah, cool. Sounds great.
[20:40] <ted_> mterry, Uhm, okay. I don't care how it lands. Long term the way we should go though.
[20:51] <mterry> ted_, https://code.launchpad.net/~mterry/unity-greeter-session-broadcast/urls/+merge/211823
[20:54] <ted_> mterry, We should probably change the signal/method names as well.
[20:55] <mterry> ted_, hrm, k.  to Url?
[20:55] <ted_> mterry, Yeah, be creative :-) Something not "Application Start" since that's not really what we're doing.
[21:33] <mterry> ted_, updated branch btw
[21:33] <mterry> ted_, went with amazing "StartUrl" name
[21:47]  * ted_ is in awe