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:48 |
DonkeyHotei | anyway, does mir have logs? | 07:49 |
RAOF | DonkeyHotei: You can find some in /var/log/lightdm and ~/.cache/upstart/ | 07:51 |
DonkeyHotei | RAOF: looks like lightdm and plymouth just aren't even started anymore | 08:01 |
DonkeyHotei | can someone tell me what's going on? | 08:11 |
DonkeyHotei | nvm | 08:16 |
=== pete-woods is now known as pete-woods-away | ||
=== alan_g is now known as alan_g|lunch | ||
anpok | yay egl_configs | 12:16 |
anpok | +no | 12:16 |
=== pete-woods-away is now known as pete-woods | ||
=== alan_g|lunch is now known as alan_g | ||
=== ara is now known as Guest42533 | ||
alan_g | greyback: Saviq - thoughts? https://code.launchpad.net/~vanvugt/mir/fatal-error/+merge/219471/comments/532638 | 13:22 |
chrisccoulson | does the mir egl backend in mesa support pbuffer surfaces? | 14:09 |
chrisccoulson | actually, I think I already know the answer to this | 14:10 |
greyback | alf_: you there? | 14:38 |
alf_ | greyback: yes | 14:42 |
=== alan_g|tea is now known as alan_g | ||
greyback | alf_: quick question: if I turn on framedropping for a Surface,does swap buffers block for vsync or not? | 14:44 |
alf_ | greyback: it should not block, are you seeing something different? (why are you enabling framedropping?) | 14:45 |
greyback | alf_: I'm not, I just wanted to know how it behaves | 14:47 |
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:48 |
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:51 |
greyback | alf_: oh that's great | 14:53 |
=== 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 | ||
DonkeyHotei | i get a black screen when i select the mir session in lightdm, how to troubleshoot? | 20:07 |
=== dandrader|lunch is now known as dandrader | ||
DonkeyHotei | hello? | 21:36 |
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:42 |
DonkeyHotei | i'll pastebin it | 21:43 |
bschaefer | /var/log/lightdm/unity-system-compositior | 21:43 |
bschaefer | .log | 21:43 |
DonkeyHotei | bschaefer: http://pastebin.com/YNB1qirT | 21:50 |
bschaefer | DonkeyHotei, what version of lightdm are you running? | 21:51 |
DonkeyHotei | whatever trusty has | 21:51 |
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:52 |
bschaefer | hmm | 21:53 |
bschaefer | could you do apt-cache policy unity-system-compositor | 21:53 |
DonkeyHotei | 0.0.2+14.04.20140411-0ubuntu1 | 21:54 |
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 |
ubot5 | Ubuntu bug 1304959 in unity8 (Ubuntu) "unity8 crashed with SIGABRT in qt_message_fatal()" [Critical,Won't fix] | 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:55 |
bschaefer | so its failing to create an eglContext :( | 21:56 |
bschaefer | DonkeyHotei, did you have this working before? | 21:56 |
DonkeyHotei | no | 21:56 |
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:01 |
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:06 |
DonkeyHotei | pause | 22:07 |
bschaefer | DonkeyHotei, yeah, the unity8-mir log tells us what the issue is | 22:07 |
bschaefer | it hit an ASSERT because it was unable to create an egl context | 22:08 |
bschaefer | (which is pretty bad) | 22:08 |
DonkeyHotei | i can't change the status from won't fix | 22:10 |
bschaefer | yes, but adding comments helps others see its still an issue (with other machines?) | 22:11 |
* bschaefer will be back in ~15 min | 22:15 | |
DonkeyHotei | bschaefer: found this too: https://bugs.launchpad.net/mir/+bug/1275398 | 22:54 |
ubot5 | Ubuntu bug 1275398 in Mir "i945: Mir GL clients are rendered as black or transparent windows when using i945 graphics" [High,Triaged] | 22:54 |
bschaefer | DonkeyHotei, yours is a bit different, thats a black screen but the eglContext is still being created | 22:54 |
bschaefer | in your case, you hit an assert and the program stops running | 22:55 |
bschaefer | (so you wont get the FPS stdout) | 22:55 |
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:56 |
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 :) | 22:58 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!