Gnome freezes upon login

seth · 2024-06-06 15:20:31

"Gnome freezes upon login" - do you autostart chromium or are you talking about random freezes mid-session?

mathes.s · 2024-06-07 07:08:38

If you are referring to my post, yes i did start bitwarden via autostart and got frozen screens of gnome after hitting the enter button in the login screen.

BG Mathias

haritaki · 2024-06-19 09:31:22

I've also been getting this issue intermittently on a fresh install with an amdgpu.

danwood76 · 2024-07-17 11:24:32

@Seth

I just wanted to post an update on this issue (or at least the issue I was having).

I haven't seen it for a few weeks now, I remember seeing a kernel update come in but nothing gnome related after the last time I saw the hang.

So maybe the kernel update solved the issue? Not entirely sure.

ynuwyytqaw · 2024-07-17 13:18:41

@danwood76: Me too. No issues in the past couple of weeks. There was a systemd update, but I am not sure if it is related.

Muflone · 2024-07-17 14:50:31

Unfortunately I had the same issue recently, by removing the Ethernet cable and the power cable to move the laptop in another place.

Unlocking the GDM screen the whole session hangs and the shield doesn't remove itself

I had to kill gdm, losing all the unchanged data.

Max Ammann · 2024-12-06 20:40:05

I'm experiencing similar issues out of nowhere. During login GDM freezes upcompletely and swithc to different tty does not work. It happens roughly between 1/3 - 1/10 logins. However, the kernel does not lockup, so I'm still able to ping and SSH into NixOS (I'm not running arch but I think this still adds to the discussion).

I can confirm the following:
- I suspenct this is a dbus issue and lockup. If I run `pkill dbus` as my current user the spawned Gnome dbus sessions get killed and GDM crashes/continue. Doing `ps -aux | grep dbus` shows GDM and Gnome dbus sessions while GMD is locked up.
- Gnome version does not seem to affect anything. I recently upgraded to Gnome 47 and expereince the same issues.
- Other users on the installation are not affected
- Clearing the home directory does not resolve the issue
- Switch to LightDM works aroudn the issue. Sometimes logins take a long time but eventually succeed.
- Kernel versions 6.6 and 6.11 show the same behavior.

Last edited by Max Ammann (2024-12-06 20:40:39)

eagleflo · 2025-01-16 20:58:29

I guess I'm relieved to see I'm not the only one. This has been an intermittent issue for me for months by this point. Usually the very next boot works again. GDM crashes so hard that I can't switch TTY, but the kernel is still there, as I get logging for failed alt + sysrq attempts.

Failed boot: https://0x0.st/s/Nx543la6tQe73ZS_8tVJ7g/8ols.txt
Good boot right after: https://0x0.st/s/PM1YWTbz2KwPYII6iALkxg/8olz.txt

I don't think it matters but running stock Gnome, Wayland, `nvidia-open`. I guess I'll open `sshd` and try to get an interactive session going with a second computer in preparation of this inevitably happening again.

seth · 2025-01-17 10:55:52

Not sure whether the original problem wasn't just down to watch me rant
"export MUTTER_DEBUG_KMS_THREAD_TYPE=user" - though the upstream bug was closed and the pattern also isn't in your journal (hitting the RT limit wins you a kill -9 from the kernel)

Try to add "nvidia_drm.fbdev=0" to the kernel parameters.

eagleflo · 2025-01-19 13:57:23

Yeah, quite possible there are multiple different issues interleaved in this post, just with the same end result.

Did your suggested change now. Since this issue has been intermittent for me (race condition?), it will probably take a bit to see whether it helped or not. Out of curiosity and willingness to learn, what makes you recommend this change?

I seem to recall at one point in nearby past `nvidia_drm.modeset=1` and `nvidia_drm.fbdev=1` were both necessary to get Wayland working on Nvidia. Apparently fbdev isn't with the driver 565.77, despite what the wiki says right now, as I've now turned it off and still managed to get a running session.

Last edited by eagleflo (2025-01-19 13:59:44)

seth · 2025-01-19 14:13:35

Both are currently activated by default, only modeset=1 is a wayland requirement plus keeping it set explicitly wll fend of the simpledrm device that has a habit of getting in the way.
fbdev=1 has been complete hit and miss in the past w/ a weak pattern to perform better w/ the latest nvidia chips and worse w/ the earlier ones (still supported by the 565 drivers)

Arch Linux

#76 2024-06-06 15:20:31

Re: Gnome freezes upon login

#77 2024-06-07 07:08:38

Re: Gnome freezes upon login

#78 2024-06-19 09:31:22

Re: Gnome freezes upon login

#79 2024-07-17 11:24:32

Re: Gnome freezes upon login

#80 2024-07-17 13:18:41

Re: Gnome freezes upon login

#81 2024-07-17 14:50:31

Re: Gnome freezes upon login

#82 2024-12-06 20:40:05

Re: Gnome freezes upon login

#83 2025-01-16 20:58:29

Re: Gnome freezes upon login

#84 2025-01-17 10:55:52

Re: Gnome freezes upon login

#85 2025-01-19 13:57:23

Re: Gnome freezes upon login

#86 2025-01-19 14:13:35

Re: Gnome freezes upon login

Board footer