GNOME freezes after login

[mihalycsaba]

It freezes after the gdm login box disappears, only thing I can see is a grey screen and the mouse cursor.
This started happening a few months ago, but usually a hard reset fixed it. But today there was a linux-firmware and an amd-ucode update an it’s happening every time. So far it didn’t happen on the lts kernel. I was already on the 6.7 kernel this morning, it started normally, the firmware update probably changed something. It’s weird that it loads with the 6.6 lts, because it started happening on that kernel a few months ago.

I can load hyprland, disabled every extension.

amd 5700g processor, no graphics card

here’s a log:

[csaba@csaba-mini ~]$ journalctl -f
Jan 18 22:51:59 csaba-mini systemd[1403]: Listening on PipeWire Multimedia System Sockets.
Jan 18 22:51:59 csaba-mini systemd[1403]: Listening on D-Bus User Message Bus Socket.
Jan 18 22:51:59 csaba-mini systemd[1403]: Reached target Sockets.
Jan 18 22:51:59 csaba-mini systemd[1403]: Reached target Basic System.
Jan 18 22:51:59 csaba-mini systemd[1]: Started User Manager for UID 1000.
Jan 18 22:51:59 csaba-mini systemd[1403]: Starting Update XDG user dir configuration...
Jan 18 22:51:59 csaba-mini systemd[1]: Started Session 3 of User csaba.
Jan 18 22:51:59 csaba-mini systemd[1403]: Finished Update XDG user dir configuration.
Jan 18 22:51:59 csaba-mini systemd[1403]: Reached target Main User Target.
Jan 18 22:51:59 csaba-mini systemd[1403]: Startup finished in 83ms.
Jan 18 22:52:12 csaba-mini gdm-password][1432]: gkr-pam: unable to locate daemon control file
Jan 18 22:52:12 csaba-mini gdm-password][1432]: gkr-pam: stashed password to try later in open session
Jan 18 22:52:12 csaba-mini gdm-password][1432]: pam_unix(gdm-password:session): session opened for user csaba(uid=1000) by csaba(uid=0)
Jan 18 22:52:12 csaba-mini systemd-logind[694]: New session 5 of user csaba.
Jan 18 22:52:12 csaba-mini systemd[1]: Started Session 5 of User csaba.
Jan 18 22:52:12 csaba-mini systemd[1403]: Started GNOME Keyring daemon.
Jan 18 22:52:12 csaba-mini gnome-keyring-daemon[1450]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 18 22:52:12 csaba-mini systemd[1403]: Created slice User Core Session Slice.
Jan 18 22:52:12 csaba-mini systemd[1403]: Starting D-Bus User Message Bus...
Jan 18 22:52:12 csaba-mini dbus-broker-launch[1462]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jan 18 22:52:12 csaba-mini dbus-broker-launch[1462]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jan 18 22:52:12 csaba-mini systemd[1403]: Started D-Bus User Message Bus.
Jan 18 22:52:12 csaba-mini dbus-broker-launch[1462]: Ready
Jan 18 22:52:12 csaba-mini gdm-password][1432]: gkr-pam: unlocked login keyring
Jan 18 22:52:13 csaba-mini kernel: rfkill: input handler enabled
Jan 18 22:52:13 csaba-mini gsd-media-keys[1083]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 18 22:52:13 csaba-mini gsd-media-keys[1083]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/ldac
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink/aptx
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/aptx
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink/aac
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/aac
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink/sbc
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/sbc
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink/sbc_xq
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/sbc_xq
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/faststream
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink/opus_05
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/opus_05
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Failed to remove UUID: Failed (0x03)
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Failed to remove UUID: Failed (0x03)
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Failed to remove UUID: Failed (0x03)
Jan 18 22:52:13 csaba-mini bluetoothd[688]: Failed to remove UUID: Failed (0x03)
Jan 18 22:52:13 csaba-mini systemd[1403]: Created slice Slice /app/gnome-session-manager.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME Wayland Session.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target Session services which should run early before the graphical session is brought up.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME Shell.
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME Remote Desktop...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting Monitor Session leader for GNOME Session...
Jan 18 22:52:13 csaba-mini systemd[1403]: Started Monitor Session leader for GNOME Session.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target Tasks to be run before GNOME Session starts.
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME Session Manager (session: gnome)...
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME Remote Desktop.
Jan 18 22:52:13 csaba-mini gnome-keyring-daemon[1450]: The PKCS#11 component was already initialized
Jan 18 22:52:13 csaba-mini gnome-keyring-d[1450]: The PKCS#11 component was already initialized
Jan 18 22:52:13 csaba-mini gnome-keyring-daemon[1548]: discover_other_daemon: 1
Jan 18 22:52:13 csaba-mini gnome-keyring-pkcs11.desktop[1548]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 18 22:52:13 csaba-mini gnome-session[1528]: gnome-session-binary[1528]: GnomeDesktop-WARNING: Could not create transient scope for PID 1540: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 1540 does not exist.
Jan 18 22:52:13 csaba-mini gnome-session-binary[1528]: GnomeDesktop-WARNING: Could not create transient scope for PID 1540: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 1540 does not exist.
Jan 18 22:52:13 csaba-mini gnome-keyring-daemon[1551]: discover_other_daemon: 1
Jan 18 22:52:13 csaba-mini gnome-keyring-ssh.desktop[1551]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 18 22:52:13 csaba-mini gnome-keyring-ssh.desktop[1551]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jan 18 22:52:13 csaba-mini gnome-keyring-daemon[1450]: The Secret Service was already initialized
Jan 18 22:52:13 csaba-mini gnome-keyring-d[1450]: The Secret Service was already initialized
Jan 18 22:52:13 csaba-mini gnome-keyring-daemon[1554]: discover_other_daemon: 1
Jan 18 22:52:13 csaba-mini gnome-keyring-secrets.desktop[1554]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 18 22:52:13 csaba-mini gnome-keyring-secrets.desktop[1554]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jan 18 22:52:13 csaba-mini systemd[1403]: app-gnome-gnome\x2dkeyring\x2dsecrets-1547.scope: Couldn't move process 1547 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-1547.scope': No such process
Jan 18 22:52:13 csaba-mini systemd[1403]: app-gnome-gnome\x2dkeyring\x2dsecrets-1547.scope: Failed to add PIDs to scope's control group: No such process
Jan 18 22:52:13 csaba-mini systemd[1403]: app-gnome-gnome\x2dkeyring\x2dsecrets-1547.scope: Failed with result 'resources'.
Jan 18 22:52:13 csaba-mini systemd[1403]: Failed to start Application launched by gnome-session-binary.
Jan 18 22:52:13 csaba-mini systemd[1403]: app-gnome-gnome\x2dkeyring\x2dssh-1544.scope: PID 1544 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1544.scope', skipping: No such process
Jan 18 22:52:13 csaba-mini systemd[1403]: app-gnome-gnome\x2dkeyring\x2dssh-1544.scope: No PIDs left to attach to the scope's control group, refusing.
Jan 18 22:52:13 csaba-mini systemd[1403]: app-gnome-gnome\x2dkeyring\x2dssh-1544.scope: Failed with result 'resources'.
Jan 18 22:52:13 csaba-mini systemd[1403]: Failed to start Application launched by gnome-session-binary.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME Session Manager (session: gnome).
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME Session Manager is ready.
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME Shell on Wayland...
Jan 18 22:52:13 csaba-mini systemd[1403]: GNOME Shell on X11 was skipped because of an unmet condition check (ConditionEnvironment=XDG_SESSION_TYPE=x11).
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting Virtual filesystem service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Started Virtual filesystem service.
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Running GNOME Shell (using mutter 45.3) as a Wayland display server
Jan 18 22:52:13 csaba-mini rtkit-daemon[1245]: Supervising 7 threads of 4 processes of 1 users.
Jan 18 22:52:13 csaba-mini rtkit-daemon[1245]: Supervising 7 threads of 4 processes of 1 users.
Jan 18 22:52:13 csaba-mini rtkit-daemon[1245]: Successfully made thread 1586 of process 1556 owned by '1000' RT at priority 20.
Jan 18 22:52:13 csaba-mini rtkit-daemon[1245]: Supervising 8 threads of 5 processes of 2 users.
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Made thread 'KMS thread' realtime scheduled
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Device '/dev/dri/card1' prefers shadow buffer
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Created gbm renderer for '/dev/dri/card1'
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Boot VGA GPU /dev/dri/card1 selected as primary
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Obtained a high priority EGL context
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Obtained a high priority EGL context
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting Accessibility services bus...
Jan 18 22:52:13 csaba-mini systemd[1403]: Started Accessibility services bus.
Jan 18 22:52:13 csaba-mini at-spi-bus-launcher[1656]: Policy to allow eavesdropping in /usr/share/defaults/at-spi2/accessibility.conf +15: Eavesdropping is deprecated and ignored
Jan 18 22:52:13 csaba-mini at-spi-bus-launcher[1656]: Policy to allow eavesdropping in /usr/share/defaults/at-spi2/accessibility.conf +17: Eavesdropping is deprecated and ignored
Jan 18 22:52:13 csaba-mini dbus-broker-launch[1656]: Ready
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Using public X11 display :0, (using :1 for managed services)
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Using Wayland display name 'wayland-0'
Jan 18 22:52:13 csaba-mini systemd[1403]: Created slice Slice /app/dbus-:1.18-org.a11y.atspi.Registry.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started dbus-:1.18-org.a11y.atspi.Registry@0.service.
Jan 18 22:52:13 csaba-mini at-spi2-registryd[1660]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Will monitor session 5
Jan 18 22:52:13 csaba-mini systemd[1403]: Created slice Slice /app/dbus-:1.2-org.gnome.Shell.Screencast.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started dbus-:1.2-org.gnome.Shell.Screencast@0.service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Created slice Slice /app/dbus-:1.2-org.gnome.Shell.CalendarServer.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started dbus-:1.2-org.gnome.Shell.CalendarServer@0.service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting sandboxed app permission store...
Jan 18 22:52:13 csaba-mini gnome-shell-calendar-server[1665]: /usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-2.0.so.2: cannot open shared object file: No such file or directory
Jan 18 22:52:13 csaba-mini systemd[1403]: dbus-:1.2-org.gnome.Shell.CalendarServer@0.service: Main process exited, code=exited, status=127/n/a
Jan 18 22:52:13 csaba-mini systemd[1403]: dbus-:1.2-org.gnome.Shell.CalendarServer@0.service: Failed with result 'exit-code'.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started sandboxed app permission store.
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting User preferences database...
Jan 18 22:52:13 csaba-mini systemd[1403]: Started User preferences database.
Jan 18 22:52:13 csaba-mini systemd[1403]: Created slice Slice /app/dbus-:1.2-org.gnome.Shell.Notifications.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started dbus-:1.2-org.gnome.Shell.Notifications@0.service.
Jan 18 22:52:13 csaba-mini gnome-shell[1556]: Could not issue 'GetUnit' systemd call
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME Shell on Wayland.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME Session is initialized.
Jan 18 22:52:13 csaba-mini systemd[1403]: GNOME session X11 services is inactive.
Jan 18 22:52:13 csaba-mini systemd[1403]: Dependency failed for GNOME XSettings service.
Jan 18 22:52:13 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.XSettings.service: Job org.gnome.SettingsDaemon.XSettings.service/start failed with result 'dependency'.
Jan 18 22:52:13 csaba-mini systemd[1403]: gnome-session-x11-services-ready.target: Job gnome-session-x11-services-ready.target/verify-active failed with result 'dependency'.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME Session (session: gnome).
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME XSettings target.
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting Signal initialization done to GNOME Session Manager...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME accessibility service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME color management service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME date & time service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME maintenance of expirable data service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME keyboard configuration service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME keyboard shortcuts service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME power management service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME printer notifications service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME RFKill support service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME FreeDesktop screensaver service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME file sharing service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME smartcard service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME sound sample caching service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME USB protection service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Starting GNOME Wacom tablet support service...
Jan 18 22:52:13 csaba-mini systemd[1403]: Finished Signal initialization done to GNOME Session Manager.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME accessibility service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME maintenance of expirable data service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started Application launched by gnome-session-binary.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME accessibility target.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME maintenance of expirable data target.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME smartcard service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME smartcard target.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME date & time service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME date & time target.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME FreeDesktop screensaver service.
Jan 18 22:52:13 csaba-mini kernel: rfkill: input handler disabled
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME RFKill support service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME RFKill support target.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME FreeDesktop screensaver target.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME USB protection service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME USB protection target.
Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME file sharing service.
Jan 18 22:52:13 csaba-mini systemd[1403]: Reached target GNOME file sharing target.
Jan 18 22:52:14 csaba-mini systemd[1403]: Started GNOME sound sample caching service.
Jan 18 22:52:14 csaba-mini systemd[1403]: Created slice Slice /app/dbus-:1.2-org.gnome.ScreenSaver.
Jan 18 22:52:14 csaba-mini systemd[1403]: Reached target GNOME sound sample caching target.
Jan 18 22:52:14 csaba-mini systemd[1403]: Started dbus-:1.2-org.gnome.ScreenSaver@0.service.
Jan 18 22:52:14 csaba-mini gnome-session-binary[1528]: WARNING: Failed to start app: Unable to start application: Desktop file didn’t specify Exec field
Jan 18 22:52:14 csaba-mini gnome-session[1528]: gnome-session-binary[1528]: WARNING: Failed to start app: Unable to start application: Desktop file didn’t specify Exec field
Jan 18 22:52:14 csaba-mini gnome-session-binary[1528]: Entering running state
Jan 18 22:52:14 csaba-mini systemd[1]: Starting Disk Manager...
Jan 18 22:52:14 csaba-mini systemd[1403]: Started Application launched by gnome-session-binary.
Jan 18 22:52:14 csaba-mini systemd[1403]: Started Application launched by gnome-session-binary.
Jan 18 22:52:14 csaba-mini systemd[1403]: Started Application launched by gnome-session-binary.
Jan 18 22:52:14 csaba-mini systemd[1403]: Started Application launched by gnome-session-binary.
Jan 18 22:52:14 csaba-mini systemd[1403]: app-gnome-wallpaper\x2donce-1848.scope: PID 1848 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-wallpaper\x2donce-1848.scope', skipping: No such process
Jan 18 22:52:14 csaba-mini systemd[1403]: app-gnome-wallpaper\x2donce-1848.scope: No PIDs left to attach to the scope's control group, refusing.
Jan 18 22:52:14 csaba-mini systemd[1403]: app-gnome-wallpaper\x2donce-1848.scope: Failed with result 'resources'.
Jan 18 22:52:14 csaba-mini systemd[1403]: Failed to start Application launched by gnome-session-binary.
Jan 18 22:52:14 csaba-mini systemd[1403]: Started Application launched by gnome-session-binary.
Jan 18 22:52:14 csaba-mini udisksd[1864]: udisks daemon version 2.10.1 starting
Jan 18 22:52:14 csaba-mini systemd[1]: Started Disk Manager.
Jan 18 22:52:14 csaba-mini systemd[1403]: Started GNOME printer notifications service.
Jan 18 22:52:14 csaba-mini systemd[1403]: Reached target GNOME printer notifications target.
Jan 18 22:52:14 csaba-mini udisksd[1864]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jan 18 22:52:14 csaba-mini welcome.desktop[1822]: Welcome app is disabled. To start it anyway, use option --enable (temporarily: --once).
Jan 18 22:52:15 csaba-mini gnome-session[1528]: gnome-session-binary[1528]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
Jan 18 22:52:15 csaba-mini gnome-session-binary[1528]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
Jan 18 22:52:18 csaba-mini systemd-timesyncd[678]: Contacted time server 109.230.227.90:123 (2.arch.pool.ntp.org).
Jan 18 22:52:18 csaba-mini systemd-timesyncd[678]: Initial clock synchronization to Thu 2024-01-18 22:52:18.286964 EET.
Jan 18 22:52:20 csaba-mini systemd[1]: systemd-localed.service: Deactivated successfully.
Jan 18 22:52:39 csaba-mini gnome-session[1528]: gnome-session-binary[1528]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
Jan 18 22:52:39 csaba-mini gnome-session-binary[1528]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
Jan 18 22:52:39 csaba-mini gsd-usb-protect[1741]: Failed to get screen saver status: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code24: Timeout was reached
Jan 18 22:52:39 csaba-mini gsd-usb-protect[1741]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Jan 18 22:52:44 csaba-mini systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jan 18 22:52:50 csaba-mini geoclue[1238]: Service not used for 60 seconds. Shutting down..
Jan 18 22:52:50 csaba-mini systemd[1]: geoclue.service: Deactivated successfully.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Keyboard.service: start operation timed out. Terminating.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.MediaKeys.service: start operation timed out. Terminating.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Wacom.service: start operation timed out. Terminating.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Color.service: start operation timed out. Terminating.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Power.service: start operation timed out. Terminating.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'timeout'.
Jan 18 22:53:44 csaba-mini systemd[1403]: Failed to start GNOME keyboard configuration service.
Jan 18 22:53:44 csaba-mini systemd[1403]: Reached target GNOME keyboard configuration target.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Color.service: Failed with result 'timeout'.
Jan 18 22:53:44 csaba-mini systemd[1403]: Failed to start GNOME color management service.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'timeout'.
Jan 18 22:53:44 csaba-mini systemd[1403]: Failed to start GNOME keyboard shortcuts service.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Power.service: Failed with result 'timeout'.
Jan 18 22:53:44 csaba-mini systemd[1403]: Failed to start GNOME power management service.
Jan 18 22:53:44 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'timeout'.
Jan 18 22:53:44 csaba-mini systemd[1403]: Failed to start GNOME Wacom tablet support service.
Jan 18 22:53:44 csaba-mini systemd[1403]: Reached target GNOME color management target.
Jan 18 22:53:44 csaba-mini systemd[1403]: Reached target GNOME keyboard shortcuts target.
Jan 18 22:53:44 csaba-mini systemd[1403]: Reached target GNOME power management target.
Jan 18 22:53:44 csaba-mini systemd[1403]: Reached target GNOME Wacom tablet support target.
Jan 18 22:53:44 csaba-mini systemd[1403]: Reached target GNOME Session.
Jan 18 22:53:44 csaba-mini systemd[1403]: Reached target GNOME Wayland Session (session: gnome).
Jan 18 22:53:44 csaba-mini systemd[1403]: Reached target Current graphical user session.
Jan 18 22:53:45 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Keyboard.service: Scheduled restart job, restart counter is at 1.
Jan 18 22:53:45 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Color.service: Scheduled restart job, restart counter is at 1.
Jan 18 22:53:45 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Power.service: Scheduled restart job, restart counter is at 1.
Jan 18 22:53:45 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.Wacom.service: Scheduled restart job, restart counter is at 1.
Jan 18 22:53:45 csaba-mini systemd[1403]: org.gnome.SettingsDaemon.MediaKeys.service: Scheduled restart job, restart counter is at 1.
Jan 18 22:53:45 csaba-mini systemd[1403]: Starting GNOME color management service...
Jan 18 22:53:45 csaba-mini systemd[1403]: Starting GNOME keyboard configuration service...
Jan 18 22:53:45 csaba-mini systemd[1403]: Starting GNOME keyboard shortcuts service...
Jan 18 22:53:45 csaba-mini systemd[1403]: Starting GNOME power management service...
Jan 18 22:53:45 csaba-mini systemd[1403]: Starting GNOME Wacom tablet support service...

