[Solved] Gnome wayland session unable to login

freewick · 2024-11-02 20:32:37

Hi, I am unable to login into gnome wayland session. When I try to login it blinks and go back to login manager which is gdm and sddm.

This is been happening to me for so many times after I update to a new version of gnome. It happened when I updated from 44 to 45 and 45 to 46 now I think from 46 to 47. I switched to KDE but I just want to figured out why exactly this is happening.

When I updated from gnome 46 to 47 everything broke including gdm and i switched to sddm and kde and didnt bother and even gnome xorg session didnt work. After sometime after an update I tried gdm again and it worked and gnome-xorg session worked but not gnome wayland.

So I just want to figure out why it is happening. I am using mesa drivers only cause I have an all amd laptop with rx 6800s with amd gpu pro drivers also installed just in case.

I did 4 boots and did the following. I am using 0 -1 -2 and -3 to explain what i did in previous boots to understand journalctl log.

In the zero boot which is the latest boot I logged in with zen kernel and gdm. I tried to login with gnome and gnome classic using gdm gui but it didnt work. Then I opened a tty and tried to start wayland with

XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

but it gave the error

A connection to the bus can't be made

In the -1 boot which is the previous boot I logged in with lts kernel and tried to login using gdm gui to gnome and gnome classic but failed and logged into hyprland and exported the journalctl log.

In the -2 boot I did the same except with zen kernel and i logged into gnome xorg session.

In the -3 boot also I did the same.

Here are the journalctl logs I generated using commands and exported.

❯ journalctl -D /var/log/journal -b  | curl -F 'file=@-' 0x0.st
http://0x0.st/XG9q.txt
❯ journalctl -D /var/log/journal -b -1 | curl -F 'file=@-' 0x0.st
http://0x0.st/XG9b.txt
❯ journalctl -D /var/log/journal -b -2 | curl -F 'file=@-' 0x0.st
http://0x0.st/XG9H.txt
❯ journalctl -D /var/log/journal -b -3 | curl -F 'file=@-' 0x0.st
http://0x0.st/XGLF.txt

Link for 0 boot log http://0x0.st/XG9q.txt
Link for -1 boot log http://0x0.st/XG9b.txt
Link for -2 boot log http://0x0.st/XG9H.txt
Link for -3 boot log http://0x0.st/XGLF.txt

So can some one help me figure out whats happening as I want to find solution for this once and for all.

Last edited by freewick (2024-11-02 23:57:49)

seth · 2024-11-02 21:11:23

Nov 03 01:30:35 sanganaka kernel: gnome-shell[2242]: segfault at 20 ip 000073bda6fe8c7c sp 000073bd61ffe060 error 4 in libmutter-15.so.0.0.0[1e8c7c,73bda6e3c000+1c8000] likely on CPU 6 (core 3, socket 0)
Nov 03 01:30:43 sanganaka kernel: gnome-shell[2498]: segfault at 20 ip 00007e23917e8c7c sp 00007e2347dfe060 error 4 in libmutter-15.so.0.0.0[1e8c7c,7e239163c000+1c8000] likely on CPU 7 (core 3, socket 0)
Nov 03 01:31:07 sanganaka kernel: gnome-shell[2852]: segfault at 20 ip 00007b01105e8c7c sp 00007b00c3dfe060 error 4 in libmutter-15.so.0.0.0[1e8c7c,7b011043c000+1c8000] likely on CPU 7 (core 3, socket 0)
Nov 03 01:33:02 sanganaka kernel: gnome-shell[3142]: segfault at 20 ip 00007c78011e8c7c sp 00007c77b7dfe060 error 4 in libmutter-15.so.0.0.0[1e8c7c,7c780103c000+1c8000] likely on CPU 6 (core 3, socket 0)
Nov 03 01:34:55 sanganaka kernel: gnome-shell[3390]: segfault at 20 ip 0000786b755e8c7c sp 0000786b34bfe060 error 4 in libmutter-15.so.0.0.0[1e8c7c,786b7543c000+1c8000] likely on CPU 6 (core 3, socket 0)
Nov 03 01:35:06 sanganaka kernel: gnome-shell[3638]: segfault at 20 ip 00007ecf5c5e8c7c sp 00007ecf0f3fe060 error 4 in libmutter-15.so.0.0.0[1e8c7c,7ecf5c43c000+1c8000] likely on CPU 6 (core 3, socket 0)

