[SOLVED] GNOME crashes on login unlike other desktops in GDM

KevinCrrl · 2025-10-25 16:03:10

Hi everyone, a day ago I tried to log in to Gnome using GDM, but right when I hit enter after entering the password, the screen went gray (the gray background of GDM). It wouldn't go any further, and I couldn't even move the GDM cursor.

I was looking through the Wiki [1] and found this command to be a possible solution:

gsettings set org.gnome.SessionManager auto-save-session false

However, the output was only this error:

$ gsettings set org.gnome.SessionManager auto-save-session false
No existe la clave «auto-save-session»

("No such key "auto-save-session"", just that my system is in Spanish.)

I rebooted the system to test by saving the journalctl to a .txt file, filtering only what was related to GNOME startup, and I got this on startup:

sep 20 18:51:08 kevarch gnome-shell[1035]: Connection to xwayland lost
sep 20 18:53:04 kevarch /usr/lib/gdm-wayland-session[1026]: dbus-daemon[1026]: [session uid=120 pid=1026 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=1027 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
sep 20 18:53:04 kevarch gnome-session[1027]: gnome-session-binary[1027]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error al llamar StartSereviceByName para org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
sep 20 18:53:04 kevarch gnome-session-binary[1027]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error al llamar StartSereviceByName para org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
sep 20 18:53:04 kevarch gnome-session[1027]: gnome-session-binary[1027]: WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
sep 20 18:53:04 kevarch gnome-session-binary[1027]: WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
sep 20 18:53:04 kevarch gnome-shell[1039]: Running GNOME Shell (using mutter 48.5) as a Wayland display server
sep 20 18:53:05 kevarch gnome-shell[1039]: Thread 'KMS thread' will be using high priority scheduling
sep 20 18:53:05 kevarch gnome-shell[1039]: Device '/dev/dri/card1' prefers shadow buffer
sep 20 18:53:05 kevarch gnome-shell[1039]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
sep 20 18:53:05 kevarch gnome-shell[1039]: Created gbm renderer for '/dev/dri/card1'
sep 20 18:53:05 kevarch gnome-shell[1039]: GPU /dev/dri/card1 selected primary from builtin panel presence
sep 20 18:53:05 kevarch gnome-shell[1039]: Obtained a high priority EGL context
sep 20 18:53:05 kevarch /usr/lib/gdm-wayland-session[1026]: dbus-daemon[1026]: [session uid=120 pid=1026 pidfd=5] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=120 pid=1039 comm="/usr/bin/gnome-shell")
sep 20 18:53:05 kevarch gnome-shell[1039]: Using public X11 display :1024, (using :1025 for managed services)
sep 20 18:53:05 kevarch gnome-shell[1039]: Using Wayland display name 'wayland-0'
sep 20 18:53:05 kevarch /usr/lib/gdm-wayland-session[1089]: dbus-daemon[1089]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=1039 comm="/usr/bin/gnome-shell")
sep 20 18:53:06 kevarch gnome-shell[1039]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
sep 20 18:53:06 kevarch /usr/lib/gdm-wayland-session[1026]: dbus-daemon[1026]: [session uid=120 pid=1026 pidfd=5] Activating service name='org.gnome.Shell.Screencast' requested by ':1.3' (uid=120 pid=1039 comm="/usr/bin/gnome-shell")
sep 20 18:53:06 kevarch /usr/lib/gdm-wayland-session[1026]: dbus-daemon[1026]: [session uid=120 pid=1026 pidfd=5] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=120 pid=1039 comm="/usr/bin/gnome-shell")
sep 20 18:53:06 kevarch /usr/lib/gdm-wayland-session[1026]: dbus-daemon[1026]: [session uid=120 pid=1026 pidfd=5] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=120 pid=1039 comm="/usr/bin/gnome-shell")
sep 20 18:53:06 kevarch gnome-shell[1039]: Failed to parse saved session file: Falló al abrir el archivo «/var/lib/gdm/.config/mutter/sessions/1074bbea9e276b3c3b175841238487755000000010270000.ms»: No existe el fichero o el directorio
sep 20 18:53:06 kevarch gnome-shell[1039]: Failed to launch ibus-daemon: Falló al ejecutar el proceso hijo «ibus-daemon» (No existe el fichero o el directorio)
sep 20 18:53:06 kevarch gnome-shell[1039]: Will monitor session 1
sep 20 18:53:06 kevarch gnome-shell[1039]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
sep 20 18:53:06 kevarch /usr/lib/gdm-wayland-session[1026]: dbus-daemon[1026]: [session uid=120 pid=1026 pidfd=5] Successfully activated service 'org.gnome.Shell.Notifications'
sep 20 18:53:06 kevarch org.gnome.Shell.desktop[1361]: The XKEYBOARD keymap compiler (xkbcomp) reports:
sep 20 18:53:06 kevarch org.gnome.Shell.desktop[1361]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
sep 20 18:53:06 kevarch org.gnome.Shell.desktop[1361]: > Warning:          Could not resolve keysym XF86Accessibility
sep 20 18:53:06 kevarch org.gnome.Shell.desktop[1361]: > Warning:          Could not resolve keysym XF86DoNotDisturb
sep 20 18:53:06 kevarch org.gnome.Shell.desktop[1361]: Errors from xkbcomp are not fatal to the X server
sep 20 18:53:06 kevarch gnome-session-binary[1027]: Entering running state
sep 20 18:53:06 kevarch gnome-shell[1039]: Failed to launch ibus-daemon: Falló al ejecutar el proceso hijo «ibus-daemon» (No existe el fichero o el directorio)