There are a few PID x vanished messages like this one:

Jan 18 22:52:14 csaba-mini systemd[1403]: app-gnome-wallpaper\x2donce-1848.scope: PID 1848 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-wallpaper\x2donce-1848.scope', skipping: No such process
Jan 18 22:52:14 csaba-mini systemd[1403]: app-gnome-wallpaper\x2donce-1848.scope: No PIDs left to attach to the scope's control group, refusing.
Jan 18 22:52:14 csaba-mini systemd[1403]: app-gnome-wallpaper\x2donce-1848.scope: Failed with result 'resources'.
Jan 18 22:52:14 csaba-mini systemd[1403]: Failed to start Application launched by gnome-session-binary.

@mbod I was googling the errors and saw you pop up with a similar issue from 2021, do you remember what you did with this?

The screen is frozen, I can’t ctrl + alt + fx to the console, but I can log in with ssh and I can see new gnome messages pop up with journalctl -f so it’s probably a display related error.

[Nomad]

It looks like there are several warnings and errors in your journal logs, and it seems that some GNOME services are timing out or failing to start properly. Let’s try to troubleshoot this step by step:

1. Desktop File Issue:

   gnome-session-binary[1528]: WARNING: Failed to start app: Unable to start application: Desktop file didn’t specify Exec field
   

   This warning indicates that there might be an issue with a desktop file. Make sure all your GNOME desktop files are correctly configured, especially the Exec field.

