[09:54] <alan_g> alf__: I guess this is no linger needed? https://code.launchpad.net/~afrantzis/mir/always-consume-input-events-in-clients/+merge/209313
[09:54] <alf__> alan_g: affirmative
[10:01] <hikiko> hello
[10:03] <hikiko> I am trying to run mir on nvidia, I have loaded and installed the nouveau driver (checked with lsmod that there is no other nvidia driver) and when I run the mir server basic demo, I get a message that gbm failed to load the nouveau driver... (nvidia GF188 [GeForce GT 440])
[10:04] <hikiko> does anyone else have the problem?
[10:04] <hikiko> is there anything I can do to fix it?
[10:04] <RAOF> Hey!
[10:04] <RAOF> I... think that card should be supported by nouveau?
[10:04] <RAOF> Does X work properly?
[10:05] <hikiko> yes RAOF
[10:05] <hikiko> X is fine
[10:05] <RAOF> And glxinfo under X shows that it's using nouveau?
[10:06] <hikiko> let me check
[10:07] <hikiko> well if I run: glxinfo | grep -i nouveau
[10:08] <hikiko> I gett libGL error: failed to open drm device: Permission denied libGL error: failed to load driver nouveau
[10:09] <hikiko> (i ran startx though so it might be just permissions let me check in unity7)
[10:10] <hikiko> yep
[10:10] <hikiko> when i start unity from lightdm
[10:10] <hikiko> i get OpenGL vendor string: nouveau
[10:11] <RAOF> Cool. Hm...
[10:18] <duflu> Look over there!
[10:18]  * duflu runs away
[10:20] <hikiko> :P
[10:23] <hikiko> in /usr/lib/x86_64-linux-gnu/dri I have a nouveau_dri.so (and a nouveau_vieux_dri.so) if that helps
[10:23] <hikiko> so it should find it
[15:43] <alan_g> alf__: @fix-1260612 - it is an improvement. Should I approve and log a bug for the not-working scenario? Or do you have a clue how to fix?
[15:47] <alf__> alan_g: No clue, but I will keep investigating. Feel free to log a different bug if you like and assign it to me.
[15:49] <alf__> alan_g: hmm, you are running shell as host basic as nested, I am running basic as host shell as nested.
[15:51] <alan_g> alf__: I've tried your scenario with "_shell" and "_basic" as the nested server. The latter shows the problem I saw. Not sure why there's a difference though.
[15:52] <alan_g> I'll approve the MP - it seems to be a "_basic" bug
[15:56] <alf__> alan_g: well, basic doesn't support resizing or moving gestures, in the shell==host scenario we are moving/resizing the whole nested window, and I am not sure if resizing means scaling or cropping in this case
[15:59] <alan_g> alf__: I think some /examples gardening is required - who can remember these differences. But explained to my satisfaction
[16:01] <alf__> alan_g|tea: so, yes, we seem to be cropping in the shell==host scenario (if you "zoom in" hard enough you will see it)
[16:36] <kgunn> AlbertA: btw, i landed the usc change to have fuzzy time on screen blank...but i still see the app on unblank
[16:36] <kgunn> will our plan to move all the screen state in usc better address this ?
[16:36] <kgunn> AlbertA: what's weird is i know i saw it work once (e.g. saw only the lock screen)
[16:37] <AlbertA> kgunn: well you need to add the delay to a configuration file
[16:37] <AlbertA> kgunn: by default its 0
[16:37] <AlbertA> If you add /etc/xdg/unity-system-compositor.conf
[16:38] <AlbertA> with a power-off-delay=500 maybe
[16:39] <AlbertA> kgunn: but yes moving the screen state out of powerd will help here
[16:40] <AlbertA> kgunn: also for the power-off-delay to be "seen"
[16:41] <AlbertA> kgunn: you need this in powerd: https://code.launchpad.net/~albaguirre/powerd/let-display-turn-off-backlight/+merge/208667
[17:31] <mterry> alan_g, btw, I finally got a chance to test your nested-sessions-dont-post-buffers-until-something-happens branch (had to wait for 0.1.6 to settle first, was getting weird crashes before).  It works like a charm, thanks!
[17:32] <alan_g> mterry: \o/
[17:46] <ogra_> hmm, so after using mirscreencast it seems that the screen stopped auto-suspending
[17:49] <AlbertA> ogra_: hmm, interesting... I don't see why that would be the case from a mir perspective
[17:50] <ogra_> the screen was initially suspended ... running miscreencast properly woke it up too ... it just doesnt turn off again until i press the power button twice
[17:50] <AlbertA> ogra_: there must be some resource we are holding on the screencast compositor
[17:51] <ogra_> well, is that solely screencast or do you perhaps invoke powerd somewhere to get the display up
[17:53] <AlbertA> ogra_: there must be a display on - I think that was fixed recently - but not through powerd
[17:54] <ogra_> hmm, i could imagine that both processes start wrangling over owning the screen then or that powerd simply isnt aware the screen is on if you force it on from Mir
[17:54] <ogra_> (so it doesnt try to suspend it then)
[18:05] <AlbertA> ogra_: Oh I see, you started mirscreencast while the screen was off, then yeah, powerd wouldn't know about that
[18:06] <ogra_> AlbertA, yeah, not a biggie, but it would be good if they could communicate to each other about this
[18:06] <AlbertA> ogra_: In any case, we are ripping the screen power state out of powerd and putting it in usc
[18:06] <ogra_> ah, k
[18:06] <ogra_> thats will be fine then
[18:06] <AlbertA> ogra_: Also the forcing of display on will be removed if this lands:
[18:06] <AlbertA> https://code.launchpad.net/~robertcarr/mir/remove-ensure-display-powered/+merge/209734
[18:07] <ogra_> hmm, tests need this function
[18:07] <ogra_> you should talk to the QA guys about that, autopilot needs a way to force the screen on before starting its tests
[18:09] <AlbertA> racarr: ^
[18:26] <racarr_> ogra_: AlbertA: I think my branch is unrelated
[18:27] <racarr_> you guys need to be able to to force screen on externally
[18:27] <racarr_> like powerd-ctl or hatever it was called
[18:27] <racarr_> does
[18:27] <racarr_> which should still work for now? but maybe they got changed out
[18:27] <AlbertA> racarr_: well I think it's kinda related in that right now the screencast turns the screen on
[18:28] <racarr_> my branch is just about, clients which have explicitly turned the screen off
[18:28] <AlbertA> racarr_: I believe your MP will avoid that
[18:28] <racarr_> there was a behavior that automatically turns it back on when they swap buffers
[18:28] <racarr_> hmm
[18:28] <racarr_> maybe!
[18:28] <AlbertA> racarr_: which is good
[18:29] <racarr_> mm