On Sat, Oct 12, 2024 at 8:16 PM Samuel Sieb <sam...@sieb.net> wrote: > On 10/12/24 5:07 PM, home user via users wrote: > > [...] > >> What does "systemctl status gdm" show now? I have no idea how it got > >> disabled, but if it still is, then try "systemctl enable --now gdm". > > > > It showed "disabled". I entered the command as suggested, the system > > paused for about a minute, and then displayed the graphical login screen > > (without logging me out). I lost the systemctl status gdm output before > > I could capture it. > > I shutdown and booted up. > > It booted to the graphical console. > > Now the suggested status command shows this: > > > > -bash.3[~]: systemctl status gdm > > ● gdm.service - GNOME Display Manager > > Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; > > preset: disabled) > > Drop-In: /usr/lib/systemd/system/service.d > > └─10-timeout-abort.conf > > Active: active (running) since Sat 2024-10-12 17:54:23 MDT; 4min > > 40s ago > > Main PID: 1214 (gdm) > > Tasks: 4 (limit: 19026) > > Memory: 6.2M (peak: 9.0M) > > CPU: 142ms > > CGroup: /system.slice/gdm.service > > └─1214 /usr/sbin/gdm > > > > Oct 12 17:54:23 coyote systemd[1]: Starting gdm.service - GNOME Display > > Manager... > > Oct 12 17:54:23 coyote systemd[1]: Started gdm.service - GNOME Display > > Manager. > > Oct 12 17:54:24 coyote gdm[1214]: Gdm: on_display_added: assertion > > 'GDM_IS_REMOTE_DISPLAY (display)' failed > > Oct 12 17:55:11 coyote gdm-password][1830]: gkr-pam: unable to locate > > daemon control file > > Oct 12 17:55:11 coyote gdm-password][1830]: gkr-pam: stashed password to > > try later in open session > > Oct 12 17:55:15 coyote gdm[1214]: Gdm: on_display_added: assertion > > 'GDM_IS_REMOTE_DISPLAY (display)' failed > > Oct 12 17:55:32 coyote gdm[1214]: Gdm: Child process -1318 was already > > dead. > > Oct 12 17:55:32 coyote gdm[1214]: Gdm: on_display_removed: assertion > > 'GDM_IS_REMOTE_DISPLAY (display)' failed > > -bash.4[~]: > > > > This seems like another good step forward. But what are the 3 "failed" > > lines and the "unable to locate" message? Problems or something I can > > ignore? > > That's expected. It's checking if it's displaying to a remote display > and that check is failing. > > I think you're all good now.
I would definitely consider some post-upgrade clean-ups as detailed in <https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-optional-post-upgrade-tasks>. At minimum, there are some old packages and a lot of dangling symlinks that should be cleaned up. Jeff -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
