[00:12] <sgehrman> Just got 13.10.  My xmodmap file isn't working very well now.  How can I easily swap the ctrl and alt keys?
[07:00] <dandrader> thomi, ping
[08:00] <didrocks> Saviq: hey, when do you think that landing request 196 will be ready?
[08:00] <Saviq> didrocks, as soon as ogra wakes up ;)
[08:00] <Saviq> didrocks, u8 is ready
[08:00] <didrocks> veebers: hey, when do you mean to "fix AP jobs", what is it? for the smoketesting?
[08:01] <Saviq> didrocks, u-n are landing right now
[08:01] <Saviq> didrocks, so we only need u-s-touch to land
[08:01] <didrocks> Saviq: ok, do you know how this is helping AP?
[08:01] <didrocks> (like will that help the various runs when we have all tests hanging?)
[08:02] <Saviq> didrocks, yes, I've run the suite 20 times on both maguro and mako last night
[08:02] <veebers> didrocks: can you elaborate, I'm not sure I understand the question
[08:02] <Saviq> didrocks, one or two crashes on startup that I can't trace at all, but nothing hanging and such
[08:02] <didrocks> Saviq: but you never had hangs as well recently, right?
[08:03] <didrocks> veebers: I see that the latest unity8 has some "fix AP jobs" description, should wanted to know more :)
[08:03] <Saviq> didrocks, I did - u8 hangs on shutdown pretty often - tsdgeos is looking into that
[08:03] <didrocks> Saviq: ah, so maybe that's what is hanging after the first test finishes…
[08:04] <didrocks> Saviq: let's cross fingers ;) keep me posted, I'll ensure you land today
[08:04] <Saviq> didrocks, will do
[08:04] <Saviq> didrocks, it might just be that upstart is more persistent at killing stuff
[08:04] <veebers> didrocks: can you link me to where you're seeing this please?
[08:04] <Saviq> veebers, in the landing pipeline
[08:04] <didrocks> Saviq: I hope it is :)
[08:05] <Saviq> didrocks, phablet-test-run was working fine
[08:05] <Saviq> didrocks, only thing to make sure of
[08:05] <didrocks> veebers: I guess that's link to http://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/461
[08:05] <Saviq> didrocks, is "powerd-cli display on" before starting the suite
[08:05] <didrocks> Saviq: on utah? I don't at all, I always ensure that when testing manually personnaly
[08:06] <Saviq> didrocks, yeah, in automation
[08:06] <Saviq> due to bug #1233870
[08:06] <Saviq> no
[08:06] <veebers> didrocks, Saviq: ah right, that was to start launching unity with upstart while testing to sort out some issues with the keyboard etc.
[08:06] <Saviq> bug #1235000
[08:07] <tsdgeos> Saviq: tbh this one hang on shutdown looks not so "easy" to fix, i.e. the thread for driver painting is still there alive
[08:07] <tsdgeos> may me more a mir one than an unity-mir one
[08:07] <didrocks> ajmitch: I can just tell you this fix is in, but it didn't reallyhelp
[08:07] <tsdgeos> still having a more in depth look though
[08:07] <tsdgeos> greyback: did you have time to look at the fixes i made for "ctrl+c while starting" ?
[08:08] <Saviq> tsdgeos, got it
[08:08] <veebers> didrocks: I'm not sure if that answers your question; But I'm just popping out, will be back later if there is anything else
[08:08] <greyback> tsdgeos: ah no, I didn't realise it was ready
[08:08] <didrocks> veebers: ok, let's see, time to get that in anyway, I think it will be your tomorrow :)
[08:08] <tsdgeos> greyback: yep, it should fix the crashes if you ctrl+c while starting
[08:08] <greyback> tsdgeos: ok, will have a look
[08:09] <tsdgeos> greyback: then there's the hang we are getting on exit if there's something on screen animating, looking at that now, but seems to be pretty much a different thing
[08:10] <veebers> as ok, I see now didrocks. Sounds good
[08:11] <tsdgeos> veebers: do you know how do i tell autopilot to forward me the debug output of the app it's running?
[08:13] <didrocks> veebers: have a good night!
[08:13] <Saviq> tsdgeos, -v
[08:13] <Saviq> tsdgeos, autopilot run -v
[08:13] <Saviq> tsdgeos, but!
[08:14] <tsdgeos> Saviq: did not do what i expected yesterday
[08:14] <Saviq> tsdgeos, with what we have in trunk
[08:14] <Saviq> tsdgeos, ~/.cache/upstart/unity8.log
[08:14] <veebers> didrocks: will do thanks
[08:14] <tsdgeos> Saviq: ok
[08:15] <veebers> tsdgeos: yes, what Saviq said. If you use -v (or -vv) the output log should contain the stderr/stdout  of the app if the test fails
[08:15] <Saviq> veebers, that's not the case through upstart, though
[08:15] <veebers> tsdgeos: you can also use -o <filename> to save the output to a file
[08:15] <veebers> Saviq: ah I see, very good point :-\
[08:15] <Saviq> veebers, we should think about this
[08:15] <veebers> yeah, the log that Saviq pointed out is probably the best bet.
[08:15] <Saviq> veebers, generally upstart support needs building into autopilot more
[08:15] <Saviq> veebers, but, go away now, have a good night!
[08:16] <dandrader> greyback, updated https://code.launchpad.net/~dandrader/ubuntu-keyboard/osk_rotation_lp1236489/+merge/190946
[08:16] <greyback> dandrader: thank you
[08:16] <veebers> Saviq: sure. Yep and thomi has been working on some things in the next version of autopilot. So we will have a bunch of new goodness coming up
[08:16] <veebers> Saviq: heh, will do o/
[08:16] <dandrader> Saviq,  should qmlscene work?  I'm getting a seg fault when I try to run it on the device...
[08:17] <Saviq> dandrader, it should, but I've seen people saying it doesn't
[08:17] <Saviq> dandrader, let me try
[08:18] <Saviq> dandrader, you passing --desktop_file_hint?
[08:18] <dandrader> Saviq, no
[08:18] <Saviq> dandrader, you should :)
[08:18] <dandrader> Saviq, what's that about?
[08:18] <Saviq> dandrader, it's always been there :D
[08:18] <Saviq> dandrader, you need to point at a .desktop file
[08:19] <Saviq> dandrader, so that u8 can match the session to an app
[08:19] <dandrader> Saviq, so "--desktop_file_hint" is a qmlscene parameter?
[08:19] <Saviq> dandrader, no, it's a "whatever" parameter
[08:20] <veebers> oh rats, Saviq one more thing. Are there known issues with interaction between unity and maliit/osk?
[08:20] <Saviq> dandrader, it's only interpreted by the app manager
[08:20] <Saviq> veebers, I didn't get any during testing
[08:20] <veebers> for instance running the ubuntu_keyboard tests it seems that unity crashes/restarts/something. But only if I do something similar to this:
[08:20] <veebers> stop maliit-server && start maliit-server && autopilot run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTypingTests.test_can_type_string
[08:21] <Saviq> veebers, there is bug #1233245
[08:21] <Saviq> veebers, will try
[08:21] <veebers> this is after doing this (so we can introspect the keyboard): echo exec maliit-server -testability > ~/.config/upstart/maliit-server.override
[08:21] <veebers> I came across it while testing this branch: https://code.launchpad.net/~veebers/ubuntu-keyboard/restarting-maliit-for-tests/+merge/190005
[08:22] <Saviq> veebers, nothing that I know of, if you have a .crash file I could try and see
[08:22] <veebers> but even when using trunk tests and using a similar command as above (also added a sleep before starting the tests)
[08:23] <Saviq> veebers, btw just pass QT_LOAD_TESTABILITY=1 to initctl start - no need for -testability
[08:23] <veebers> Saviq: ah, right, I was using an outdated method
[08:23] <dandrader> Saviq, works now. thanks!
[08:24] <veebers> I have some stale crash files, not sure if they are interesting, will attempt to generate some new ones later on.
[08:24] <Saviq> veebers, k, o/
[08:24] <Saviq> dandrader, we'll be getting rid of that soon, when all of the apps (and app tests) are launched via upstart, which we want to be the only supported way of launching apps
[08:25] <dandrader> Saviq, so "qmlscene foo.qml" will just work then or will I have to do it?
[08:25] <dandrader> I mean, how am I going to do it
[08:25] <Saviq> dandrader, it won't, you will still need a .desktop file
[08:26] <Saviq> dandrader, and launch through upstart, something like:
[08:26] <Saviq> initctl start application APP_ID=qmlscene ARGS=/path/to/qmlfile
[08:26] <Saviq> or similar
[08:27] <dandrader> ah, ok
[08:27] <Saviq> dandrader, where qmlscene.desktop would be a generic launcher for testing purposes
[08:56] <tvoss> Saviq, https://code.launchpad.net/~thomas-voss/unity-mir/oom_adjust
[08:57] <dednick> Saviq: the datetime indicator seems to be stopping randomly. i think it's crashing, but not getting a crash report. Do we have to turn it on per process?
[08:57] <Saviq> dednick, no, if it's crashing - there should be a .crash
[08:57] <dednick> hm
[09:00] <mzanetti> Saviq: hey, expanding categories in the dash seems to animate really slow nowadays, intentionally?
[09:01] <Saviq> mzanetti, bug #1224552
[09:05] <mhr3> dednick, +1
[09:05] <mhr3> dednick, exactly what i've been seeing past week(s)
[09:05] <mzanetti> Saviq: hmm... seems to me this issue was only introduced with the branch that should fix it
[09:06] <dednick> mhr3: you mean datetime?
[09:06] <Saviq> mzanetti, not really, using duration you'll always get slow for small movement, fast for large movement
[09:06] <Saviq> mzanetti, but now the easing is wrong
[09:07] <mhr3> dednick, yep, i told you i don't see it half of the time
[09:07] <dednick> yeah
[09:07] <mhr3> dednick, also, it's using am/pm... where are we? in us? :P
[09:07] <dednick> mhr3: it using locale.
[09:08] <mhr3> dednick, what's our default locale?
[09:08] <Saviq> mhr3, en_US
[09:08] <mhr3> i see
[09:08] <Saviq> or en_EN?
[09:08] <Saviq> en_US
[09:09] <mhr3> would be nice to have a first run wizard which sets up the network, gets location, sets locale etc...
[09:09]  * mhr3 dreams
[09:10] <dednick> might be good to have a working phone first ;)
[09:10] <dednick> or at least a datetime.
[09:11] <mhr3> dednick, details
[09:26] <dednick> mhr3: if you see that datetime thing again, can you check for a crash report?
[09:26] <mhr3> dednick, i don't think i saw one... ever
[09:26] <tsdgeos> Saviq: i've bad news :/
[09:26] <dednick> mhr3: i cant seem to get it to not show up. have my phone in a reboot loop now checking for the process... but it's done it about 10 times now with no luck
[09:27] <tsdgeos> now that i've qtdeclarative with debug in the phone
[09:27] <tsdgeos> that hang points to our friend the amazing QQuickRenderThreadSingleContextWindowManager :/
[09:28] <Saviq> :|
[09:28] <tsdgeos> Saviq: is it worth compiling 5.1 and seeing if it doesn't happen there?
[09:28] <tsdgeos> i guess it's not
[09:28] <Saviq> tsdgeos, qt5-beta-proper not good?
[09:28] <tsdgeos> i mean we're not going to update because of this
[09:28] <Saviq> tsdgeos, oh yeah, we're not
[09:29] <Saviq> tsdgeos, but finding out would be good regardless
[09:29] <tsdgeos> i need more phones :
[09:29] <Saviq> tsdgeos, I know what you mean :D
[09:29] <tsdgeos> took my almost a day to get all the stuff compiled with debug in this one
[09:29] <tsdgeos> don't want to destroy it just to use the ppa
[09:29] <Saviq> tsdgeos, we should have a debug-enabled PPA
[09:29] <tsdgeos> i guess i could rsync the stuff
[09:29] <Saviq> Mirv, wdyt ↑?
[09:29] <tsdgeos> Saviq: like as compiled with CONFIG+=debug ?
[09:29] <Saviq> tsdgeos, try with qt-beta-proper - if that doesn't work - just comment on the bug and leave it
[09:29] <tsdgeos> that'd rock :D
[09:30] <Saviq> tsdgeos, yes
[09:30] <Saviq> tsdgeos, and it's easy ;)
[09:30] <tsdgeos> save me quite some time
[09:30] <tsdgeos> qtdeclarative compiles reasonably fast
[09:30] <tsdgeos> but qtbase can be a bit of a pain
[09:33] <Mirv> Saviq: the debug packages are all there in qt5-betaproper
[09:33] <Mirv> and for archive versions, ddebs.ubuntu.com
[09:33] <Saviq> Mirv, not debug packages
[09:33] <Saviq> Mirv, but built in debug mode
[09:33] <Saviq> Mirv, as in, with assertions and stuff
[09:33] <Saviq> and debug logging
[09:33] <Saviq> Mirv, basically CONFIG+=debug
[09:33] <Mirv> right, so it's not good enough then, but requires a separate debian/rules?
[09:34] <Saviq> Mirv, yeah
[09:34] <Mirv> yep, makes sense for PPA test builds if there are no downsides except for size
[09:36] <Saviq> tsdgeos, hrmpf... ideas on why I can't link http://bazaar.launchpad.net/~saviq/unity8/fix-lvwph-easing/revision/463 ?
[09:37] <Saviq> I bet it's not exported...
[09:37] <tsdgeos> most probably
[09:37] <tsdgeos> well
[09:37] <Saviq> of course it's not
[09:37] <tsdgeos> if it's installe
[09:37] <tsdgeos> should be
[09:37] <tsdgeos> that's weird
[09:38] <Saviq> tsdgeos, nope, Q_AUTOTEST_EXPORT
[09:38] <Saviq> vs. Q_QUICK_PRIVATE_EXPORT
[09:38] <tsdgeos> that in qquicksmoothedanimation_p.h ?
[09:38] <Saviq> tsdgeos, yes
[09:39] <tsdgeos> Saviq: yep
[09:39] <Saviq> grrr
[09:39] <tsdgeos> so i guess if it's us wrongly installing that in the -private package or them
[09:40] <tsdgeos> i mean, what's the point of that header being installed?
[09:40] <Saviq> tsdgeos, indeed
[09:40] <Saviq> tsdgeos, think we could make the animation a prop and pass it from QML?
[09:41] <tsdgeos> shouldn't be too hard
[09:42] <mhr3> does the update manager app actually work? everytime i run it i just get a white screen of nothingness
[09:45] <nic-doffay> mhr3, you know you're search active branch? Is it up to date with trunk atm?
[09:46] <nic-doffay> I'm back on all of that now after some more SDK stuff.
[09:46] <nic-doffay> Trying to sort out the filters branch again.
[09:46] <mhr3> nic-doffay, it was merged into trunk quite some time ago
[09:47] <mhr3> nic-doffay, but filters never needed that branch, did they?
[09:48] <Saviq> mzanetti, hrm, right, with velocity we get long categories collapsing in seconds...
[09:48] <nic-doffay> mhr3, which one did it rely on? I can't recall...
[09:50] <Saviq> mzanetti, we need a two-step animation - first collapse to "visible size" in one frame, and then collapse to the end
[09:53] <mzanetti> Saviq: yeah, something like that
[09:53]  * Saviq hacks
[09:54] <mhr3> nic-doffay, anything it did rely on should be in trunk
[09:55] <nic-doffay> mhr3, ok great, sorted then :)
[10:09] <Saviq> mzanetti, https://code.launchpad.net/~saviq/unity8/fix-lvwph-easing/+merge/191139
[10:10] <mzanetti> Saviq: should I manually merge?
[10:10] <Saviq> mzanetti, ye
[10:10] <Saviq> s
[10:11] <Saviq> mzanetti, well, or I can - gonna be easier
[10:11] <Saviq> mzanetti, you approve?
[10:11] <Saviq> mzanetti, I'm merging
[10:11] <Saviq> mzanetti, done
[10:12] <mzanetti> Saviq: ok...  just would have needed to push
[10:12] <Saviq> mzanetti, hopefully after a unity8 release we'll get to green and get autolanding again
[10:13] <mzanetti> Saviq: oh boy, this switching previews turned out more complex then expected :)
[10:13] <Saviq> mzanetti, I did expect it to be complex, did you not? ;)
[10:13] <mzanetti> not that much no...
[10:14] <mzanetti> actually it would be fairly easy if QML animations wouldn't such in some certain regard
[10:14] <mzanetti> s/such/suck/
[10:15] <Saviq> true, true
[10:33] <nic-doffay> Saviq, so the ui-tk is having some CI issues which timp is looking at. My branch won't land until that's sorted, however would you mind giving a code review of: https://code.launchpad.net/~nicolas-doffay/unity8/filter-selector/+merge/191145? I superseded the mp as a result of it being reliant upon a new branch.
[10:33] <nic-doffay> Then once the new selectors branch lands perhaps a full functional review?
[10:33] <nic-doffay> Unless you're comfortable doing both now?
[10:34] <Saviq> nic-doffay, we'll get there, not today though - we won't merge it before release anyway
[10:35] <nic-doffay> Saviq, also are you aware of anything in QML that can mimic abstraction?
[10:35] <Saviq> nic-doffay, what kind of abstraction?
[10:35] <nic-doffay> Saviq, something like an abstract base class.
[10:35] <Saviq> nic-doffay, btw, did you use  the "resubmit proposal" link in https://code.launchpad.net/~nicolas-doffay/unity8/filter-selector/+merge/183503 ?
[10:35] <Saviq> nic-doffay, QML is *all* about abstractions
[10:35] <nic-doffay> Saviq, yeah I did.
[10:36] <Saviq> nic-doffay, weird, it didn't leave a "superseded by" / "supersedes" links
[10:36] <Saviq> nvm
[10:36] <Saviq> nic-doffay, any qml component can be a base component to another
[10:36] <Saviq> nic-doffay, Item { property string foo: "bar" }
[10:37] <nic-doffay> Saviq, yeah but an abstract base class so that it can't potentially be used by someone else.
[10:37] <nic-doffay> Like C++/C#
[10:37] <Saviq> nic-doffay, you mean private/protected properties? no
[10:37] <nic-doffay> Saviq, yeah essentially.
[10:37] <Saviq> nic-doffay, nope, nothing like that
[10:38] <nic-doffay> Saviq, ergh right. Thanks.
[10:38] <Saviq> nic-doffay, well, just don't expose a type to the outside world
[10:38] <Saviq> nic-doffay, and they won't be able to use it
[10:38] <Saviq> nic-doffay, i.e. don't put it in the qmldir file
[10:39] <nic-doffay> Saviq, then only the current dir would be access it, right?
[10:39] <Saviq> nic-doffay, no, you can import "Foo/Bar" where the internal component is
[10:39] <Saviq> nic-doffay, and well, people would still be able to import "/full/path/to/Foo/Bar"
[10:39] <Saviq> nic-doffay, but no one will
[10:41] <nic-doffay> Saviq, I guess if that's the closest it can get to completely restricting access I'll have to settle. Thanks.
[10:41] <Saviq> tvoss, you'd like https://code.launchpad.net/~thomas-voss/unity8/add_post_inst_script_to_gain_cap_sys_resource/+merge/191144 to be merged for release, right?
[10:42] <Saviq> tvoss, wth does it say "updating diff" all the time?
[10:44] <Saviq> tvoss, and is that persistent across reboots?
[10:44] <tvoss> Saviq, yup, should be persistent across reboots, ripped of the post inst script from the gnome-keyring package
[10:45] <tvoss> Saviq, merged, yes. Requires https://code.launchpad.net/~thomas-voss/unity-mir/oom_adjust/+merge/191123, too
[10:45] <tvoss> Saviq, well, not strictly requires
[10:46] <tvoss> Saviq, just land the mp
[10:46] <tvoss> asac, http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/97:20131015:20131015/4730/notes-app-autopilot/ reports 4 crashes in the overview, although nothing crashed
[10:46] <tvoss> asac, seems like crash "detection" is a wildcard *crash*
[10:47] <Saviq> lol
[10:47] <Saviq> didrocks, +1 on https://code.launchpad.net/~thomas-voss/unity8/add_post_inst_script_to_gain_cap_sys_resource/+merge/191144 ?
[10:47] <tvoss> popey, who is looking into the failing ap test cases for ubuntu-filemanager?
[10:48] <tvoss> popey, http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/97:20131015:20131015/4730/ubuntu-filemanager-app-autopilot/486002/ is a bit weird ;)
[10:48] <Saviq> tvoss, setcap is not installed on my device, has that been added?
[10:48] <tvoss> none == none
[10:48] <asac> tvoss: nice catch :)
[10:48] <tvoss> Saviq, hah, good catch
[10:48] <didrocks> Saviq: I approved it, but yeah, you're right need to add setcap as a dep
[10:48] <asac> Saviq: oh it was you... well done!
[10:49] <popey> tvoss: I will poke balloons when he wakes up
[10:49] <tvoss> Saviq, the *crash* was me
[10:49] <Saviq> asac, ↑
[10:49] <tvoss> ;)
[10:49] <asac> lol
[10:49] <asac> nevermind
[10:49] <asac> thanks to both of you for many things! :)
[10:49] <tvoss> argh, which package has setcap?
[10:49] <Saviq> tvoss, didrocks, are postinst ran on the devices or only during image creation? will that get through on the image?
[10:50] <tvoss> Saviq, not sure
[10:50] <didrocks> Saviq: only during image creation (or when you install a package by hand)
[10:50] <didrocks> Saviq: but it needs to be seeded anyway and it's a dep of unity8 now
[10:50] <Saviq> tvoss, yeah, I'm worried this is not gonna cut it
[10:50] <Saviq> tvoss, maybe an additional upstart job instead?
[10:50] <tvoss> Saviq, why do you think so?
[10:51] <didrocks> Saviq: no, it should work, generating the image is about package installation basically
[10:51] <didrocks> so if you have the right dep, that's fine
[10:51] <didrocks> add a dep on libcap2-bin
[10:51] <Saviq> didrocks, I know, but do we know what "setcap" does when called?
[10:51] <tvoss> didrocks, just on unity8?
[10:51] <Saviq> tvoss, didrocks, does it store the settings in a file somewhere?
[10:51] <Saviq> so that it's applied on boot?
[10:51] <tvoss> Saviq, does not need to, look at the gnome-keyring package
[10:52] <didrocks> Saviq: yeah, the dep from the binary package you add the postinst hoook
[10:52] <Saviq> tvoss, do we know that it's working when applied on a different device (image builder) than the target?
[10:52] <didrocks> Saviq: well, I guess that's stephane's job to ensure that
[10:52] <Saviq> tvoss, like how does it know?
[10:53] <Saviq> maybe it just stores it on the file itself?
[10:54] <Saviq> "Failed to set capabilities on file `/usr/bin/unity8' (Operation not supported)"
[10:54] <Saviq> tvoss, ↑
[10:55] <tvoss> Saviq, it stores them as extended attributes
[10:55] <didrocks> Saviq: it's part of file system capabilities, I think it's the same set of attribute or rights that we do have
[10:55] <Saviq> tvoss, didrocks, we're on ext2 and not mounted xattr
[10:55] <tvoss> \o/
[10:55] <didrocks> ext2 on touch, really?
[10:55]  * didrocks looks
[10:56] <Saviq> can we please test that stuff actually works?
[10:56] <didrocks> /dev/loop0 on / type ext2 (rw,relatime,errors=continue)
[10:57] <tvoss> Saviq, yup, my bad
[11:00] <Saviq> /food
[11:04] <mhr3> mzanetti, any idea what this is?
[11:04] <mhr3> file:///home/phablet/shell/Dash/DashPreviewPlaceholder.qml: Object destroyed during incubation
[11:04] <mzanetti> otp
[11:21] <tsdgeos> Mirv: i can't use qt5-beta-proper
[11:22] <tsdgeos> Mirv: http://paste.ubuntu.com/6240105/
[11:23] <Mirv> tsdgeos: right. I haven't had time for the PPA for weeks, but the auto-builds are still running. that sounds like that the diverts from qtmultimedia-touch don't take it kindly that the diverted package gets upgraded.
[11:24] <Mirv> or, right, that the diverted package actually gets to the same version
[11:24] <Mirv> so qtmultimedia-touch would need upgrading to work with that, then
[11:26]  * tsdgeos uninstalls billions of multimedia pckages
[11:28] <didrocks> Saviq: ubuntu-touch-session was providing the upstart session right?
[11:28] <didrocks> Saviq: you need a replaces: in that case
[11:28] <didrocks> is that dropped from ubuntu-touch-session as well?
[11:28] <didrocks> (and ogra doing it?)
[11:29] <tsdgeos> let's see if stuff still starts
[11:33] <didrocks> Saviq: I'll buy a new pair of glass it seems :p the replaces is there
[11:48] <Cimi> how do I see the video carousel? putting videos?
[11:48] <Cimi> or is there a trick or sole to enable?
[11:48] <Cimi> scope
[11:50] <Saviq> Cimi, put videos in, yes
[11:50] <Saviq> Cimi, if they don't show up - try searching to refresh, but it should be fine
[11:50] <Cimi> first have to download 6
[11:50] <Saviq> Cimi, if they still don't - you might not have the right codecs
[11:50] <Cimi> don't have any
[11:51] <Cimi> Saviq, which codecs are supported?
[11:51] <Cimi> or sample videos I can take?
[11:52] <Cimi> trying also not to fill the memory
[11:57] <tsdgeos> Saviq: also happens with 5.1.1 so may not be that then
[11:58] <tsdgeos> lunch!
[12:00] <Cimi> Saviq, tsdgeos we also have another issue in qt that I think we should distropatch
[12:00] <Cimi> the default maximumFlickVelocity on the devices seems to be slow
[12:01] <Cimi> indeed we tweak it when we need, since we have higher pixel density
[12:01] <Cimi> I think we should distropatch qt to change the default value accordingly to pixel density
[12:21] <om26er> Saviq, ping
[12:22] <om26er> Saviq, unity8 in trunk seems to break my sim signals.. i.e. no signals
[12:22] <om26er> I have to open the messaging app or the dialer app first and then the signals come back
[12:23] <om26er> because opening those apps invokes telephony-service and which I assume calls ofono
[12:23] <didrocks> sil2100: please track that ^
[12:23] <Saviq> om26er, that will be fixed in session-manager-touch
[12:23] <Saviq> om26er, https://code.launchpad.net/~saviq/session-manager-touch/drop-unity8/+merge/190842
[12:25] <om26er> Saviq, ok. I reported a bug for that a few hours ago. I'll assign it you then.
[12:26] <Saviq> om26er, k
[12:37] <mzanetti> mhr3: when do you see this message?
[12:38] <mhr3> mzanetti, when playing with switching-previews :)
[12:39] <mzanetti> mhr3: I guessed that far. I don't see it tho. so probably some certain corner case
[12:40] <mhr3> mzanetti, sorry, no exact way to repro
[12:53] <Saviq> mzanetti, saw bug #1239750 ?
[12:53] <mzanetti> Saviq: yes
[12:53] <Saviq> mhr3, it sometimes happen when an item in a ListView is destroyed before it completed
[12:54] <mzanetti> Saviq: not sure yet how to tackle this
[12:54] <tsdgeos> Cimi: i think they somehow fixed that in later qts
[12:54] <Cimi> tsdgeos, so we should back port no?
[12:54] <mzanetti> Saviq: given that the appID is indeed a different one
[12:54] <mzanetti> so it's in fact a different app
[12:54] <tsdgeos> Cimi: no, we should update :D
[12:55] <Cimi> tsdgeos, indeed
[12:55] <Saviq> mzanetti, appid://blah.blah.blah/blah/current-user-verion
[12:55] <Saviq> version
[12:55] <mzanetti> Saviq: do appids now contain slashes?
[12:55] <mzanetti> good thing this stuff is communitcated :)
[12:55] <Saviq> mzanetti, no
[12:55] <Saviq> mzanetti, appid:// !== application:///
[12:56] <Saviq> mzanetti, appid:// is a way to target an app at no specific version
[12:56] <Saviq> mzanetti, like ppid://com.ubuntu.developer.webapps.webapp-facebook/webapp-facebook/current-user-version
[12:56] <Saviq> *appid
[12:56] <Saviq> mzanetti, http://bazaar.launchpad.net/~indicator-applet-developers/url-dispatcher/trunk.13.10/revision/34
[12:56] <mzanetti> mhm... ok. will check it out
[12:57] <mzanetti> Saviq: I think the switching-previews are one step closer. pushed a bunch of fixes
[12:57] <Saviq> mzanetti, why we need the  "current-user-version" you'll need to ask tedg ;)
[12:57] <Saviq> mzanetti, cool beanz
[12:57] <tsdgeos> Saviq: i looked at the code and it seems you could request a specifc version too maybe
[12:57] <tsdgeos> url-dispatcher
[12:57] <Saviq> tsdgeos, yes yes
[12:57] <tsdgeos> seems to have some kind of support for it
[12:58] <Saviq> tsdgeos, appid://com.ubuntu.developer.webapps.webapp-facebook/webapp-facebook/0.1.5
[12:58] <Saviq> tsdgeos, but that's the same as
[12:58] <Saviq> application:///com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_0.1.5.desktop
[12:58] <tsdgeos> ah
[12:58] <tsdgeos> ok
[12:58] <Saviq> tsdgeos, and I just don't get why we need the "current-user-version" at all
[12:58] <Saviq> couldn't it just be
[12:59] <Saviq> appid://com.ubuntu.developer.webapps.webapp-facebook/webapp-facebook/
[12:59] <tsdgeos> ah
[12:59] <Saviq> for the "current user version"?
[12:59] <tsdgeos> sure
[12:59] <Saviq> like what else would you request
[12:59] <Saviq> TBH I think ↑ that should be the default
[12:59] <Saviq> and version as a url param
[12:59] <Saviq> i.e. appid://com.ubuntu.developer.webapps.webapp-facebook/webapp-facebook?version=0.1.5
[12:59] <tsdgeos> Saviq: so, what do you want me to do with the hang on animation, go back to qt5.0.x and keep trying to find out what's wrong?
[13:00] <Saviq> or well, appid://com.ubuntu.developer.webapps/facebook?version=0.1.5 would be even better :P
[13:00] <Saviq> ETOOMANYWEBAPPS
[13:00] <Saviq> tsdgeos, no
[13:00] <tsdgeos> hang on quit on animation i mean
[13:00] <Saviq> tsdgeos, upstart seems to take care of it for us now
[13:00] <Saviq> tsdgeos, i.e. no problems in autopilot now that we're using upstart
[13:00] <Saviq> tsdgeos, please add as much info as possible to the bug
[13:01] <Saviq> tsdgeos, and make it Medium
[13:01] <mhr3> Saviq, kill the disable-hswipe-on-vswipe now!!!
[13:01] <mhr3> it's driving my crazy
[13:01] <mhr3> stupid dash doesn't want to swipe the way i want half of the time
[13:02] <Saviq> mhr3, it's like that all the time
[13:02] <Saviq> mhr3, you only ever could swipe to the sides on empty spaces
[13:02] <Saviq> mhr3, that's QML I'm afraid
[13:03] <mhr3> Saviq, it's just the threshold i guess, i do tiny vswipe and then it doesn't want to do the switch between changes
[13:03] <Saviq> mhr3, if you put a horizontal flickable on top of a vertical one - you won't be able to move to the outer one while the inner one is moving
[13:03] <mhr3> s/changes/pages/
[13:03] <Saviq> mhr3, yes, the disable-hswipe-on-vswipe has nothing to do with it
[13:04] <tsdgeos> Saviq: ok
[13:04] <mhr3> Saviq, but someone it got worse after that branch
[13:04] <Saviq> mhr3, you think it did - it didn't
[13:04] <Saviq> mhr3, bug #1152150
[13:04] <Saviq> mhr3, really - patch -R it, you'll see it's exactly the same
[13:04] <Saviq> mhr3, you just notice it more now and associate with that merge
[13:05] <mhr3> Saviq, still.... grrrrrrrrrrr
[13:07] <Cimi> Saviq, still this one waiting review https://code.launchpad.net/~unity-team/unity8/carousel-loader/+merge/190406
[13:08] <Saviq> Cimi, not gonna happen for S
[13:16] <mhr3> Cimi, sorry, it'd cause too many issues imo
[13:16] <mhr3> Cimi, after 13.10
[13:17] <Cimi> mhr3, what, that loader?
[13:17] <mhr3> Cimi, count changes too often in scopes, basing renderer off of it is dangerous
[13:17] <mhr3> we'd need to minimize the count changes first
[13:26] <tsdgeos> Saviq: so the maintainer of qsortfilterproxy argues that my patch is wrong and that the bug is actually at the qmlvisualmodel level
[13:26] <tsdgeos> Saviq: so i'll have to create a qml testcase and then let the qml people and him fight on who's wrong
[13:27] <tsdgeos> Saviq: we probably don't want to carry much time a patch in qsortfilterproxymodel that is not blessed by upstream
[13:27] <tsdgeos> Saviq: mind if i edit the description of https://bugs.launchpad.net/unity-mir/+bug/1239409 ?
[13:28] <Saviq> tsdgeos, do
[13:28] <Saviq> tsdgeos, that above one was re: which patch?
[13:28] <Saviq> tsdgeos, the loop?
[13:28] <tsdgeos> Saviq: the one i made to fix the issues with pstolowski reorder branch
[13:29] <Saviq> ah
[13:29] <Saviq> tsdgeos, since we dropped reordering anyway... we might as well drop that patch from qt
[13:29] <Saviq> tsdgeos, before release that is
[13:29] <Saviq> Mirv, still around?
[13:29] <tsdgeos> Saviq: sure
[13:30] <Saviq> feels like a safe route
[13:30] <tsdgeos> +1
[13:50] <MacSlow> Saviq, can you imagine what alcohol would to to my untouched liver? ;)
[13:50] <MacSlow> would do
[13:50] <Saviq> MacSlow, soften it slightly? ;)
[13:50] <mzanetti> the s shirt looks like the q one
[13:50] <didrocks> bregma: Trevinho: andyrock: hey, urgency ping
[13:51] <didrocks> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1240074
[13:51] <didrocks> with latest unity
[13:51] <Trevinho> didrocks: pong
[13:51] <Saviq> mzanetti, but you can have a t-shirt with the infographic ;)
[13:51] <mzanetti> huh?
[13:51] <didrocks> Trevinho: elmo can produce more info
[13:51] <didrocks> Trevinho: I had it at first as well
[13:51] <MacSlow> mzanetti, a t-shirt that can actually pull data form the phone's inforgraphic-backend :)
[13:51] <mzanetti> hah, right
[13:51] <Saviq> mzanetti, http://shop.canonical.com/advanced_search_result.php?keywords=infographic+and+t-shirt
[13:51] <Saviq> MacSlow, exactly what I thought about :D
[13:52] <Saviq> MacSlow, double tap to see how much alcohol you drunk today :D
[13:52] <MacSlow> Saviq, should be possible with today's tech I guess :)
[13:52] <MacSlow> Saviq,  :)
[13:52] <Trevinho> didrocks: mh, ok, thanks let me check that
[13:52] <mzanetti> reminds me of the episode of Big Bang Theory where Raj has the speaker shirt :D
[13:52] <mzanetti> hillarious
[13:52] <didrocks> Trevinho: if we need to revert, let's revert
[13:52] <MacSlow> mzanetti, don't know that one
[13:53] <Trevinho> didrocks: but... I can't understand exactly what the problem is there...
[13:53] <Trevinho> the bug is quite generic
[13:53] <didrocks> Trevinho: well, I got the same this morning
[13:53] <Trevinho> didrocks: no multi-monitor at all?
[13:53] <mzanetti> MacSlow: http://www.youtube.com/watch?v=n6r_AclV6X8
[13:54] <greyback> mzanetti: uh oh, if I click that, that's 22 minutes of me not working
[13:54] <mzanetti> nah... it's a 2 minutes clip
[13:54] <didrocks> Trevinho: yeah, just one was up
[13:54] <didrocks> then I rebooted
[13:54] <didrocks> and it was fine again
[13:54] <MacSlow> mzanetti, top... totally wicked!
[13:54] <Trevinho> didrocks: just one laucnher/panel and such?
[13:55] <didrocks> Trevinho: one of the screen was off
[13:55] <Trevinho> mh, how could be that related to unity... looks weird
[13:55] <didrocks> even going to g-c-c
[13:55] <didrocks> yeah, it's weird
[13:55] <didrocks> hey elmo
[13:56] <Trevinho> didrocks: I don't even seen what could have caused it from 7.1.2+13.10.20131014.1-0ubuntu1 to 7.1.1+13.10.20131004-0ubuntu1
[13:56] <didrocks> eean: we are discussing https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1240074
[13:56] <didrocks> elmo: ^
[13:56] <didrocks> sorry eean :)
[13:56] <didrocks> elmo: so, it seems you had the same symptom than I
[13:56] <didrocks> like just one screen starting
[13:56] <didrocks> and the other one being off?
[13:56] <elmo> didrocks: yeah
[13:57] <didrocks> do you know exactly what happen? (I know that when I got it, I had only the internal monitor on, and then I plugged the other one)
[13:58] <elmo> didrocks: sorry, I'm not sure what you mean.  basically, I can reproduce it by turning on display mirroring
[13:58] <elmo> didrocks: if I do that, I get an image on only one screen
[13:58] <Spads> ah
[13:58] <didrocks> ah, different from what I saw
[13:58] <Spads> I got it without mirroring
[13:58] <Spads> but with both displays on
[13:58] <didrocks> Spads: but then, you still get it?
[13:58] <Spads> yes
[13:58] <elmo> yeah, I can reproduce it that way too
[13:58] <elmo> mirroring just seemed like the easiest to explain
[13:58] <didrocks> let me try
[13:58] <Spads> yeah
[13:59] <didrocks> hum, I can't get it anymore
[13:59] <didrocks> I just rebooted and it was fine
[13:59] <didrocks> (this morning)
[13:59] <didrocks> and I can't reproduce it again
[13:59] <didrocks> with the same unity version
[13:59] <didrocks> (7.1.2+13.10.20131014.1-0ubuntu1)
[14:00] <didrocks> elmo: can you try just upgrading? I can see unity being guilty for a lot of things, but having the screen shutted down…
[14:00] <didrocks> Trevinho: your team didn't land anything regarding that, right?
[14:00] <elmo> didrocks: checking
[14:00] <didrocks> thanks :)
[14:00] <Trevinho> didrocks: mh, I've been checking but I don't see what bit could have affected this
[14:01]  * didrocks looks at uploads
[14:01] <Saviq> didrocks, soo, we have a dpatch in qtbase that's being debated upstream, but we had to revert the code triggering the issue for unrelated reasons, so we could drop the dpatch to be on the safe side, what do you think?
[14:01] <Spads> 2013-10-14 20:16:14 status installed unity:amd64 7.1.2+13.10.20131014.1-0ubuntu1
[14:01] <Spads> er, mispaste
[14:01] <didrocks> Saviq: does this patch is known to create any issue?
[14:02] <didrocks> "triggering the issue" is quite vague :)
[14:02] <elmo> didrocks: I can't reproduce now
[14:02] <Saviq> didrocks, no, but it's not known to not
[14:02] <didrocks> elmo: yeah, same frustration than mine then…
[14:02] <Saviq> didrocks, without the patch unity8 was broken when reordering categories in Home
[14:02] <didrocks> I don't see anything creating it :/
[14:02] <Saviq> didrocks, but we've reverted that for other reasons
[14:02] <didrocks> Saviq: let's not change anything that we ship for now I would say
[14:02] <Saviq> didrocks, but upstream is arguing whether the patch tsdgeos sent is correct
[14:03] <Saviq> didrocks, ok
[14:03] <didrocks> after V1, we can reevaluate
[14:03] <Saviq> didrocks, there's no known regressions
[14:03] <Saviq> didrocks, so that's good
[14:03] <tsdgeos> Saviq: didrocks: otoh this is a patch to a core qt component
[14:03] <didrocks> elmo: I don't see any other upload which can be guilty though…
[14:03] <elmo> didrocks: right, and I only downgraded unity
[14:03] <tsdgeos> Saviq: didrocks: and upstream argues it destroys some optimization in the code
[14:03] <tsdgeos> i'm fine with leaving it in
[14:04] <didrocks> elmo: yeah, but maybe restarting the session was enough to """fix""" it
[14:04] <didrocks> tsdgeos: let's keep it for V1, really, we have too many bugs to tackle right now to get to that level of details/risks :)
[14:04] <tsdgeos> didrocks: i'm fine leaving it for now, but forever 13.10 not sure i'm really confortable
[14:04] <elmo> didrocks: possibly
[14:04] <didrocks> Spads: have you tried restarted the session?
[14:05] <Spads> didrocks: no, haven't logged out since the last reboot-requiring update two days ago
[14:06] <didrocks> Trevinho: before Spads maybe try logging out, is there any info that can be interesting to us? ^
[14:07] <Trevinho> 1 sec...
[14:10] <tsdgeos> Saviq: ok, added my bt to https://bugs.launchpad.net/unity-mir/+bug/1239409 with what i think is interesting in it
[14:10] <Trevinho> didrocks, Spads: I guess some output from xrandr, wnckprop --list may help to understand what's going on
[14:11] <tsdgeos> Saviq: now i'm going to have a look at creating the qt testcase to get them to fight themselves at who's bug it is
[14:12] <Spads> ok
[14:14] <Spads> http://pastebin.ubuntu.com/6240708/ <-- Trevinho I redacted some of the window titles :)
[14:15] <Trevinho> Spads: LVDS1 is the black one, right?
[14:15] <Spads> Trevinho: yep
[14:15] <Saviq> tsdgeos, yup, thanks
[14:16] <Trevinho> mh, it doesn't seem ON on xrandr as well.. it's very strange that only updating unity can fix this issue
[14:16] <Trevinho> downgrading*
[14:16] <Spads> well, it's possible it was the session restart that did it
[14:16] <Spads> since elmo can't reproduce
[14:17] <Trevinho> Spads: looking there unity only correctly creates the windows it needs...
[14:17] <Spads> I can see if a restart without touching my packages helps
[14:17] <didrocks> Spads: elmo: do you have the list of upgrades you have done before getting that issue?
[14:17] <Trevinho> Spads: just try to do a "compiz --replace&" in a terminal before
[14:17] <Trevinho> I see you've a couple opneed :D
[14:17] <Spads> Trevinho: STALKER
[14:17] <didrocks> oh, nice idea :)
[14:17] <Trevinho> ahah
[14:18] <Spads> didrocks: I can snip out a dpkg.log spam if you need
[14:18] <Spads> okay, so should I do compiz --replace first?
[14:18] <Trevinho> yep
[14:18] <Spads> okeedokee
[14:18] <Trevinho> it should reload unity, I don't expect it to fix anything though
[14:19] <Spads> LVDS1 still off
[14:20] <Spads> yeah my X server is still from the 13th
[14:20] <Spads> shall I log out now?  Because all my windows are in one workspace and it's making my brain cramp :)
[14:20] <didrocks> Trevinho: ? ^ I think Spads should ;)
[14:21] <Spads> I could try the multi-monitor tool again
[14:21] <Spads> to see if it can wake lvds1 up now
[14:21] <didrocks> Spads: I tried it this morning, without any success
[14:21] <Spads> oh, so you saw this as well?
[14:21] <didrocks> yeah, but as I suspended/resumed a lot, I was thinking it was due to that
[14:21] <didrocks> and I just rebooted
[14:22] <Spads> yeah it couldn't switchi t on
[14:22] <Trevinho> Spads: yes, reboot
[14:22] <Spads> Trevinho: I'm going to log out first instead of reboot
[14:22] <Trevinho> Spads: using xrandr manually doens't help?
[14:22] <Trevinho> Spads: sure
[14:23] <Spads> welp, that fixed it
[14:24] <Spads> even before it was done logging me out
[14:24] <Spads> although that's probably just lag of various sorts
[14:25] <Spads> ooh, apport wants me to submit a complaint
[14:25] <Trevinho> Spads: why complaining, that's working! ^_^
[14:25] <bregma> probably just the usual unity-panel-service crash-on-dbus-disconnect apport noise
[14:26] <Trevinho> yeah, maybe...
[14:26] <dednick> mhr3: ping
[14:26] <mhr3> dednick, pong
[14:26] <dednick> mhr3: howdy. could you do me a favour? :)
[14:26] <Spads> okay, well at least it looks like it was a transient thing that's fixed now
[14:27] <dednick> mhr3: can you grep your syslog for anything from "indicator-date"
[14:28] <dednick> mhr3: on your device i mean
[14:29] <mhr3> dednick, syslog?
[14:29] <mhr3> hmm, let me try
[14:29] <dednick> mhr3: zgrep 'indicator-date' /var/log/syslog*
[14:30] <didrocks> Spads: can you do one more test?
[14:30] <Spads> didrocks: sure what's up
[14:30] <didrocks> shut your computer down, disconnect the external monitor, boot it, log in, then plug the external monitor
[14:31] <mhr3> dednick, nope, nothing
[14:31] <dednick> mhr3: have you flashed lately?
[14:31] <Spads> didrocks: okay
[14:31] <mhr3> dednick, yes, morning
[14:31] <mhr3> dednick, was just about to ask if it'd survive
[14:31]  * Spads will bbiab
[14:31] <dednick> mhr3: hm. i think it does actually
[14:31] <mhr3> dednick, fwiw i don't have any gzipped syslogs there
[14:32] <mhr3> dednick, and the first entry is from this morning
[14:32] <dednick> mhr3: ah. probably didnt then
[14:32] <dednick> mhr3: dang. dont suppose you noticed your datetime indicator not working ;)
[14:32] <mhr3> dednick, nope, today it was fine
[14:32] <dednick> stupid indicator
[14:33] <dednick> works when you dont want it to
[14:33] <mhr3> who wouldn't love those kind of bugs
[14:33] <dednick> i'd like everything to always work
[14:34] <dednick> although i might not have much of a job
[14:34] <mhr3> dednick, they you have to be the one who makes it always work :)
[14:34] <mhr3> then*
[14:35] <dednick> what you talkin about. my stuff always works
[14:35] <greyback> Saviq: hey, what was the signal you wanted unity-mit/unity8 to emit when Mir was ready to get client connections? Upstart needed it
[14:35] <Saviq> greyback, raise(SIGSTOP)
[14:35] <dednick> mhr3: other people secretly add bugs to my code.
[14:35] <greyback> Saviq: ok. I can add to unity-mir easily enough, but how about the SF case?
[14:35] <Saviq> greyback, we'd need to raise it on sflinger, too - but whenever, so probably in main()
[14:35] <mhr3> dednick, damn, you noticed it?
[14:36] <dednick> trying to bring me down to their level!
[14:36] <Saviq> greyback, since we know on sflinger nothing else will emit it, and we know we're ready already, we'll just emit ourselves
[14:36] <Spads> okay, let's try plugging this in now
[14:36] <dednick> all: anyone's datetime indicator not working at the moment?
[14:37] <Spads> didrocks: works fine
[14:37] <didrocks> Spads: ok, thanks for all the testing :)
[14:37] <Spads> dednick: I had that problem last week, but it's been clear for a while
[14:38] <didrocks> thanks Trevinho, Spads, elmo. Seems it's a transition issue in something else than unity anyway, we are going to continue investigating
[14:38] <Spads> didrocks: want a paste of my dpkg.log for the past few days?
[14:38] <Spads> I warn you it's full of noise :)
[14:38] <Trevinho> didrocks: np
[14:38] <didrocks> Spads: no, I think we've identified another victim :)
[14:38] <didrocks> (upower)
[14:38] <Spads> eeexcellent
[14:38] <Spads> ohhhhh
[14:39] <Spads> come to think
[14:39] <didrocks> yeah?
[14:39] <Spads> the behaviour of the light dimmer was odd for a while
[14:39] <didrocks> yeah, that's what the last upower was supposed to fix
[14:39] <Spads> like it seemed like it took on a new power profile
[14:39] <Spads> aha
[14:40] <Saviq> greyback, https://code.launchpad.net/~saviq/unity8/raise-sigstop/+merge/191212
[14:45] <mzanetti> dednick: define "not working". It's here but none of the items in it open something when I tap them
[14:45] <mzanetti> dednick: not sure if that is expected or not
[14:46] <dednick> mzanetti: that may indicator not working
[14:46] <dednick> is the indicator-datetime-service process running on the device?
[14:47] <dednick> mzanetti: otherwise it may just be another bug
[14:47] <dednick> mzanetti: although that one is related to the indicator restarting i think.
[14:48] <mzanetti> dednick: oh... just realized that it tried to launch the datetime settings but I already had systemsettings open in the "accounts" page
[14:48] <mzanetti> dednick: so it just brought the accounts page to the front again
[14:48] <mzanetti> dednick: I guess that means it's working fine (the indicator part at least)
[14:48] <dednick> mzanetti: yup
[14:49] <dednick> mzanetti: not working means not visible in this case i think (or at least not updating the time)
[14:49] <mzanetti> dednick: I've seen kalikiana's device at the dev days basically never showing the datetime indicator. but I haven't ever seen this issue on my device
[14:54]  * tsdgeos hits himself
[14:54] <tsdgeos> after wondering why the qml testcase works for a while
[14:54] <tsdgeos> i realized we have patched qt so i can't be hitting the bug
[14:54] <tsdgeos> :D
[14:55] <mhr3> Saviq, could you look at the overridden-results-preview branch?
[14:55] <tsdgeos> what?¿?¿? http://www.engadget.com/2013/10/13/lg-g-flex-revealed/
[14:56] <tsdgeos> it's so big that they curved it so you can use it with a single hand
[14:56] <tsdgeos> weeeeir
[14:56] <tsdgeos> d
[15:04] <mhr3> tsdgeos, sometimes the dash decides that there's less content than there really is... any idea what's up with that?
[15:04] <mhr3> i mean there's lots of content but it doesn't want to let me scroll to it
[15:05] <tsdgeos> mhr3: that'd be a bug in the LVWPH i guess :'(
[15:06] <mhr3> tsdgeos, yey!
[15:07] <tsdgeos> mhr3: i guess it's not easily-reproducible, no?
[15:08] <mhr3> tsdgeos, it you just want to get into that state, it's not too hard, if you want exact steps though...
[15:09] <tsdgeos> mhr3: well, not exact steps, but rough step?
[15:09] <tsdgeos> s
[15:09] <mhr3> tsdgeos, search in home scope, swipe away to clear
[15:09] <tsdgeos> like "if you do this a few times it'll happen"
[15:09] <mhr3> repeat until it's broken
[15:09] <tsdgeos> ?
[15:09] <tsdgeos> mhr3: swipe away = change to a different scope?
[15:09] <mhr3> tsdgeos, yes
[15:09] <tsdgeos> and then?
[15:10] <tsdgeos> when does it break? how does it look like?
[15:10] <tsdgeos> breaks before swiping away?
[15:10] <mhr3> it looks like you can't scroll all the way down :)
[15:10] <tsdgeos> after?
[15:11] <mhr3> tsdgeos, it's easier to see when you still have lots of results from the home scope, so before swiping away, which resets it back to the surfacing model
[15:12] <tsdgeos> mhr3: ok, could you open a bug with all that info?
[15:12] <mhr3> tsdgeos, are you sure there isn't one already?
[15:12] <tsdgeos> i'm not
[15:12] <tsdgeos> but if there is
[15:12] <tsdgeos> it's not assigned to me :D
[15:12] <tsdgeos> Saviq: any idea about ↑↑↑↑
[15:13] <Saviq> tsdgeos, no, didn't see/hear
[15:13] <mhr3> opening then
[15:15] <mhr3> tsdgeos, although i'm seeing this on saucy-proposed which still has the reordering, maybe it's easier to trigger with that
[15:15] <tsdgeos> may b
[15:15] <mhr3> but i do remember seeing it before that as well
[15:21] <Saviq> kill -SIGINT tsdgeos
[15:22] <tsdgeos> Saviq: what?
[15:22] <Saviq> tsdgeos, can I interrupt you?
[15:22] <tsdgeos> sure
[15:22] <greyback> Saviq: https://code.launchpad.net/~gerboland/unity-mir/listen-for-server-start-stop-ready/+merge/191224
[15:23] <Saviq> greyback, cool beanz
[15:24] <greyback> tsdgeos: you pay extra for the "I sat on my phone" joke?
[15:24] <greyback> ah that comment was 30 mins ago
[15:24] <tsdgeos> :D
[15:25] <mhr3> tsdgeos, https://bugs.launchpad.net/unity8/+bug/1240118
[15:32] <mhr3> tsdgeos, so with the steps there i can reproduce it reliably when the reordering is enabled, with trunk it just breaks the search bar position
[15:33] <tsdgeos> i fixed the search bar pos a while ago :S
[15:33] <tsdgeos> maybe needs more fixing :D
[16:21] <mhr3> Saviq, is this useful in any way? http://paste.ubuntu.com/6241183/
[16:33]  * greyback eod
[16:47] <Cimi> Saviq, mhr3 https://code.launchpad.net/~cimi/unity8/carousel-music-video/+merge/191247
[16:47] <Cimi> for T
[16:55] <mhr3> Cimi, yey, pretty :)
[16:56] <mhr3> Cimi, it's not pixel perfect though :P
[16:56] <Cimi> mhr3, music lens?
[16:57] <Cimi> mhr3, not my fault
[16:57] <mhr3> Cimi, yep
[16:57] <mhr3> Cimi, see http://imgur.com/6NgLiOZ
[16:58] <Cimi> mhr3, can't do much about it with those assets
[17:01] <mhr3> Cimi, the video carousel behaves weird though, it keeps disappearing for me... not sure whether your branch introduced that though
[19:11] <thomi> morning
[20:32] <kgunn> mterry: ping
[20:33] <mterry> kgunn, hello
[20:33] <kgunn> mterry: hey...i don't have a sim...but you can rcv/answer a call with a locked phone right ?
[20:33] <kgunn> locked greeter
[20:33] <mterry> kgunn, yes, I believe I tested last Friday
[20:33] <mterry> kgunn, you can test without a sim these days
[20:33] <mterry> kgunn, I'll test again, just to make double sure
[20:34] <kgunn> mterry: how to test w/o a sim ?
[20:34] <mterry> kgunn, one moment, let me get instructions
[20:34] <kgunn> mterry: i assume emergency call is supported as well
[20:34] <kgunn> ?
[20:35] <mterry> kgunn, no need for emergency call, there is no lock
[20:37] <kgunn> mterry: yeah...ok, so there is _some_ effort there just to make sure those items "just work" when lock get in
[20:39] <mterry> kgunn, hmm, the script to fake an incoming call isn't working right now
[20:39] <mterry> kgunn, for when the lock is enabled...
[20:40] <kgunn> ok, no biggie..just updating bp's
[20:41] <mterry> kgunn, we need either the dialer-app to provide a Qml plugin (which got put on hold for 13.10) or transition the split greeter into a full session that can launch internal apps (which we probably want to do eventually anyway)
[20:42] <kgunn> mterry: right, i'd like to focus on migrating to the split greeter really....
[20:42] <kgunn> mterry: what do you think...i mean we're now free for effectively another 6mo window
[20:42] <mterry> kgunn, so would I...  I started updating my split branch today and was going to try to test everything in concert
[20:44] <kgunn> mterry: so we're looking at setting milestones for the 1/2 way mark to 14.04...i would like to see split greeter be one of those
[20:44] <kgunn> thots?
[20:44] <kgunn> seems like we're close
[20:45] <mterry> kgunn, OK.  Yeah, we're close.  If we are OK with regressions, even closer.  I've been trying to keep track of things that need updating for a split greeter (things like making sure the indicators have a phone_greeter mode and the dialer stuff
[20:46] <mterry> Also sharing some settings like volume/ringtone via AccountsService
[20:48] <mterry> kgunn, blueprints!  Sorry, I have not been keeping the greeter ones up to date...  :(
[20:49] <kgunn> mterry: no worries....you are much less an offender than most...so i thank you for that
[20:49] <mterry> I find that hard to believe
[20:49] <mterry> :)
[20:49] <kgunn> mterry: everyone's probably going to need to help me with filtering out work items
[20:57] <mterry> hmm, now I can't get the phone to see my sim
[21:08] <mterry> kgunn, yup, just tested with real sim, we can receive calls in greeter just fine
[21:08] <kgunn> cool thanks for testing mterry
[21:16] <Cimi> kgunn, I'd love to have bug reports instead blueprints...
[21:16] <kgunn> Cimi: noted
[21:16] <Cimi> kgunn, they have milestones, priorities… they get automatically updated when they land!
[21:17] <Cimi> and they show up in +upcomingwork on launchpad :)
[21:17] <kgunn> Cimi: yep....there's vices and virtues to everything...bp's have this http://status.ubuntu.com/ubuntu-s/
[21:18] <kgunn> Cimi: i hope to have an opportunity to discuss with upper management
[21:18] <kgunn> i get the fact bugs "make more sense" to the individual
[21:18] <Cimi> kgunn, I generally don't like duplicated work, and blueprints/bugs feel like dup
[21:18] <kgunn> i think bugs could be massaged into being more closely like bp's
[21:18] <Cimi> kgunn, I think we should use BP only for small amount of things without a specific bug
[21:19] <Cimi> at least we don't have kanban anymore :)
[21:20] <Cimi> kgunn, speaking of upcoming work, I have still on my list the calendar for sdk
[21:20] <Cimi> kgunn, the calendar landed in ubuntu-settings-components, do we want to extract it and put in the SDK?
[21:20] <kgunn> Cimi: yep...actually i was just doing bp's...you have more than that
[21:20] <kgunn> :)
[22:27] <Saviq> veebers, hey
[22:27] <Saviq> veebers, care to comment/respond on https://code.launchpad.net/~doanac/phablet-tools/unlock_screen/+merge/191268/comments/439588 ?
[22:27] <veebers> HI Saviq , sure will look now
[22:28] <Saviq> veebers, I don't want to another more place that keeps a blind unity8 unlock
[22:28] <Saviq> we can do it right, it's not that much more work
[22:30] <veebers> Saviq: right, the code is already in the greeter emulator and we do it in the unity8 tests
[22:31] <Saviq> veebers, yeah, we just need to make it consumable from the outside
[22:31] <Saviq> veebers, we just need a Unity8 emulator with a "unlock" method
[22:32] <Saviq> veebers, that will take care of everything that's needed (restart unity8 if not under testability, wait for it, unlock), and return for the other suite to just continue
[22:33] <veebers> Saviq: hmm, I'm not sure about just restarting the shell, it's the same discussion that we had with the unity8 tests restarting the shell (ownership of the environment)
[22:33] <Saviq> veebers, sure, we could say you need to do it yourself
[22:33] <Saviq> veebers, I think we said that before - that the test harness should just set-env QT_LOAD_TESTABILITY=1
[22:34] <Saviq> and restart unity8 - basically start the phone with testability all over
[22:34] <Saviq> veebers, and then the emulator would just find the running unity8 and unlock it, and give the reins back to the app
[22:35] <veebers> Saviq: I agree with the idea, just wasn't sure about where the 'restart the shell' part should go
[22:35] <Saviq> veebers, we do need to make sure that it's possible to run them outside of unity8 - so if the emulator doesn't find unity8 running, maybe a custom exception to-be-caught by whoever uses the emulator
[22:36] <Saviq> veebers, and if they decide it's fine, just continue - or bail out if it's actually required for the test to be ran under unity8
[22:36] <veebers> Saviq: makes sense, I'm just writing something now like you described, shouldn't be too much to do
[22:36] <Saviq> veebers, cool
[22:44] <veebers> Saviq: just a thought, in the context of the unlocking the restarting of unity should reside in with the user or the calling testcase, this is so it can be cleaned up easily. (emulators don't have a n addCleanup)
[22:44] <Saviq> veebers, sure, we just said that, didn't we :D
[22:45] <veebers> Saviq: yeag, I guess so :-P oops
[22:45] <Saviq> veebers, that to use the emulator - you need to make sure unity8 is testable
[22:45] <Saviq> veebers, we can still provide utility functions for that
[22:46] <Saviq> veebers, so that we control how that happens
[22:46] <Saviq> veebers, or well, if we say people need to prepare (i.e. set-env manually), that's fine with me, too, probably
[22:46] <Saviq> veebers, will you respond to doanac please?
[22:46] <veebers> Saviq: sure can do
[22:50] <veebers> Saviq: fyi as per comment I filed: https://bugs.launchpad.net/unity8/+bug/1240261
[22:50] <veebers> might need it's tags tweaked
[22:50] <Saviq> veebers, thanks
[22:50] <veebers> nw
[22:57] <veebers> Saviq: heres a thought, if we're wanting to provide something for tests to use to unlock the greeter and restart unity if required, they are going to have to have unity8-autopilot installed right?
[22:57] <veebers> Why not just get their testsuites to inherit from UnityTestCase and they can do what the unity8 tests do: self.launch_unity(); self.main_window.get_greeter().swipe()
[22:58] <veebers> that way we don't need to add anything.
[22:58] <Saviq> veebers, testing on desktop
[22:58] <Saviq> veebers, I'd rather not tie them that much
[22:58] <veebers> we could still add the unlock emulator part for those that want to take care of the restarting of unity etc.
[22:59] <Saviq> veebers, I'd rather provide a very simple .prepare_unity8() or something
[22:59] <Saviq> veebers, so that it's *us* that know what that entails
[22:59] <Saviq> veebers, and in case things change, we don't have to chase apps
[23:00] <Saviq> veebers, the tests should also run if you *don't* use that emulator to unlock (say you unlocked manually, 'cause your phone is password-protected)
[23:00] <Saviq> and I dare say - even when unity8 suite is not installed
[23:03] <Saviq> veebers, I'm thinking of it more like of a helper
[23:03] <veebers> Saviq: hmm ok, was a thought. I should have a MR up for discussion in a little bit if you'll still be around
[23:04] <Saviq> veebers, 1am here, probably not ;)
[23:04] <Saviq> veebers, but will definitely look tomorrow
[23:04] <veebers> hah, I never know when you'll be around Saviq :-)
[23:04] <Saviq> true, true ;)
[23:04] <Saviq> don't get used to it, though, it's not gonna continue past release day :D
[23:04] <veebers> Saviq: awesome, I'll try get other eyes etc. get it as far as possible
[23:04] <veebers> Saviq: heh, will you be sleeping for a week?
[23:05] <Saviq> veebers, that might *just* happen indeed