FS#51908 - [gnome-session] can't log into gnome on xorg since the change to wayland

Attached to Project: Arch Linux
Opened by Cédric Auger (cedric_a) - Monday, 21 November 2016, 05:35 GMT
Last edited by Jan de Groot (JGC) - Sunday, 03 December 2017, 23:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
I cannot log in "Gnome on Xorg" from gdm.

in my logs, i've a segfault from gnome-session-f :
gnome-session-f[17420]: segfault at 0 ip 00007f83a62ce1e9 sp 00007fff679529b0 error 4 in libgtk-3.so.0.2200.1[7f83a5fec000+6f2000]

the complete message :

Process 17420 (gnome-session-f) of user 1000 dumped core.

Stack trace of thread 17420:
#0 0x00007f83a62ce1e9 n/a (libgtk-3.so.0)
#1 0x00007f83a616a5f8 n/a (libgtk-3.so.0)
#2 0x00007f83a617f674 n/a (libgtk-3.so.0)
#3 0x00007f83a616b92c n/a (libgtk-3.so.0)
#4 0x00007f83a617f59c n/a (libgtk-3.so.0)
#5 0x00007f83a617f5f5 n/a (libgtk-3.so.0)
#6 0x00007f83a616c292 n/a (libgtk-3.so.0)
#7 0x00007f83a5ad730f g_type_create_instance (libgobject-2.0.so.0)
#8 0x00007f83a5ab91fb n/a (libgobject-2.0.so.0)
#9 0x00007f83a5abac0d g_object_newv (libgobject-2.0.so.0)
#10 0x00007f83a5abb3c4 g_object_new (libgobject-2.0.so.0)
#11 0x00007f83a6187ada n/a (libgtk-3.so.0)
#12 0x00007f83a63651c7 n/a (libgtk-3.so.0)
#13 0x00007f83a5ad730f g_type_create_instance (libgobject-2.0.so.0)
#14 0x00007f83a5ab91fb n/a (libgobject-2.0.so.0)
#15 0x00007f83a5abac0d g_object_newv (libgobject-2.0.so.0)
#16 0x00007f83a5abb3c4 g_object_new (libgobject-2.0.so.0)
#17 0x0000000000401db3 n/a (gnome-session-failed)
#18 0x00007f83a5413291 __libc_start_main (libc.so.6)
#19 0x00000000004021ba n/a (gnome-session-failed)

I'v read that :
https://bbs.archlinux.org/viewtopic.php?id=218580
https://bbs.archlinux.org/viewtopic.php?id=218168
https://bugs.archlinux.org/task/51791?project=1&cat%5B0%5D=2&string=mutter

there is the same problem, except downgrading mutter didn't change anything
and the fix on the 17/11 change nothing too.


Additional info:
my system is up to date today.

I precise that gnome on wayland works but crashes randomly and virtualbox crash...
I've tried to dowgrade gtk3 without any success.

i attached the xorg log and an export of journal.

Thanks
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 03 December 2017, 23:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  Segfault from initial bugreport was fixed.
Comment by G R (gururise) - Wednesday, 11 January 2017, 16:47 GMT
I have an Intel i7 3770k with an Nvidia Geforce 750ti.

I have validated that I have the latest intel microcode update, latest nvidia drivers and latest version of gnome packages & mutter. Every attempt to login via Gnome/Gnome Wayland/Gnome Classic just returns to the login screen and dmesg will show the segfault in gtk-3 as posted in the original bug report.

I am able to log in and use my computer with KDE Plasma desktop. Gnome Desktop does not work.
Comment by Paste Dubrow (Nolchetyre) - Thursday, 12 January 2017, 09:00 GMT
Can't login into gnome (pushes back to login screen). I'm able to login another WM, like i3.

journalctl -xk
kernel: gnome-session-f[3375]: segfault at 0 ip 00007f2deb90ecc9 sp 00007fff724f72b0 error 4 in libgtk-3.so.0.2200.6[7f2deb62c000+6fa000]

coredump process
Stack trace of thread 3375:
#0 0x00007f2deb90ecc9 n/a (libgtk-3.so.0)
#1 0x00007f2deb7aa9a8 n/a (libgtk-3.so.0)
#2 0x00007f2deb7bfa94 n/a (libgtk-3.so.0)
#3 0x00007f2deb7abcdc n/a (libgtk-3.so.0)
#4 0x00007f2deb7bf9bc n/a (libgtk-3.so.0)
#5 0x00007f2deb7bfa15 n/a (libgtk-3.so.0)
#6 0x00007f2deb7ac642 n/a (libgtk-3.so.0)
#7 0x00007f2deb11730f g_type_create_instance (libgobject-2.0.so.0)
#8 0x00007f2deb0f91fb n/a (libgobject-2.0.so.0)
#9 0x00007f2deb0fac0d g_object_newv (libgobject-2.0.so.0)
#10 0x00007f2deb0fb3c4 g_object_new (libgobject-2.0.so.0)
#11 0x00007f2deb7c7efa n/a (libgtk-3.so.0)
#12 0x00007f2deb9a5cb7 n/a (libgtk-3.so.0)
#13 0x00007f2deb11730f g_type_create_instance (libgobject-2.0.so.0)
#14 0x00007f2deb0f91fb n/a (libgobject-2.0.so.0)
#15 0x00007f2deb0fac0d g_object_newv (libgobject-2.0.so.0)
#16 0x00007f2deb0fb3c4 g_object_new (libgobject-2.0.so.0)
#17 0x0000000000401db3 n/a (gnome-session-failed)
#18 0x00007f2deaa53291 __libc_start_main (libc.so.6)
#19 0x00000000004021ba n/a (gnome-session-failed)
Comment by Jan Alexander Steffens (heftig) - Thursday, 12 January 2017, 10:28 GMT
The fail whale screen (gnome-session-failed) crashing is most likely a red herring. Something must have caused the screen to be launched in the first place; perhaps the components that gnome-session attempted to launch crashed similarly.

