Dear Maintainer,

Dear Maintainer,

I am reporting a recurring issue with gdm3 when using GNOME on Xorg
(gnome-xorg session) after resuming from hibernation.

What led up to the situation:
The system is running Debian 12 (bookworm) with gdm3 managing a GNOME
session on X11 (Wayland explicitly not used). The issue occurs after the
system is put into hibernation (systemctl hibernate) and then powered
on again.

What exactly did you do:
I hibernated the system normally. After powering it back on, the system
attempts to restore the graphical session.

What was the outcome:
The graphical login/session does not restore correctly. The screen
remains blank or shows an incomplete GDM state (sometimes without user
avatar), and the GNOME X11 session cannot be resumed. Switching to a TTY
is possible, but the graphical session is unusable until gdm3 is
restarted or the system is rebooted.

This failure is intermittent but frequent, and it occurs even after
short hibernation periods (less than two hours).

What outcome did you expect instead:
I expected the GDM login screen or the previous GNOME Xorg session to be
restored correctly after resuming from hibernation, as it does after a
normal reboot.


Additional diagnostic information:

- The issue reliably occurs after resuming from hibernation; cold boots work correctly.
- Short hibernation periods (<2h) are sufficient to reproduce the failure.
- When the failure occurs, the GDM greeter renders incompletely: only input fields are shown, without the usual user avatar or branding.
- Wayland is intentionally disabled; the system is configured to use X11 only (gnome-xorg).
- /var/lib/AccountsService/users/<user> explicitly sets Session=gnome-xorg.
- Xorg starts successfully after resume, and gdm-session-worker and gdm-x-session processes are present.
- The failure occurs after GDM hands off to gnome-session, resulting in a black screen or blinking cursor.
- systemd reports failures starting gnome-keyring components (pkcs11, secrets, ssh).
- loginctl may fail to resolve $XDG_SESSION_ID after resume; multiple sessions remain registered and user lingering is enabled.
- Restarting systemd-logind caused immediate session failure, resulting in an unusable login state.
- After resume, Dropbox reports missing AppIndicator support, suggesting incomplete session or tray initialization.