2. Library Missing Error:

   gnome-shell-calendar-server[1665]: /usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-2.0.so.2: cannot open shared object file: No such file or directory
   

   This error suggests that a library (libecal-2.0.so.2) is missing. Try reinstalling the package that provides this library.

3. Timeout Issues:

   org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'timeout'.
   Failed to start GNOME keyboard configuration service.
   

   These errors indicate that some GNOME services are timing out. It could be related to the overall system load or resource availability. You can try the following steps:

   • Check your system resource usage (top or htop) to see if there are any processes consuming too much CPU or memory.
   • Try disabling some non-essential startup applications or services to see if the issue persists.

4. USBGuard Parameters Issue:

   gsd-usb-protect[1741]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
   

   This error suggests that the USBGuard service might not be available or installed. You can check if USBGuard is installed and try restarting the USBGuard service.

5. Screensaver and Idle Monitor Issues:

   GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
   

   These warnings indicate issues related to screensaver and idle monitor proxies. This might be a consequence of the timeout issues mentioned earlier. Troubleshoot the timeouts first, and these warnings might resolve.

6. Bluetooth Endpoints Unregistered:

   bluetoothd[688]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource/ldac
   

   These messages are related to Bluetooth endpoints. They seem normal, unless you’re experiencing issues with Bluetooth functionality.

