[07:48] <DonkeyHotei> so i installed unity8-desktop-session-mir like you said, and now i get only a text console
[07:48] <DonkeyHotei> oops, bad copypaste
[07:49] <DonkeyHotei> anyway, does mir have logs?
[07:51] <RAOF> DonkeyHotei: You can find some in /var/log/lightdm and ~/.cache/upstart/
[08:01] <DonkeyHotei> RAOF: looks like lightdm and plymouth just aren't even started anymore
[08:11] <DonkeyHotei> can someone tell me what's going on?
[08:16] <DonkeyHotei> nvm
[12:16] <anpok> yay egl_configs
[12:16] <anpok> +no
[13:22] <alan_g> greyback: Saviq - thoughts? https://code.launchpad.net/~vanvugt/mir/fatal-error/+merge/219471/comments/532638
[14:09] <chrisccoulson> does the mir egl backend in mesa support pbuffer surfaces?
[14:10] <chrisccoulson> actually, I think I already know the answer to this
[14:38] <greyback> alf_: you there?
[14:42] <alf_> greyback: yes
[14:44] <greyback> alf_: quick question: if I turn on framedropping for a Surface,does swap buffers block for vsync or not?
[14:45] <alf_> greyback: it should not block, are you seeing something different? (why are you enabling framedropping?)
[14:47] <greyback> alf_: I'm not, I just wanted to know how it behaves
[14:48] <greyback> alf_: so with Mir's renderer, if a surface is not visible, it is still the compositor that consumes the un-composited buffers generated by the client?
[14:51] <alf_> greyback: In mir/devel the BufferQueue for a client drops buffers itself, so the compositor is no longer involved
[14:51] <alf_> greyback: s/client/client surface/
[14:53] <greyback> alf_: oh that's great
[20:07] <DonkeyHotei> i get a black screen when i select the mir session in lightdm, how to troubleshoot?
[21:36] <DonkeyHotei> hello?
[21:42] <bschaefer> DonkeyHotei, for unity8 desktop session mir? On utopic? Or Trusty?
[21:42] <DonkeyHotei> trusty
[21:42] <bschaefer> check ~/.cache/upstart/unity8-*
[21:42] <bschaefer> should complain about something
[21:42] <bschaefer> or
[21:43] <DonkeyHotei> i'll pastebin it
[21:43] <bschaefer> /var/log/lightdm/unity-system-compositior
[21:43] <bschaefer> .log
[21:50] <DonkeyHotei> bschaefer: http://pastebin.com/YNB1qirT
[21:51] <bschaefer> DonkeyHotei, what version of lightdm are you running?
[21:51] <DonkeyHotei> whatever trusty has
[21:52] <bschaefer> as I *think* there was a fix put out for that in 1.11.3
[21:52] <bschaefer> DonkeyHotei, apt-cache policy lightdm
[21:52] <DonkeyHotei> 1.10.1-0ubuntu1
[21:52] <bschaefer> as if you are running unity-system-compositor version 0.3, and only lightdm version 1.11.2 you'll get a black screen
[21:53] <bschaefer> hmm
[21:53] <bschaefer> could you do apt-cache policy unity-system-compositor
[21:54] <DonkeyHotei> 0.0.2+14.04.20140411-0ubuntu1
[21:55] <bschaefer> DonkeyHotei, shouldn't be the issue then
[21:55] <bschaefer> DonkeyHotei, looking at bugs: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1304959
[21:55] <bschaefer> that one seems to match your assert
[21:55] <bschaefer> in your log
[21:55] <bschaefer> the
[21:55] <bschaefer> ASSERT: "(eglContext_ = eglCreateContext( eglDisplay_, screen->eglConfig(), share ? share->eglContext() : EGL_NO_CONTEXT, attribs.constData())) != EGL_NO_CONTEXT" in file ../../../../src/platforms/base/context.cc, line 63
[21:55] <bschaefer> bit
[21:56] <bschaefer> so its failing to create an eglContext :(
[21:56] <bschaefer> DonkeyHotei, did you have this working before?
[21:56] <DonkeyHotei> no
[22:01] <bschaefer> DonkeyHotei, it might be worth while to post on the bug report that you can reproduce this issue with your specs + unity8-mir log
[22:01] <bschaefer> to hopefully get something rolling agian
[22:01] <bschaefer> again*
[22:06] <DonkeyHotei> here is /var/log/lightdm/unity-system-compositior.log:
[22:06] <DonkeyHotei> GL_VENDOR = Intel Open Source Technology Center
[22:06] <DonkeyHotei> GL_RENDERER = Mesa DRI Intel(R) 945GME x86/MMX/SSE2
[22:06] <DonkeyHotei> GL_VERSION = OpenGL ES 2.0 Mesa 10.1.3
[22:06] <DonkeyHotei> dm_connection_start
[22:06] <DonkeyHotei> Unable to set active session, unknown client name
[22:06] <DonkeyHotei> set_active_session 'x-0'
[22:06] <DonkeyHotei> set_active_session
[22:06] <DonkeyHotei> set_active_session 'session-0'
[22:06] <DonkeyHotei> set_active_session
[22:06] <DonkeyHotei> Unable to set active session, unknown client name session-0
[22:07] <DonkeyHotei> pause
[22:07] <bschaefer> DonkeyHotei, yeah, the unity8-mir log tells us what the issue is
[22:08] <bschaefer> it hit an ASSERT because it was unable to create an egl context
[22:08] <bschaefer> (which is pretty bad)
[22:10] <DonkeyHotei> i can't change the status from won't fix
[22:11] <bschaefer> yes, but adding comments helps others see its still an issue (with other machines?)
[22:15]  * bschaefer will be back in ~15 min
[22:54] <DonkeyHotei> bschaefer: found this too: https://bugs.launchpad.net/mir/+bug/1275398
[22:54] <bschaefer> DonkeyHotei, yours is a bit different, thats a black screen but the eglContext is still being created
[22:55] <bschaefer> in your case, you hit an assert and the program stops running
[22:55] <bschaefer> (so you wont get the FPS stdout)
[22:56] <bschaefer> DonkeyHotei, i moved that other bug back to confirmed, as if its old hardware, its still an issue
[22:56] <bschaefer> vs a "We wont fix" but it wont be a focus atm though
[22:58] <DonkeyHotei> the won't fix was set by the original reporter
[22:58] <bschaefer> yes, which doesn't make much sense either, as its still confirmed :)