[10:48] <Saviq> greyback_, icanhastest for setFullscreen(false) please?
[10:53] <greyback_> Saviq: setFullscreen?
[10:53] <Saviq> greyback_, uhm
[10:54] <Saviq> setFocused(false)
[10:54] <greyback_> I saw the comment
[10:54] <Saviq> kk
[10:54] <greyback_> I was going to, then thought it a lightly ridiculous test
[10:55] <greyback_> ofc setFocused(false) should not grab a wakelock
[10:55] <Saviq> greyback_, why? can't you have a test that reproduces what we saw yesterday?
[10:55] <Saviq> greyback_, well, it does, currently, doesn't it ;)
[10:55] <greyback_> yeah, was bad code
[10:56] <Saviq> greyback_, and what if we get bad code again? why can't there be a unit test failing then?
[10:57] <greyback_> I know you're right, but the test I'd write would effectively be "test if an "if" statement works"
[10:57] <Saviq> greyback_, can it not be a more high level test, testing that if you launch a lifecycle-exempt app and unfocus it, that there's no wakelock held?
[10:58] <Saviq> which is what we saw happen yesterday?
[10:58] <greyback_> yeah alright
[11:07] <greyback_> Saviq: pushed
[11:07] <Saviq> greyback_, tx
[14:19] <dandrader> Saviq, ping
[14:19] <Saviq> dandrader, here
[14:20] <dandrader> Saviq, do you think we would need a feature freeze exception to merge qtmir/port-to-mirevent2.0 + qtubuntu/use-mirclient?
[14:23] <Saviq> dandrader, think it should be fine
[14:23] <Saviq> dandrader, one thing greyback_ pointed out yesterday is that might mean some changes to unity8 to still support mouse properly?
[14:39] <dandrader> Saviq, if you wrote something back I didn't receive it as my router stopped working and needed a reboot
 dandrader, think it should be fine