7. Kernel Log:

   Jan 18 22:52:13 csaba-mini kernel: rfkill: input handler enabled
   Jan 18 22:52:14 csaba-mini kernel: rfkill: input handler disabled
   

   The rfkill messages indicate changes in the status of RFKill (Radio Frequency Kill) switch handling. This may or may not be related to the freezing issue.

After checking these aspects, if the issue persists, you may want to consider checking for another update to your system (sudo pacman -Syu) to ensure that all packages are up-to-date. Additionally, check the Arch Linux forums to see if this has been reported by other users.

[mihalycsaba]

is this a gpt answer?

btw I’m not sure what it wants to start

gnome-session-binary[1528]: WARNING: Failed to start app: Unable to start application: Desktop file didn’t specify Exec field

[Nomad]

@mihalycsaba

I’m not sure what it wants to start

• The number in square brackets [1528] in your error message represents the process ID (PID) of the gnome-session-binary process. You can use this PID to find more information about the process and its associated application.

• Run the following command in the terminal: ps aux | grep 1528

This command will show you more details about the process, including the command line it was started with.

[mbod]

@mihalycsaba

@mbod I was googling the errors and saw you pop up with a similar issue from 2021, do you remember what you did with this?

I did remove certain desktop files from autostart folder.
In /etc/xdg/autostart I created a folder OFF and moved the following files into OFF:

