On 03/02/2021 14:09, Stephen Morris wrote:
For me systemctl status gdm gives:
gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled;
vendor preset: enabled)
Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago
Main PID: 1221 (gdm)
Tasks: 3 (limit: 19120)
Memory: 5.5M
CPU: 280ms
CGroup: /system.slice/gdm.service
└─1221 /usr/sbin/gdm
Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display Manager...
Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager.
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam:
unable to locate daemon control file
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam:
stashed password to try later in open session
Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process
-1267 was already dead.
What I'm not sure at the moment is how to find out what process -1267 is.
The bugzillas referenced so far have been against sddm. Your issues seem unrelated.
There have been fixes to sddm to address those issues. You may wish to try sddm instead
of gdm to
see if you still have issues. The most current sddm is still in updates-testing. So, if
you wan to give
it a try....
dnf --enablerepo updates-testing update sddm
systemctl --now enable sddm
The reboot....
--
The key to getting good answers is to ask good questions.