GNOME Bugzilla – Bug 772368
After update to gnome 3.22 non-root users can not login
Last modified: 2017-02-10 18:18:14 UTC
Created attachment 336823 [details] journalctl -b outpout After updating Arch Linux to gnome 3.22 non-root users can not login, returns to login screen immediately and no error messages. Root user can login. From journalctl -b I see entries this like Oct 02 12:18:29 CQ5110F systemd-coredump[1510]: Process 1507 (gnome-session-f) of user 1000 dumped core. Stack trace of thread 1507: #0 0x00007f3a2658e1c9 n/a (libgtk-3.so.0) #1 0x00007f3a2642a5f8 n/a (libgtk-3.so.0) #2 0x00007f3a2643f674 n/a (libgtk-3.so.0) #3 0x00007f3a2642b92c n/a (libgtk-3.so.0) #4 0x00007f3a2643f59c n/a (libgtk-3.so.0) #5 0x00007f3a2643f5f5 n/a (libgtk-3.so.0) #6 0x00007f3a2642c292 n/a (libgtk-3.so.0) #7 0x00007f3a25d9730f g_type_create_instance (libgobject-2.0.so.0) #8 0x00007f3a25d791fb n/a (libgobject-2.0.so.0) #9 0x00007f3a25d7ac0d g_object_newv (libgobject-2.0.so.0) #10 0x00007f3a25d7b3c4 g_object_new (libgobject-2.0.so.0) #11 0x00007f3a26447ada n/a (libgtk-3.so.0) #12 0x00007f3a266251a7 n/a (libgtk-3.so.0) #13 0x00007f3a25d9730f g_type_create_instance (libgobject-2.0.so.0) #14 0x00007f3a25d791fb n/a (libgobject-2.0.so.0) #15 0x00007f3a25d7ac0d g_object_newv (libgobject-2.0.so.0) #16 0x00007f3a25d7b3c4 g_object_new (libgobject-2.0.so.0) #17 0x0000000000401db3 n/a (gnome-session-failed) #18 0x00007f3a256d3291 __libc_start_main (libc.so.6) #19 0x00000000004021ba n/a (gnome-session-failed) Output of journalctl -b attached
Problem persists after several 3.22 updates. Occurs with Nouveau and nvidia drivers. Attaching recent journalctl -b output
Created attachment 338377 [details] journalctl -b
Looks more like a bug in your graphics driver, according to this line: > Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Is this bug still present?
I no longer use gnome so I can not answer. Note. root user could log in with gnome so unlikely to be a driver issue outside of permission related issues.
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 775337 ***