gnome-keyring-pkcs11.desktop  
gnome-keyring-secrets.desktop  
user-dirs-update-gtk.desktop  
wallpaper-once.desktop

form my point of view the gnome-keyring*desktop files are obsolete because the gnome-keyring-daemon is started with a systemd service gnome-keyring-daemon.service already.

And I do not need user-dirs-update-gtk.desktop and wallpaper-once.desktop to start at every login.

But these messages in the journal are just cosmetic annoyances. They can not explain why your desktop freezes.

[mbod]

@mihalycsaba

Jan 18 22:52:13 csaba-mini systemd[1403]: Started GNOME Remote Desktop.

What is this for? From my point of view this should not be there.

[mihalycsaba]

It happened on LTS too, at least I managed to get in after a restart.

@mbod

What is this for? From my point of view this should not be there.

I tried to use the built in gnome remote desktop in the gnome settings, which starts some rdp server. I will turn it off since it’s unusable anyway.

I have lot of autostart items, some of them are old. No idea what is really needed. I have removed the gnome-keyring ones and the user dir update, wallpaper once and xapp-sn-watcher

-rw-r--r-- 1 root root   150 Nov  4  2021 arch-audit-gtk.desktop
-rw-r--r-- 1 root root   292 Jan  6 06:14 at-spi-dbus-bus.desktop
-rw-r--r-- 1 root root   352 Jan 11 00:16 eos-update-notifier.desktop
-rw-r--r-- 1 root root  4117 Feb 28  2023 firewall-applet.desktop
-rw-r--r-- 1 root root   223 Jan 18 17:42 geoclue-demo-agent.desktop
-rw-r--r-- 1 root root  8539 Jun  8  2023 gnome-keyring-pkcs11.desktop
-rw-r--r-- 1 root root  8066 Jun  8  2023 gnome-keyring-secrets.desktop
-rw-r--r-- 1 root root  6605 Jun  8  2023 gnome-keyring-ssh.desktop
-rw-r--r-- 1 root root   249 Dec 25 10:33 org.gnome.SettingsDaemon.A11ySettings.desktop
-rw-r--r-- 1 root root   244 Dec 25 10:33 org.gnome.SettingsDaemon.Color.desktop
-rw-r--r-- 1 root root   242 Dec 25 10:33 org.gnome.SettingsDaemon.Datetime.desktop
-rw-r--r-- 1 root root   199 Dec  1 22:00 org.gnome.SettingsDaemon.DiskUtilityNotify.desktop
-rw-r--r-- 1 root root   264 Dec 25 10:33 org.gnome.SettingsDaemon.Housekeeping.desktop
-rw-r--r-- 1 root root   253 Dec 25 10:33 org.gnome.SettingsDaemon.Keyboard.desktop
-rw-r--r-- 1 root root   251 Dec 25 10:33 org.gnome.SettingsDaemon.MediaKeys.desktop
-rw-r--r-- 1 root root   244 Dec 25 10:33 org.gnome.SettingsDaemon.Power.desktop
-rw-r--r-- 1 root root   263 Dec 25 10:33 org.gnome.SettingsDaemon.PrintNotifications.desktop
-rw-r--r-- 1 root root   243 Dec 25 10:33 org.gnome.SettingsDaemon.Rfkill.desktop
-rw-r--r-- 1 root root   263 Dec 25 10:33 org.gnome.SettingsDaemon.ScreensaverProxy.desktop
-rw-r--r-- 1 root root   242 Dec 25 10:33 org.gnome.SettingsDaemon.Sharing.desktop
-rw-r--r-- 1 root root   241 Dec 25 10:33 org.gnome.SettingsDaemon.Smartcard.desktop
-rw-r--r-- 1 root root   248 Dec 25 10:33 org.gnome.SettingsDaemon.Sound.desktop
-rw-r--r-- 1 root root   251 Dec 25 10:33 org.gnome.SettingsDaemon.UsbProtection.desktop
-rw-r--r-- 1 root root   248 Dec 25 10:33 org.gnome.SettingsDaemon.Wacom.desktop
-rw-r--r-- 1 root root   239 Dec 25 10:33 org.gnome.SettingsDaemon.Wwan.desktop
-rw-r--r-- 1 root root   241 Dec 25 10:33 org.gnome.SettingsDaemon.XSettings.desktop
-rw-r--r-- 1 root root  8405 May  4  2023 print-applet.desktop
-rw-r--r-- 1 root root   401 Dec 20 09:54 tracker-miner-fs-3.desktop
-rw-r--r-- 1 root root   375 Dec 20 09:54 tracker-miner-rss-3.desktop
-rw-r--r-- 1 root root 12433 Jun  5  2023 user-dirs-update-gtk.desktop
-rw-r--r-- 1 root root   304 Jan 18 15:42 wallpaper-once.desktop
-rw-r--r-- 1 root root   461 Jan 18 15:42 welcome.desktop
-rw-r--r-- 1 root root   208 Jan  7 05:39 xapp-sn-watcher.desktop