Nov 03 01:30:35 sanganaka kernel: gnome-shell[2242]: segfault at 20 ip 000073bda6fe8c7c sp 000073bd61ffe060 error 4 in libmutter-15.so.0.0.0[1e8c7c,73bda6e3c000+1c8000] likely on CPU 6 (core 3, socket 0)
Nov 03 01:30:35 sanganaka kernel: Code: c7 ff 15 4f 0a 0c 00 4c 89 e7 ff 15 d6 f8 0b 00 48 8b 0d 07 2f 0c 00 48 89 c2 48 8d 35 7d 1f 00 00 48 89 df ff 15 bc 2f 0c 00 <49> 8b 75 20 48 89 df ff 15 af 18 0c 00 48 89 df ff 15 c6 0a 0c 00
Nov 03 01:30:35 sanganaka systemd-coredump[2251]: Process 2184 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing...

Nov 03 01:30:35 sanganaka systemd-coredump[2252]: Process 2184 (gnome-shell) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 2242:
                                                  #0  0x000073bda6fe8c7c n/a (libmutter-15.so.0 + 0x1e8c7c)
                                                  #1  0x000073bda7b7097a n/a (libgobject-2.0.so.0 + 0x2397a)
                                                  #2  0x000073bda7b72afb g_object_new_valist (libgobject-2.0.so.0 + 0x25afb)
                                                  #3  0x000073bda7b72eb0 g_object_new (libgobject-2.0.so.0 + 0x25eb0)
                                                  #4  0x000073bda6fe8dba n/a (libmutter-15.so.0 + 0x1e8dba)
                                                  #5  0x000073bda6fe1e59 n/a (libmutter-15.so.0 + 0x1e1e59)
                                                  #6  0x000073bda6fe2d14 n/a (libmutter-15.so.0 + 0x1e2d14)
                                                  #7  0x000073bda6fe5244 n/a (libmutter-15.so.0 + 0x1e5244)
                                                  #8  0x000073bda7572026 n/a (libglib-2.0.so.0 + 0x91026)
                                                  #9  0x000073bda6ca339d n/a (libc.so.6 + 0x9439d)
                                                  #10 0x000073bda6d2849c n/a (libc.so.6 + 0x11949c)

Doesn't look like the MUTTER_DEBUG_KMS_THREAD_TYPE situation, can you log into a gnome session w/ a fresh user account?

Nov 03 01:30:35 sanganaka mutter-x11-fram[1532]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

Otherwise please see https://wiki.archlinux.org/title/Core_d … _core_dump utilizing https://wiki.archlinux.org/title/Debuginfod for a better backtrace.

freewick · 2024-11-02 22:56:54

seth wrote:

Doesn't look like the MUTTER_DEBUG_KMS_THREAD_TYPE situation, can you log into a gnome session w/ a fresh user account?

Omg it worked. I created new account using useradd i was able to login to gnome wayland with that user. I tried with my regular user account and its not working. So It seems my user account has some problem I think. Add idea how to fix for my current user?

seth · 2024-11-02 23:13:31

Maybe some 3rd party extension

Nov 03 01:35:06 sanganaka systemd[2060]: Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (ConditionPathExists=/run/user/1000/gnome-shell-disable-extensions).

or maybe because of the configured UI theme.

In doubt the debuginfod enriched backtrace will hint at the cause.

freewick · 2024-11-02 23:57:19

seth wrote:

Maybe some 3rd party extension

Nov 03 01:35:06 sanganaka systemd[2060]: Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (ConditionPathExists=/run/user/1000/gnome-shell-disable-extensions).

or maybe because of the configured UI theme.

I think that is the cause

In doubt the debuginfod enriched backtrace will hint at the cause.

I haven't used this but based on your suggestion, its likely extension or theme so I did a full reset to gnome using dconf command which I randomly found on some reddit post

dconf reset -f /org/gnome/

It worked. Finally my 2 years of pain with gnome not logging in or broken is finally over. It was just one command. Thank you.

Arch Linux

#1 2024-11-02 20:32:37

[Solved] Gnome wayland session unable to login

#2 2024-11-02 21:11:23

Re: [Solved] Gnome wayland session unable to login

#3 2024-11-02 22:56:54

Re: [Solved] Gnome wayland session unable to login

#4 2024-11-02 23:13:31

Re: [Solved] Gnome wayland session unable to login

#5 2024-11-02 23:57:19

Re: [Solved] Gnome wayland session unable to login

Board footer