http://bugzilla.opensuse.org/show_bug.cgi?id=1036342 http://bugzilla.opensuse.org/show_bug.cgi?id=1036342#c2 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org, | |markos.chandras@suse.com Flags| |needinfo?(markos.chandras@s | |use.com) --- Comment #2 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Markos Chandras from comment #0)
Hi,
Ever since I updated to 20170424 I can't get gnome session to start. gdm is stuck in an infinite loop and I can see the following issue on dmesg
[ 209.298800] gnome-session-f[2668]: segfault at 0 ip 00007fb96a6e78a9 sp 00007ffc3a8734b0 error 4 in libgtk-3.so.0.2200.11[7fb96a3f8000+708000] [ 256.323964] gnome-session-f[3378]: segfault at 0 ip 00007f7a6bfe08a9 sp 00007ffd9c426de0 error 4 in libgtk-3.so.0.2200.11[7f7a6bcf1000+708000]
I can't tell if the previous snapshot worked for me because I haven't update in a while. Please let me know if you need more information from me
That seems not to be gnome-session crashing, but actually gnome-session-failed, which means even if it would not crash, you'd not be happy: you would simply see the 'Something has gone wrong" screen. If you are running in a wayland session, then it is known that gnome-session-failed does not work (if gnome-shell crashed/failed to start, there is no wayland compositor and hence nothing gtk3 could paint on) So in short: the crash you see is 'not nice', but is not the root of you not having a GNOME session running. Please get more information from your journal to actually trace the root cause -- You are receiving this mail because: You are on the CC list for the bug.