Score:2

22.04 - GDM Shell crashes (occasionally) after login

za flag

How would I diagnose a GDM crash after login. I can still SSH into the machine and I've been "fixing" broken shell session with:

$ sudo systemctl stop gdm
$ sudo systemctl start gdm

What logs would I need to look at to begin diagnosis?

Raffa avatar
jp flag
You need to check the output of `journalctl -rxu gdm`
za flag
Found this in the output: gkr-pam: unable to locate daemon control file. Trying this fix: https://askubuntu.com/questions/1144153/how-to-solve-gkr-pam-unable-to-locate-daemon-control-file
za flag
@Raffa This is the only output: GLib: Source ID 203 was not found when attempting to remove it
za flag
Nope, that didn't fix it - going to try a different greeter.
Score:0
za flag

Okay, problem solved.

I installed lightdm as the greeter and am using that. Note, I am not installing UNITY, but rather just the lightdm for the role of entering the password and logging into the GNOME shell GUI which remains unaltered.

I also needed to make sure that lightdm didn't put the machine to sleep when logged out and or "Switch Users" was chosen. To accomplish this, I followed the following post: How to disable suspend in 20 minutes from the lightdm login screen?

This has solved my issue with Ubuntu 22.04 LTS, AMD RYZEN Threadripper and an NVIDIA RTX4090 using the propreitary 530 driver.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.