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