On 3/2/21 19:08, Ed Greshko wrote:
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....
Hi Ed, I issued the two commands and first one worked but the second
one
didn't. The second command said it couldn't create the display-manager
symlink because it already existed and was linked to gdm.service.
I then made the mistake of issuing the command systemctl disable gdm and
that blew Fedora out of the water. I rebooted but the display manager
wouldn't start.
I then used ctrl+alt+F2 to get a login prompt, logged in, and issued the
command systemctl disable display-manager and then systemctl enable sddm
and rebooted, but sddm would not start. I logged back in again at a
login prompt and issued the command systemctl status display-manager and
it said sddm was active but sddm-helper failed with exit-11.
Hence at the moment I have switched back to gdm which runs fine.
regards,
Steve