Hi guys, maybe some of you could have an idea about what is happening.
After upgrade to Gnome 45, the Display Manager has this weird behavior, not all time but sometimes after lock screen or suspending the laptop: The GDM starts a new session, and I can not went back to my previous opened apps.
When the GDM appears with the purple background everything works fine, but when it appears with gray default from GNOME it starts a new session.
Hi Scaloni,
Look into GDM logs to see if there are any error messages or warnings related to the issue. You can find GDM logs in the /var/log directory. Check the gdm and Xorg logs for any relevant information.
journalctl -xe | grep gdm
cat /var/log/Xorg.0.log
✗ journalctl -xe | grep gdm
jan 11 08:20:49 aorus5se gdm-autologin][968]: pam_unix(gdm-autologin:session): session closed for user gustavo
jan 11 08:20:49 aorus5se systemd-logind[755]: New session 3 of user gdm.
░░ Subject: A new session 3 has been created for user gdm
░░ A new session with the ID 3 has been created for the user gdm.
jan 11 08:20:49 aorus5se (systemd)[56830]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[gdm] ruser=[<unknown>] rhost=[<unknown>]
jan 11 08:20:49 aorus5se (systemd)[56830]: pam_unix(systemd-user:session): session opened for user gdm(uid=120) by gdm(uid=0)
jan 11 08:20:49 aorus5se systemd[1]: Started Session 3 of User gdm.
jan 11 08:20:49 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=56848 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
jan 11 08:20:49 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
jan 11 08:20:49 aorus5se gnome-session[56848]: gnome-session-binary[56848]: WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
jan 11 08:20:49 aorus5se gnome-session-binary[56848]: WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=120 pid=56860 comm="/usr/bin/gnome-shell")
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Successfully activated service 'org.a11y.Bus'
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56911]: dbus-daemon[56911]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=56860 comm="/usr/bin/gnome-shell")
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56911]: dbus-daemon[56911]: Successfully activated service 'org.a11y.atspi.Registry'
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56915]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activating service name='org.gnome.Shell.Screencast' requested by ':1.3' (uid=120 pid=56860 comm="/usr/bin/gnome-shell")
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=120 pid=56860 comm="/usr/bin/gnome-shell")
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=120 pid=56860 comm="/usr/bin/gnome-shell")
jan 11 08:20:50 aorus5se org.gnome.Shell.desktop[56860]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm/.config/mutter/sessions/109b5e1d7da583ba9a170497204959063400000568480000.ms”: No such file or directory
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activating service name='org.freedesktop.systemd1' requested by ':1.20' (uid=120 pid=57025 comm="/usr/lib/gsd-sharing")
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Successfully activated service 'org.gnome.Shell.Notifications'
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activating service name='ca.desrt.dconf' requested by ':1.3' (uid=120 pid=56860 comm="/usr/bin/gnome-shell")
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Successfully activated service 'ca.desrt.dconf'
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Successfully activated service 'org.gnome.Shell.Screencast'
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Activating service name='org.gnome.ScreenSaver' requested by ':1.22' (uid=120 pid=56967 comm="/usr/lib/gsd-power")
jan 11 08:20:50 aorus5se /usr/lib/gdm-wayland-session[56847]: dbus-daemon[56847]: [session uid=120 pid=56847] Successfully activated service 'org.gnome.ScreenSaver'
jan 11 08:21:51 aorus5se gdm-password][57270]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=gustavo
jan 11 08:21:57 aorus5se gdm-password][57320]: gkr-pam: unable to locate daemon control file
jan 11 08:21:57 aorus5se gdm-password][57320]: gkr-pam: stashed password to try later in open session
jan 11 08:21:57 aorus5se gdm-password][57320]: pam_unix(gdm-password:session): session opened for user gustavo(uid=1000) by gustavo(uid=0)
jan 11 08:21:57 aorus5se gdm-password][57320]: gkr-pam: unlocked login keyring
jan 11 08:22:00 aorus5se gdm[856]: Gdm: Child process -56839 was already dead.
jan 11 08:22:10 aorus5se (sd-pam)[56831]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[gdm] ruser=[<unknown>] rhost=[<unknown>]
It looks like there are several warnings and errors in the GDM logs. Here are a few key points to consider:
Failed Activation of org.freedesktop.systemd1:
The logs indicate that there’s an issue with activating the service ‘org.freedesktop.systemd1’. This might be related to a problem with the systemd service. You can investigate further by checking the systemd logs and ensuring that the systemd service is running properly.
journalctl -xe | grep systemd
Failed to Parse Saved Session File:
There’s a warning about the GNOME Shell failing to parse a saved session file. This could be related to a corrupted or missing session file. You may want to try resetting the GNOME Shell settings or creating a new user to see if the issue persists.
Authentication Failure in gdm-password:
There is an authentication failure in the gdm-password process. Check if the user credentials are correct and if there are any issues with the PAM (Pluggable Authentication Modules) configuration.
cat /etc/pam.d/gdm-password
Ensure that the PAM configuration is correct, and there are no misconfigurations that might be causing authentication issues.
gkr-pam: unable to locate daemon control file:
The gkr-pam daemon control file cannot be located. This might be a permissions or configuration issue related to the gnome-keyring. Ensure that the gnome-keyring service is running, and there are no issues with its configuration.
systemctl status gnome-keyring
Session Closing and Opening:
The logs show sessions being closed and opened. This might be related to the issue of starting a new session after the lock screen or suspending the laptop. Investigate if there are specific conditions triggering the session closure.
Based on the information provided, these are general areas to investigate. We may need to dig deeper into each issue and explore potential solutions.