I don't think it's a GDM issue, as I can successfully boot other desktops like Plasma or WM like OpenBox. To this day, I haven't been able to find a solution, which is why I'm turning to these forums. I greatly appreciate any help.

By the way, please forgive any typos, I'm not quite used to posting here yet.

[1]: https://wiki.archlinux.org/title/GNOME/ … on_startup

Last edited by KevinCrrl (2025-10-26 15:21:12)

seth · 2025-10-25 16:33:25

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

sep 20 18:53:06 kevarch gnome-shell[1039]: Failed to launch ibus-daemon: Falló al ejecutar el proceso hijo «ibus-daemon» (No existe el fichero o el directorio)

https://archlinux.org/packages/extra/x86_64/ibus/ is a hard dependency for gnome shell

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup

KevinCrrl · 2025-10-25 18:36:16

I checked and I already had IBus installed. I even tried reinstalling it in case something was wrong, but that didn't work either.

Reading the documentation [1], I realized that GNOME doesn't even need manual integration with IBus since version 3.6, so it seems strange to me. The problem doesn't even come from updating GNOME, since I've had the latest version for a while. I still can't start the graphical environment, and the command you gave me at the end didn't show anything related to GNOME, GDM, or IBus. I'll keep investigating and let you know if I find anything.

[1]: https://wiki.archlinux.org/title/IBus#Installation

seth · 2025-10-25 18:45:28

I checked and I already had IBus installed.

The log clearly says "Falló al ejecutar el proceso hijo «ibus-daemon» (No existe el fichero o el directorio)" - do I have to translate that for you?

GNOME doesn't even need manual integration with IBus

No, but it *needs* ibus.

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup

will reveal any problems with installed packages.
Run that and post the output.
You can

sudo LC_ALL=C pacman -Qkk |& grep -v ', 0 altered files' | grep -v backup > /tmp/howbadisit.txt
sudo chmod ugo+r /tmp/howbadisit.txt
cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.st

KevinCrrl · 2025-10-25 22:44:53

Okay, I see what you mean. Here's the URL of the command you told me to troubleshoot:

http://0x0.st/K24M.txt

Although I don't see anything directly related to ibus, unless there's something affecting it.

seth · 2025-10-26 08:53:29

There're some deviations (NoExtract rules?) but indeed nothing ibus but that doesn't fit the log segment you posted

pacman -Qikk ibus

and please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

KevinCrrl · 2025-10-26 15:20:36

I've already solved the problem: I checked the boot journalctl and there was a problem starting bash apparently, because inside the .bashrc I had a script running in a loop, which left the Gnome session inside that loop and prevented it from starting:

Oct 26 10:05:25 archlinux bluetoothd[819]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Oct 26 10:05:25 archlinux bluetoothd[819]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/faststream
Oct 26 10:05:25 archlinux bluetoothd[819]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/faststream_duplex
Oct 26 10:05:25 archlinux bluetoothd[819]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSink/opus_05
Oct 26 10:05:25 archlinux bluetoothd[819]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/opus_05
Oct 26 10:05:25 archlinux bluetoothd[819]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Oct 26 10:05:25 archlinux bluetoothd[819]: Endpoint registered: sender=:1.61 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: ┌──(Kevin@archlinux)-[/home/Kevin]
Oct 26 10:05:25 archlinux /usr/lib/gdm-wayland-session[2397]: └─$

These last lines were repeated non-stop throughout the entire record, so simply I commented out the script line in .bashrc and restarted, and Gnome started correctly.

Thanks for the help. The command was very helpful in finding the problem , I hadn't thought of that before.

Arch Linux

#1 2025-10-25 16:03:10

[SOLVED] GNOME crashes on login unlike other desktops in GDM

#2 2025-10-25 16:33:25

Re: [SOLVED] GNOME crashes on login unlike other desktops in GDM

#3 2025-10-25 18:36:16

Re: [SOLVED] GNOME crashes on login unlike other desktops in GDM

#4 2025-10-25 18:45:28

Re: [SOLVED] GNOME crashes on login unlike other desktops in GDM

#5 2025-10-25 22:44:53

Re: [SOLVED] GNOME crashes on login unlike other desktops in GDM

#6 2025-10-26 08:53:29

Re: [SOLVED] GNOME crashes on login unlike other desktops in GDM

#7 2025-10-26 15:20:36

Re: [SOLVED] GNOME crashes on login unlike other desktops in GDM

Board footer