[13:01] <RAOF> mariogrip: Hm. Yeah, that's clearly not working right.
[13:02] <RAOF> mariogrip: I continue to not have access to my nvidia machine; I won't until next week.
[13:05] <mariogrip> RAOF: ok, i'll try "hacking" on it a bit an see what i can do, i'll ping you if i get something new
[13:05] <RAOF> It doesn't look like anything is actually rendering there; it looks like you've just got bits of previously-initialised vram being scanned out of.
[13:06] <RAOF> This is not something I encountered while developing, so I'm not sure what's causing it. :)
[13:08] <mariogrip> but, do you have an idea what the link error can be? http://paste.ubuntu.com/17103216/ that happens when i try to start the server or mir_demo_standalone_render_surfaces.
[13:14] <RAOF> mariogrip: Oh! That's from src/renderers/gl/program_family.cpp - it's failing to link a shader.
[13:14] <RAOF> That's likely the reason you're not seeing any rendering :)
[13:15] <mariogrip> RAOF: oh? how do i fix that?
[13:15] <RAOF> It would be nice if the driver returned any sort of reason for that link failure - we capture any failure message they provide...
[13:15] <RAOF> mariogrip: I don't know what shader it is, nor why it's failing to link; I'm not sure how you'd fix that. Probably work out what shader is trying to link would be a first go :)
[13:17] <mariogrip> ok :)
[14:43] <alan_g> greyback: https://code.launchpad.net/~alan-griffiths/miral/WindowManagementPolicy-advise_raise/+merge/296799
[14:44] <greyback> alan_g: thanks
[15:20] <alan_g> greyback: the simple part: https://code.launchpad.net/~alan-griffiths/miral/WindowManagementPolicy-advise_move_to/+merge/296805
[16:27] <alan_g> greyback: https://code.launchpad.net/~alan-griffiths/miral/WindowManagementPolicy-advise_begin-end/+merge/296817
[17:43] <alan_g> anpok: back
[17:44] <anpok> alan_g: unset QT_QPA_PLATFORMTHEME
[18:24] <alan_g> anpok: https://code.launchpad.net/~alan-griffiths/miral/fix-running-Qt-apps/+merge/296838