Let’s see what happens.

[Nomad]

Sometimes it’s as simple as a corrupted installation. Have you by any chance performed a clean installation to see what that results?

[mihalycsaba]

Removing autostart items definitely helped, now at least I can log in most of the time.

@Nomad

Sometimes it’s as simple as a corrupted installation.

I would rather not do that. I don’t think there’s an issue with the installed files, might be a problem with the user configs. If it keeps happening I will make a new user, pretty sure I wouldn’t have this problem with a new user.

[Nomad]

I know it’s not the ideal solution that people look for, but if I ever have an issue that sucks up way too much of my time and that I can’t figure out, a clean installation is the way to go.

Boils down to how much you value your time.

[JacobGates]

I’m having this issue as well and I’ve reinstalled twice now. It always works for a little while then suddenly the problem starts. This most recent install I painstakingly installed one package at a time and rebooted after and it never came up again. Then after setting up my preferences it happened again. So this suggests to me that there’s a setting conflicting or something. But reinstall definitely didn’t work.

[mihalycsaba]

Which preferences? Post a log. Let’s compare.

[JacobGates]

I wish I knew which preferences. If I did I would reset them so I could use my laptop. But I just start changing things that I didn’t expect to be the issue like wallpaper, gnome extensions (which I’ve also tried disabling after the problem started), just average user experience stuff. I’m not sure how you got some the logs you did. I ran the same journalctl -f command but it’s not really showing anything interesting. I am getting some weird error wireplumber: “failed to call lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera”. No idea why wireplumber wants to access the camera.