That said, the fail whale screen shouldn't be crashing, either, so that's another issue.

In any case, please rebuild glib2 and gtk3 with debug symbols ( https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces up to installing the package) to get better traces.

Comment by Paste Dubrow (Nolchetyre) - Thursday, 12 January 2017, 21:26 GMT
I rebuild gtk3 with debug (download package from abs, edit PKGBUILD for debug option and build).
But I got some troubles while building glib2: 2 tests didnt passed, but this is may be another issue.

coredump after rebuilding gtk3 at attachment please

I reinstalled harfbuzz and harfbuzz-icu, same problem.
Comment by Paste Dubrow (Nolchetyre) - Thursday, 12 January 2017, 21:30 GMT
I completly switched from infinality to official: https://gist.github.com/cryzed/e002e7057435f02cc7894b9e748c5671
Command `gdk-pixbuf-query-loaders --update-cache` allowed me to login into gnome-session: https://bbs.archlinux.org/viewtopic.php?pid=1683313#p1683313
Comment by G R (gururise) - Thursday, 12 January 2017, 21:50 GMT
I switched from Infinality to Freetype2 and still had the problem of not being able to log into Gnome; however, I just ran the gdk-pixbuf-query-loaders --update-cache as given by Paste and now I am able to log into Gnome on Xorg using my Nvidia 750Ti! Thanks!!
Comment by Paste Dubrow (Nolchetyre) - Thursday, 12 January 2017, 22:00 GMT
Please edit the summary for more relevant searchs, ty
Comment by hsingyun (zhkailing) - Friday, 10 March 2017, 15:54 GMT
same issue, I can login with Wayland, but not on Classic and Xorg.

[ 16.271768] gnome-session-f[783]: segfault at 0 ip 00007fdaaf44ace9 sp 00007ffea2b900d0 error 4 in libgtk-3.so.0.2200.9[7fdaaf168000+6fa000]
Comment by hsingyun (zhkailing) - Friday, 10 March 2017, 17:06 GMT
stack trace with debug symbols (build from abs with "-g -O1"):

PID: 795 (gnome-session-f)
UID: 1000 (hsingyun)
GID: 100 (users)
Signal: 11 (SEGV)
Timestamp: Sat 2017-03-11 01:01:57 CST (45s ago)
Command Line: /usr/lib/gnome-session/gnome-session-failed --allow-logout
Executable: /usr/lib/gnome-session/gnome-session-failed
Control Group: /user.slice/user-1000.slice/session-c2.scope
Unit: session-c2.scope
Slice: user-1000.slice
Session: c2
Owner UID: 1000 (hsingyun)
Boot ID: 67ea83722852415d97032a370c026e39
Machine ID: ef37610188da44ec82561bc06c08bc18
Hostname: hsingyun-pc
Storage: /var/lib/systemd/coredump/core.gnome-session-f.1000.67ea83722852415d97032a370c026e39.795.1489165317000000000000.lz4
Message: Process 795 (gnome-session-f) of user 1000 dumped core.

Stack trace of thread 795:
#0 0x00007f2172e063b2 _gtk_style_provider_private_get_settings (libgtk-3.so.0)
#1 0x00007f2172cb3103 gtk_css_value_initial_compute (libgtk-3.so.0)
#2 0x00007f2172cce331 _gtk_css_value_compute (libgtk-3.so.0)
#3 0x00007f2172cb3047 gtk_css_value_inherit_compute (libgtk-3.so.0)
#4 0x00007f2172cce331 _gtk_css_value_compute (libgtk-3.so.0)
#5 0x00007f2172cc67bc gtk_css_static_style_compute_value (libgtk-3.so.0)
#6 0x00007f2172cb42eb _gtk_css_lookup_resolve (libgtk-3.so.0)
#7 0x00007f2172cc66f6 gtk_css_static_style_new_compute (libgtk-3.so.0)
#8 0x00007f2172cc674e gtk_css_static_style_get_default (libgtk-3.so.0)
#9 0x00007f2172cb4b51 gtk_css_node_init (libgtk-3.so.0)
#10 0x00007f217263230f g_type_create_instance (libgobject-2.0.so.0)
#11 0x00007f21726141fb n/a (libgobject-2.0.so.0)
#12 0x00007f2172615c0d g_object_newv (libgobject-2.0.so.0)
#13 0x00007f21726163c4 g_object_new (libgobject-2.0.so.0)
#14 0x00007f2172cce970 gtk_css_widget_node_new (libgtk-3.so.0)
#15 0x00007f2172e97002 gtk_widget_init (libgtk-3.so.0)
#16 0x00007f217263230f g_type_create_instance (libgobject-2.0.so.0)
#17 0x00007f21726141fb n/a (libgobject-2.0.so.0)
#18 0x00007f2172615c0d g_object_newv (libgobject-2.0.so.0)
#19 0x00007f21726163c4 g_object_new (libgobject-2.0.so.0)
#20 0x00000000004024e2 main (gnome-session-failed)
#21 0x00007f2171f68511 __libc_start_main (libc.so.6)
#22 0x0000000000401d2a _start (gnome-session-failed)
Comment by hsingyun (zhkailing) - Friday, 10 March 2017, 17:31 GMT Comment by Jan de Groot (JGC) - Saturday, 06 May 2017, 21:29 GMT
Don't focus on the backtraces. You're debugging the "Oh no something is wrong" screen that should show up when gnome can't start.

Look at journalctl logs why gnome-session is not working.

Loading...