I transitioned my EOS install from Cinnamon to Gnome recently. I uninstalled lightdm and installed gdm. When the computer starts, I get the gdm login screen and can log in just fine. However, if I subsequently log out from inside of my Gnome session, I get a black screen with some weird boot screen artifacts, and the system appears totally unresponsive (CTRL_ALT_F3 or similar to switch sessions doesn’t work). I am forced to hard reboot the computer. I don’t log out/back in all that often, so this isn’t a deal breaker, but I’d like to get this functionality working if possible. Thank you for your help!
Does it happen on Wayland, or on Xorg, or both?
i would start with moving some configs… Gnome does its own thing with theming setup cinnamons old configs could be in the way of it…
at least start with moving gtk stuff:
mv ~/.config/gtk-2.0 ~/.config/gtk-2.0.bak
mv ~/.config/gtk-3.0 ~/.config/gtk-3.0.bak
mv ~/.config/gtk-4.0 ~/.config/gtk-4.0.bak
try login to TTY by pressing CtrlAltF4
And the most clean would be to start with a new user, but make sure cinnamon settings package is removed yay -R eos-settings-cinnamon
if not it will recreate cinnamon setup for new user.
You can go like this:
- login as root to TTY
- remove current user:
a. move your files:mv /home/username /home/backup
b. delet old user:userdel username - recreate user
useradd -m -G wheel,sys,rfkill username - make backup your own:
chown -R username:username /home/backup - reboot and login as new-old username
- copy your personal files back from /home/backup (only personal files and may configs for email client browser e.t.c. one by one)
no guaranty !! always backup³
2 Likes
Happens under both Wayland and Xorg.
I followed these steps, but still the same result. Since the system was fairly fresh, I decided to reinstall selecting Gnome as the desktop environment. However, I am still having this issue on my nearly fresh install. Here’s the journalctl for gdm.service, in case that helps:
May 10 09:10:44 my-endeavouros systemd[1]: Starting GNOME Display Manager...
May 10 09:10:44 my-endeavouros systemd[1]: Started GNOME Display Manager.
May 10 09:10:44 my-endeavouros gdm-autologin][655]: pam_systemd_home(gdm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 10 09:10:44 my-endeavouros gdm-autologin][655]: pam_unix(gdm-autologin:session): session opened for user my(uid=1000) by (uid=0)
May 10 09:10:44 my-endeavouros gdm-autologin][655]: gkr-pam: couldn't unlock the login keyring.
May 10 09:11:45 my-endeavouros systemd[1]: Stopping GNOME Display Manager...
May 10 09:11:46 my-endeavouros gdm[644]: Gdm: Freeing conversation 'gdm-autologin' with active job
May 10 09:11:46 my-endeavouros systemd[1]: gdm.service: Deactivated successfully.
May 10 09:11:46 my-endeavouros systemd[1]: Stopped GNOME Display Manager.
-- Boot e6bdc774966544ea8d7f7a68581cebc1 --
May 10 20:07:56 my-endeavouros systemd[1]: Starting GNOME Display Manager...
May 10 20:07:56 my-endeavouros systemd[1]: Started GNOME Display Manager.
May 10 20:07:57 my-endeavouros gdm-autologin][685]: pam_systemd_home(gdm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 10 20:07:57 my-endeavouros gdm-autologin][685]: pam_unix(gdm-autologin:session): session opened for user my(uid=1000) by (uid=0)
May 10 20:07:57 my-endeavouros gdm-autologin][685]: gkr-pam: couldn't unlock the login keyring.
May 10 20:45:57 my-endeavouros systemd[1]: Stopping GNOME Display Manager...
May 10 20:45:58 my-endeavouros gdm[582]: Gdm: Freeing conversation 'gdm-autologin' with active job
May 10 20:45:58 my-endeavouros systemd[1]: gdm.service: Deactivated successfully.
May 10 20:45:58 my-endeavouros systemd[1]: Stopped GNOME Display Manager.
-- Boot 358f3e21fb074e238afc7d1a4f48fdba --
May 11 08:06:32 my-endeavouros systemd[1]: Starting GNOME Display Manager...
May 11 08:06:32 my-endeavouros systemd[1]: Started GNOME Display Manager.
May 11 08:06:32 my-endeavouros gdm-autologin][694]: pam_systemd_home(gdm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 11 08:06:32 my-endeavouros gdm-autologin][694]: pam_unix(gdm-autologin:session): session opened for user my(uid=1000) by (uid=0)
May 11 08:06:33 my-endeavouros gdm-autologin][694]: gkr-pam: couldn't unlock the login keyring.
-- Boot 99e38e2cd07f4f6cb3b947bdb078ae2d --
May 11 08:08:56 my-endeavouros systemd[1]: Starting GNOME Display Manager...
May 11 08:08:56 my-endeavouros systemd[1]: Started GNOME Display Manager.
May 11 08:08:56 my-endeavouros gdm-autologin][689]: pam_systemd_home(gdm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 11 08:08:56 my-endeavouros gdm-autologin][689]: pam_unix(gdm-autologin:session): session opened for user my(uid=1000) by (uid=0)
May 11 08:08:57 my-endeavouros gdm-autologin][689]: gkr-pam: couldn't unlock the login keyring.
this shows up multiple times, I guess this happens when you log out, don’t know if it’s a problem.
It seems too obvious that you are probably ding something during installation, that creates this problem, or else every gnome/gdm user should have reported the same behavior.
What do you mean by nearly? Isn’t it a completely fresh installation?
This is a very restricted log. In a complicated case like this, I would check for more things than the DM, although the messages already point to a keyring problem.