[mihalycsaba]

post a log, I want to compare it to mine

[heavyjoe]

I got the same problem. Can somebody confirm that they only happen after updating (yay -Syu)?
I have yet to check what has been updated after a freeze occures because i already hard reset by reflex…

Update:
Here is my boot log: https://pastebin.com/LDD8H7xQ
Login starts at Jan 27 12:57:56

I got the Failed to start Application launched by gnome-session-binary. as well…?!

[mihalycsaba]

@heavyjoe

Can somebody confirm that they only happen after updating (yay -Syu)?

Not sure what you mean. It started happening more than a month ago for me, sometime at the release of the 6.6 kernel. Almost at every boot. I didn’t have time to tinker with it, I’ve just been restarting until it works.

I see a few dbus errors in your log. I don’t think it’s because of the new dbus daemon, it started way before that.

I do see these x2dkeyring errors in your log, and these are maybe the autostart items what mbod mentioned. You should try removing those, maybe it helps you. It didn’t do much for me and I didn’t have time to verify every item.

@mbod

gnome-keyring-pkcs11.desktop  
gnome-keyring-secrets.desktop  
user-dirs-update-gtk.desktop  
wallpaper-once.desktop

From your log:

Jan 27 12:57:57 endeavourpc systemd[1401]: app-gnome-gnome\x2dkeyring\x2dsecrets-1515.scope: PID 1515 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-1515.scope', skipping: No such process
Jan 27 12:57:57 endeavourpc systemd[1401]: app-gnome-gnome\x2dkeyring\x2dsecrets-1515.scope: No PIDs left to attach to the scope's control group, refusing.
Jan 27 12:57:57 endeavourpc systemd[1401]: app-gnome-gnome\x2dkeyring\x2dsecrets-1515.scope: Failed with result 'resources'.
Jan 27 12:57:57 endeavourpc systemd[1401]: Failed to start Application launched by gnome-session-binary.

