http://bugzilla.suse.com/show_bug.cgi?id=1125760 http://bugzilla.suse.com/show_bug.cgi?id=1125760#c9 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com Component|X11 3rd Party Driver |GNOME Assignee|sndirsch@suse.com |bnc-team-gnome@forge.provo. | |novell.com QA Contact|sndirsch@suse.com |qa-bugs@suse.de --- Comment #9 from Stefan Dirsch --- (In reply to Hadrien Grasland from comment #6)

Checking the original journalctl log again, I noticed that there is a gdm crash report before the first X initialization log (gdm is started at line 1446 and crashes due to not finding a display at line 1525, whereas the first X11 initialization log starts at line 1576). Maybe there is some kind of X11 / gdm startup race going on there ? Or maybe the X11 initialization logs are just sent to the journal at a later time...

Thanks for closer looking at it yourself! Line 1525 févr. 18 11:16:58 linux-2ak3 gnome-shell[1572]: Failed to create backend: No GPUs with outputs found My current guess is, that gdm is trying to figure out here, whether your GPU is capable of support Wayland or not. Indeed detecting no GPU looks fatal. Anyway our GNOME developers need to look at this with other displaymanagers like lightdm not being affected by this. -- You are receiving this mail because: You are on the CC list for the bug.