Arch Linux

EgidioCaprino

Member

Registered: 2016-03-13

Posts: 108

[Solved] GDM does not show up

I installed gnome-extra, gdm and enabled gdm.service. When the system starts the screen goes black and GDM only shows up when switching between TTY2 and then back to TTY1. This is what I see in journalctl

-- Reboot --
Sep 01 20:59:22 dell systemd[1]: Starting GNOME Display Manager...
Sep 01 20:59:22 dell systemd[1]: Started GNOME Display Manager.
Sep 01 20:59:23 dell gdm[544]: Child process -634 was already dead.
Sep 01 20:59:41 dell gdm-password][946]: gkr-pam: unable to locate daemon control file
Sep 01 20:59:41 dell gdm-password][946]: gkr-pam: stashed password to try later in open session
Sep 01 20:59:41 dell gdm-password][946]: pam_systemd_home(gdm-password:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service n>
Sep 01 20:59:41 dell gdm-password][946]: pam_unix(gdm-password:session): session opened for user egidio(uid=1000) by (uid=0)
Sep 01 20:59:41 dell gdm-password][946]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring

Do you have any idea?

Last edited by EgidioCaprino (2020-09-03 08:58:25)

leminhman0312

Banned

Registered: 2020-07-12

Posts: 24

Re: [Solved] GDM does not show up

Have you tried another login manager? Lightdm and see if you can boot? Then perhaps remove gdm and reinstall it?

EgidioCaprino

Member

Registered: 2016-03-13

Posts: 108

Re: [Solved] GDM does not show up

Reinstalling gdm fixed it. Thank you!

akspecs

Member

Registered: 2012-02-11

Posts: 179

Re: [Solved] GDM does not show up

...When the system starts the screen goes black and GDM only shows up when switching between TTY2 and then back to TTY1...

I was able to deal with this issue on my end by adding adding i915 and radeon to the modules section of /etc/mkinitcpio.conf, (and then regenerating my initramfs).

e.g. add something like to your
/etc/mkinitcpio.conf

MODULES=(i915 radeon)

and then:

mkinitcpio -P

of course add the correct modules relevant to your system.

I'm not sure when I noticed this happening - perhaps it was sometime during the 5.7.*+ kernel updates?