Maybe it has to do something with the https://wiki.archlinux.org/title/XDG_Desktop_Portal But I not exactly sure what it does or how to ceck which one are you using.
Also what kind of cpu and gpu you have?

[heavyjoe]

Hi and thanks for the reply @mihalycsaba

I can’t say on which kernel it startet, because it was like one time and then maybe three weeks no problems (assume i use it every day). Now it is almost every first boot.
After every hard reset (reset button on pc case) it works for me, never have to reboot multiple times.

Thanks for the keyring hint. I have now disabled the autostart stuff for the keyring and will see what happens. If that changes nothing, i will uninstall my flatpaks with the xdg-desktop-portal-* (Current Version: 1.18.2-1) and observe again…

Switched from Arch/Swaywm to Endeavouros/Gnome to not have these problems anymore… well here we are… ^^

I will report back here if I gained some new intel…

CPU: AMD Ryzen 5 5600X
GPU: Sapphire Radeon RX 6700

[mihalycsaba]

In the beginning it happened only once in a while. For me it got really bad after the latest linux-firmware and amd-ucode update. I have ryzen 5700g. I looked around in the relevant issue trackers, but didn’t see anything with this login issue.

[mbod]

@mihalycsaba

linux-firmware and amd-ucode

linux-firmware and amd-ucode package for Ryzen processors was just discussed in the german forum.

The conclusion is, neither amd-ucode nor linux-firmware contain relevant microcode for AMD desktop processors. Microcode updates for Ryzen desktop CPUs typically comes through UEFI/BIOS updates.

Check the links in this post to follow up.

Amd-ucode brauch ich das?

Hier ist ein Reddit Post, der auch weitere Links enthält. Die Gentoo Wiki erwähnt es auch. D.h. obwohl die Dateien wohl eine ganze CPU-Familie abdecken sollen, sind nicht alle CPU Modelle enthalten. Am häufgisten sind davon wohl die Ryzen APUs / Laptop CPUs betroffen. Und hier auch noch aus den Kommentaren von Phoronix.

Therefore it is unlikely that any of these two packages can break your CPU.

[JacobGates]

sorry for the late reply, had a busy weekend. I actually found the reason for my issues. Weirdly when I change my keyboard backlight via the gnome slider it causes the issues. I switched to TTY3 and managed to change the setting back to off and I could log back into gnome without issues. I have a system76 laptop and I used their cli to change it back. Not sure if that is something you can also do. It’s possible that my issue is just different but causes a similar effect. Here are my logs from a while back when the issue was still happening, if it helps at all.
https://0x0.st/HImL.txt