[14:41] <Saviq>  dandrader, one thing greyback_ pointed out yesterday is that might mean some changes to unity8 to still support mouse properly?
[14:42] <dandrader> Saviq, yeah, some MouseAreas to avoid the regression where the indicators panel would not be draggable with a mouse
[14:42] <dandrader> Saviq, mzanetti has a a simple MP for that, which would be landed along with those other two
[14:42] <dandrader> Saviq, sounds like a plan?
[14:42] <Saviq> dandrader, sure
[14:44] <dandrader> Saviq, ok, after I'm done with my current task I will build all of those in my device and let you know it's working well. would that help you? (I don't have landing powers, so don't know how to help in getting it landed)
[14:45] <dandrader> s/it's working well/if it's working well
[14:45] <Saviq> dandrader, just have MPs around and I'll build it all in silo
[14:46] <mzanetti> dandrader, Saviq: I had a chat with Jouni yesterday. He'll get us some design on what to do with the dragarea in the indicators for the mouse case. for now we should just add that simple mouse area so we can open them by clicking.
[14:46] <Saviq> +1
[14:47] <dandrader> Saviq, so here they are: lp:~mir-team/qtubuntu/port-to-mirclient, lp:~mir-team/platform-api/expose-mir-connection, lp:~mir-team/qtmir/port-to-event-2.0 and lp:~mzanetti/unity8/indicators-mouse
[14:47] <Saviq> dandrader, ok, will put those in silos soon
[14:47] <dandrader> mzanetti, do you still consider  lp:~mzanetti/unity8/indicators-mouse as "work in progress"?
[14:47] <dandrader> Saviq, ok, thanks
[14:48] <mzanetti> dandrader, no... lemme change
[14:50] <mzanetti> dandrader, Saviq: updated the branch
[14:50] <mzanetti> https://code.launchpad.net/~mzanetti/unity8/indicators-mouse/+merge/250429
[14:51] <Saviq> kk
[14:53] <dandrader> mzanetti, nice, thanks. will review it soon (today or on Monday). Unless someone else does it first :)
[14:53] <mzanetti> cheers
[14:53] <Saviq> huh, mzanetti can you repro bug #1426399 ?
[14:53]  * mzanetti tries
[14:56] <mzanetti> Saviq, can repro except the "short time"
[14:56] <mzanetti> ah no
[14:56] <mzanetti> I hit the mouse accidentally
[14:57] <mzanetti> so it was doing the transition to windowed mode
[14:57] <mzanetti> Saviq, however, pressing the play buttin will probably activate the telephony stuff
[14:57] <Saviq> mzanetti, yeah, that's what I was thinking
[14:58]  * tsdgeos has found a deadlock in qtbus on startup :/
[14:59] <seb128> mzanetti, hey
[14:59] <mzanetti> seb128, hi
[14:59] <seb128> mzanetti, on my current vivid/unity-desktop the launcher doesn't display when hitting the screen corner with a mouse, is that normal?
[14:59] <seb128> the package changelog suggest support for that has been added
[15:00] <mzanetti> seb128, yeah, need a update of mir
[15:00] <mzanetti> seb128, right now Mir doesn't give us Mouse events (except for silo0)
[15:00] <seb128> oh ok
[15:00] <a1fa> hello.. is there anyway to benchmark 2d performance of unity?
[15:00] <seb128> mzanetti, thanks
[15:00] <a1fa> i feel like my dekstop is lugging a bit
[15:00] <seb128> mzanetti, is that in mir 0.12 which is pending landing?
[15:00] <a1fa> are there any built in counters, one can refer to?
[15:01] <a1fa> r9 290 with flgrx drivers
[15:01] <mzanetti> seb128, not sure exactly, I think it's this branch: https://code.launchpad.net/~mir-team/qtmir/port-to-event-2.0/+merge/248067
[15:01] <mzanetti> and its dependencies
[15:02] <seb128> mzanetti, k, thanks
[15:02] <a1fa> example: resizing windows is very choppy
[15:04] <mzanetti> Saviq, this does happen here, but only on the first time you press that button after the device boots
[15:05] <mzanetti> re play button
[15:05] <Saviq> mzanetti, can you comment on bug and get telephony folk to comment
[15:05] <mzanetti> ack
[15:06] <Saviq> mzanetti, if anything, the function call we use to let them know about this should be async
[15:07] <mzanetti> yeah
[15:07] <mzanetti> Saviq, thing is, it has a return value
[15:07] <mzanetti> and we probably want that
[15:07] <Saviq> mzanetti, right, then we need to put it in a WorkerScript or something
[15:07] <mzanetti> yeah...
[15:08] <a1fa> anyone?
[15:08] <a1fa> resizing windows: very slow and bad...
[15:08] <a1fa> moving windows around: fast, no chopiness
[15:09] <Saviq> a1fa, is that any app, or one in particular?
[15:09] <a1fa> good example file manager
[15:09] <a1fa> with no files on the screen
[15:09] <a1fa> maybe 3-4 directories
[15:09] <a1fa> (Home Directory)
[15:10] <Saviq> Trevinho, any ideas for a1fa ↑? window resize is slow for him
[15:10] <a1fa> it's most windows like that
[15:10] <a1fa> i'm on 14.10 x64
[15:10] <Saviq> mzanetti, what was your issue with device-upgrade 0?
[15:10] <a1fa> 16GB DDR3
[15:10] <Trevinho> mhm... what driver are you using?
[15:11] <Trevinho> a1fa: ^
[15:11] <a1fa> Trevinho: flgrx
[15:11] <a1fa> i tried flgrx-update
[15:11] <a1fa> same thing
[15:11] <mzanetti> Saviq, don't remember... I did normal dist-upgrades lately
[15:11] <Saviq> mzanetti, dude :P
[15:11] <mzanetti> ...
[15:11] <Trevinho> a1fa: that's weird, I didn't head of that since we introduced new decorations...
[15:11] <mzanetti> either those scripts work or they don't
[15:11] <mzanetti> this doesn't for me
[15:11] <Saviq> "this"?
[15:11] <Trevinho> a1fa: does it happen for any window or just filemanager?
[15:11] <mzanetti> ci-train
[15:11] <a1fa> Trevinho: any window
[15:12] <Saviq> mzanetti, 100% success rate here
[15:12] <mzanetti> and doing normal upgrades does work and is not much more to type
[15:12] <mzanetti> 98% fail rate here
[15:12] <Saviq> except it will break often
[15:12] <Saviq> mzanetti, so there's something you're doing differently
[15:12] <mzanetti> didn't work for kgunn either, and for many others working on silo0
[15:13] <a1fa> 1920x1080
[15:13] <Saviq> mzanetti, it's usually useful to _report_ a tool failure like that
[15:13] <Trevinho> a1fa: mh, it's quite hard to debug.. but you might give a try to run callgrind with unity and compiz debug symbols installed... So we could have some measurement
[15:13] <Saviq> that tool is supposed to work - if it doesn't, we should fix it, not silently go and do other things
[15:13] <Trevinho> a1fa: as a workaround you can switch back to a different resize method in CCSM for now I guess
[15:13] <a1fa> Trevinho: i think this is just 1 side effect
[15:14] <a1fa> Trevinho: the entire experience feels a bit lagged
[15:14]  * Saviq hates "oh it isn't working, but I don't remember why/how" >:[
[15:14] <Trevinho> ah, ok.. so that's another thing
[15:14] <a1fa> oddly, shaking the windows around works fine
[15:14] <a1fa> no lag what so ever
[15:14] <a1fa> its mostly obvious in resizing windows
[15:14] <a1fa> my rdp session also feels strange
[15:15] <Trevinho> mh, well, I've no experience with fglrx here, I've always used radeon driver... can you try to use that and check if you get the same?
[15:15] <kgunn> Saviq: there's a bug https://bugs.launchpad.net/mir/+bug/1408827
[15:15] <kgunn> in the wrong place :-.
[15:15] <a1fa> sure
[15:16] <Saviq> kgunn, yeah, was it the same with mir 0.12 (silo 7)?
[15:16] <a1fa> be in about 2-3 mintues
[15:16] <a1fa> waiting for download to finish
[15:17] <a1fa> Trevinho: no need to reboot between driver switch? just cycle x?
[15:17] <kgunn> kdub: ^ did you test using ctrain device-upgrade?  or did you apt-add-repository with your testing ?
[15:17] <kdub> citrain
[15:17] <kdub> kgunn,
[15:17] <kgunn> ah...and all was good, did you check the package names and verify everything you expected to be installed was ?
[15:18] <kgunn> kdub: ^
[15:18] <kdub> yes, and I think I just used dist-upgrade on my desktop check
[15:18] <kdub> with apt-add-repository
[15:18] <kdub> and citrain on the devices
[15:19] <kgunn> kdub: as long as you verified the pkgs installed...
[15:19] <kgunn> i'm gonna close this https://bugs.launchpad.net/mir/+bug/1408827
[15:19] <kgunn> and open a new one
[15:19] <a1fa> Trevinho: i also noticed a slight issue with the right menu bar.. when it hides, it does not want to show up sometimes.. you can hover all you want
[15:19] <kgunn> for silo 0
[15:19] <kdub> kgunn,  yep, I did check that the numbers were correct
[15:19] <kgunn> kdub: thanks for the extra effort
[15:20] <Trevinho> a1fa: any app, same issue?
[15:20] <Trevinho> a1fa: pressing Alt is the same?
[15:20] <a1fa> alt works
[15:20] <a1fa> sometimes its firefox, sometimes terminal
[15:21] <a1fa> i switched the driver
[15:21] <a1fa> do i need to recycle X or reboot?
[15:21] <Trevinho> as for switching the driver, you can also do it without rebooting, but you need to unload/reload the proper kernel drivers, and I'm not sure whether it will work (I did this in the past, but I don't know how things are now)
[15:21] <Saviq> kgunn, so most probably what happened with the bug above was that mir had a new dependency that wasn't in the image, that citrain can't deal with yet (and why we have libevdev in silo 0)
[15:22] <a1fa> ok let me reboot
[15:22] <kgunn> right
[15:22] <a1fa> no biggie
[15:22] <a1fa> brb
[15:23] <Saviq> kgunn, btw, bug #1378245
[15:23] <a1fa> same thing
[15:25] <a1fa> it's not any better Trevinho
[15:26] <Trevinho> a1fa: ensures you're on mesa, right /usr/lib/nux/unity_support_test -p ?
[15:27] <a1fa> http://paste.debian.net/158194/
[15:27] <Saviq> mzanetti, so, please try citrain again next time you flash, and if there's an issue, let me know
[15:27] <mzanetti> Saviq, ok
[15:28] <kgunn> Saviq: mzanetti ...i'm gonna try it clean right now
[15:28] <kgunn> verify all pkg versions
[15:30] <a1fa> i will re-enable the driver and try it again
[15:32] <a1fa> http://paste.debian.net/158201/
[15:33] <a1fa> here it is with the driver enabled
[15:35] <a1fa> Trevinho: should i disable tear-free desktop?
[15:35] <Trevinho> a1fa: it's still using fglrx, not radeon (mesa)...
[15:36] <Trevinho> a1fa: mh, no I don't think that's the thing
[15:36] <Trevinho> a1fa: I guess you've to uninstall fgrlx not to make them to override mesa
[15:36] <a1fa> Trevinho: i tried it with mesa
[15:36] <Trevinho> but not sure...
[15:36] <Trevinho> ah, ok
[15:36] <a1fa> i posted the pastebin earlier
[15:36] <a1fa> it was the same issue if not worse
[15:36] <Trevinho> yeah, sorry... missded it
[15:37] <Trevinho> but well... a1fa that was not using the radeon driver either, but software rendering
[15:37] <Trevinho> (llvmpipe), maybe your card is not supported or there's some misconfiguration
[16:32] <tsdgeos> https://twitter.com/MEIZU/status/571329515391025152 :)
[17:24] <charles> Saviq, ping
[17:24] <Saviq> charles, pong
[17:25] <a1fa> Trevinho: i updated to 15.04, and same issue :(
[17:25] <a1fa> + now there are more issues with Term
[17:25] <charles> Saviq, I've been experiencing a launcher ui bug off & on this week and was wondering who would be the right person to report it to
[17:25] <Saviq> charles, hit me
[17:25] <charles> Saviq, the behavior is that sometimes the launcher can't be pulled onto the screen, even though other edges seem to work (eg, being able to drag the indicators down from the top of the screen)
[17:26] <Saviq> charles, how about the right edge? and is that mako?
[17:26] <charles> Saviq, right edge also fails. Yes, mako running nightly vivid images
[17:26] <Saviq> charles, bug #1408263
[17:26] <charles> persists if you go to lock screen and then unlock, the only workaround I found is a reboot
[17:26] <charles> Saviq, cool, thanks :)
[17:27] <Saviq> charles, unfortunately it's a mako input driver issue...
[17:27] <Saviq> charles, for whatever reason the input area "grows" out of the device
[17:27] <davmor2> Saviq: that and vivid isn't very stable right now
[17:29] <charles> ugh, reading your writeup in comment #10 now
[18:39] <dandrader> mzanetti, you there?
[18:41] <mzanetti> dandrader, about to leave
[18:41] <om26er> Saviq, Hi! on vivid I installed unity8, it does not start. I get this http://paste.ubuntu.com/10453316/
[18:41] <om26er> what am I missing ?
[18:41] <dandrader> ah, no problem then. just to mention that I made this https://code.launchpad.net/~dandrader/unity8/controlTouchEmulationFromQML/+merge/251308
[18:41] <dandrader> mzanetti, to test your branch
[18:42] <dandrader> om26er, that comes from qtmir
[18:42] <dandrader> om26er, where and how are you running it?
[18:43] <om26er> dandrader, on a desktop running vivid. I installed unity8-desktop-session-mir
[18:43] <om26er> dandrader, it installed all the deps but unity8 won't start
[18:43] <om26er> qtmir-desktop is also installed.
[18:46] <dandrader> hmm, sorry, can't help there. I don't even remember the last time I tried to run it in a desktop/laptop
[18:47] <mzanetti> dandrader, cool stuff!
[18:47] <mzanetti> will check it out on mon
[19:08] <Saviq> om26er, do you have qtmir-desktop installed>
[19:09] <om26er> Saviq, yes its installed
[19:09] <om26er> version is 0.4.4+15.04.20150220-0ubuntu1
[19:09] <Saviq> om26er, and `dpkg -S libqpa-mirserver.so`
[19:09] <om26er> Saviq, qtmir-desktop:amd64: /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
[19:10] <om26er> Saviq, I would try silo0 but seems it got outdated
[19:12] <Saviq> om26er, ok, so something's weird, how are you trying to start unity8? just the session from lightdm?
[19:12] <om26er> Saviq, both ways. from command line `unity8` also tried to login from lightdm, just gave me black screen.
[19:13] <om26er> plus this is a clean install of 15.04
[19:13] <Saviq> om26er, and just going "unity8" on the command line gives you that error?
[19:13] <Saviq> in an X session?
[19:13] <om26er> Saviq, yes
[19:14] <Saviq> om26er, you got unity8-touch-session installed by any chance?
[19:14] <om26er> Saviq, I have unity8-desktop-session-mir
[19:14] <Saviq> om26er, `env | grep QPA`?
[19:15] <om26er> Saviq, QT_QPA_PLATFORMTHEME=appmenu-qt5
[19:15] <om26er> nothing else.
[19:15] <Saviq> om26er, okay, that sounds stupid
[19:15] <Saviq> om26er, ah, to run under X11, you want `unity8-fake-env`
[19:16] <om26er> Saviq, ok, that works. So black screen from lightdm is another issue then ?
[19:16] <Saviq> om26er, yes
[19:17] <Saviq> om26er, you want to clear /var/log/lightdm and ~/.cache/upstart/*, try logging in to the unity8 session and see if you got any new interesting failrues
[19:17] <Saviq> om26er, note that guest session doesn't work yet
[19:18] <om26er> trying, brb.
[19:20] <om26er> Saviq, this time unity8 started from lightdm
[19:20] <om26er> :)
[19:21] <om26er> didn't find a graceful way to get back to X11
[19:26] <Saviq> om26er, that's bug #1360316
[19:27] <Saviq> om26er, if you confirm that you can't get it to start without unity8-fake-env, that would be a problem, please file a bug for us
[19:27] <om26er> Saviq, ok, let me try to remote that package and try logging into mir session
[19:28] <Saviq> thanks