Issues with resume from Suspend. System cannot enter user login when resuming from suspend/sleep

Ask Fedora
,
1

Hi everyone. I’m having a strange issue on my two-month-old Fedora 42 system.

Every time I manually suspend or close the lid of my laptop, then resume or open the lid, instead of going to the user login screen, it opens a blank black screen for about one second before resuming to the desktop without requiring a login.

System Details Report

Report details

  • Date generated: 2025-07-03 13:35:21

Hardware Information:

  • Hardware Model: Framework Laptop 13 AMD Ryzen 7040Series
  • Memory: 32.0 GiB
  • Processor: AMD Ryzen™ 5 7640U w/ Radeon™ 760M Graphics × 12
  • Graphics: AMD Radeon™ 760M Graphics
  • Disk Capacity: 1.0 TB

Software Information:

  • Firmware Version: 03.09
  • OS Name: Fedora Linux 42 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 48
  • Windowing System: Wayland
  • Kernel Version: Linux 6.15.4-200.fc42.x86_64

-–

paul@fedora ~> journalctl /usr/bin/gnome-shell -b Jul 03 13:39:01 fedora gnome-shell[1827]: Running GNOME Shell (using mutter 48.3) as a Wayland display server Jul 03 13:39:01 fedora gnome-shell[1827]: Enabling experimental feature 'scale-monitor-framebuffer' Jul 03 13:39:01 fedora gnome-shell[1827]: Enabling experimental feature 'xwayland-native-scaling' Jul 03 13:39:01 fedora gnome-shell[1827]: Thread 'KMS thread' will be using high priority scheduling Jul 03 13:39:01 fedora gnome-shell[1827]: Device '/dev/dri/card1' prefers shadow buffer Jul 03 13:39:01 fedora gnome-shell[1827]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting. Jul 03 13:39:01 fedora gnome-shell[1827]: Created gbm renderer for '/dev/dri/card1' Jul 03 13:39:01 fedora gnome-shell[1827]: GPU /dev/dri/card1 selected primary from builtin panel presence Jul 03 13:39:01 fedora gnome-shell[1827]: Obtained a high priority EGL context Jul 03 13:39:02 fedora gnome-shell[1827]: Using public X11 display :1024, (using :1025 for managed services) Jul 03 13:39:02 fedora gnome-shell[1827]: Using Wayland display name 'wayland-0' Jul 03 13:39:02 fedora gnome-shell[1827]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Jul 03 13:39:02 fedora gnome-shell[1827]: Extension apps-menu@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/apps-menu@gnome-shell-extensions.gcampax.git> Jul 03 13:39:02 fedora gnome-shell[1827]: Extension background-logo@fedorahosted.org already installed in /usr/share/gnome-shell/extensions/background-logo@fedorahosted.org. /usr/share/gnome-shell/extens> Jul 03 13:39:02 fedora gnome-shell[1827]: Extension launch-new-instance@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/launch-new-instance@gnome-shell-ex> Jul 03 13:39:02 fedora gnome-shell[1827]: Extension places-menu@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/places-menu@gnome-shell-extensions.gcampax> Jul 03 13:39:02 fedora gnome-shell[1827]: Extension window-list@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/window-list@gnome-shell-extensions.gcampax> Jul 03 13:39:02 fedora gnome-shell[1827]: Extension appindicatorsupport@rgcjonas.gmail.com already installed in /usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com. /usr/share/gnome-> Jul 03 13:39:02 fedora gnome-shell[1827]: Failed to parse saved session file: Failed to open file “/var/lib/gdm/.config/mutter/sessions/104590c021552dd05e175156434131549900000018150000.ms”: No such file > Jul 03 13:39:03 fedora gnome-shell[1827]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Jul 03 13:39:03 fedora gnome-shell[1827]: Will monitor session c1 Jul 03 13:39:03 fedora gnome-shell[1827]: Registering session with GDM Jul 03 13:39:12 fedora gnome-shell[2703]: Running GNOME Shell (using mutter 48.3) as a Wayland display server Jul 03 13:39:13 fedora gnome-shell[2703]: Enabling experimental feature 'scale-monitor-framebuffer' Jul 03 13:39:13 fedora gnome-shell[2703]: Enabling experimental feature 'xwayland-native-scaling' Jul 03 13:39:13 fedora gnome-shell[2703]: Thread 'KMS thread' will be using high priority scheduling Jul 03 13:39:13 fedora gnome-shell[2703]: Device '/dev/dri/card1' prefers shadow buffer Jul 03 13:39:13 fedora gnome-shell[2703]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting. Jul 03 13:39:13 fedora gnome-shell[2703]: Created gbm renderer for '/dev/dri/card1' Jul 03 13:39:13 fedora gnome-shell[2703]: GPU /dev/dri/card1 selected primary from builtin panel presence Jul 03 13:39:13 fedora gnome-shell[2703]: Obtained a high priority EGL context Jul 03 13:39:13 fedora gnome-shell[2703]: Using public X11 display :0, (using :1 for managed services) Jul 03 13:39:13 fedora gnome-shell[2703]: Using Wayland display name 'wayland-0' Jul 03 13:39:13 fedora gnome-shell[2703]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Jul 03 13:39:14 fedora gnome-shell[2703]: Will monitor session 2 Jul 03 13:39:14 fedora gnome-shell[2703]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Jul 03 13:39:14 fedora gnome-shell[2703]: loading default theme (Adwaita) Jul 03 13:39:15 fedora gnome-shell[2703]: GNOME Shell started at Thu Jul 03 2025 13:39:14 GMT-0400 (Eastern Daylight Time) Jul 03 13:39:15 fedora gnome-shell[2703]: Registering session with GDM Jul 03 13:39:15 fedora gnome-shell[1827]: Connection to xwayland lost Jul 03 13:39:15 fedora gnome-shell[1827]: Xwayland terminated, exiting since it was mandatory Jul 03 13:39:15 fedora gnome-shell[1827]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly :///org/gnome/shell/ui/init.js:21:20 Jul 03 13:39:15 fedora gnome-shell[1827]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception

-—

paul@fedora \~ \[SIGINT\]> journalctl -b -g "suspend|resume|sleep|wake" Jul 03 13:38:42 fedora kernel: Low-power S0 idle used by default for system suspend Jul 03 13:38:42 fedora kernel: rtc\_cmos 00:01: RTC can wake from S4 Jul 03 13:38:43 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend

-—

paul@fedora \~> journalctl -u gdm.service -b Jul 03 13:39:00 fedora systemd\[1\]: Starting gdm.service - GNOME Display Manager... Jul 03 13:39:00 fedora systemd\[1\]: Started gdm.service - GNOME Display Manager. Jul 03 13:39:11 fedora gdm-password\]\[2536\]: gkr-pam: unable to locate daemon control file Jul 03 13:39:11 fedora gdm-password\]\[2536\]: gkr-pam: stashed password to try later in open session Jul 03 13:39:15 fedora gdm\[1739\]: Gdm: Child process -1807 was already dead.

Based on the errors, I think GDM is failing due to gkr-pam, but I’m unsure what the next steps are.

What do you think I should be looking for to fix this issue?

3

Is it a one time problem or does it repeat?
From the logs (please try to format them better next time), it looks like you were having two gnome-shell instances while the first crashed and got replaced with another one. This could be the reason for GDM behaving strangely.

The first Gnome instance starts at 13:39:01:

 Jul 03 13:39:01 fedora gnome-shell[1827]: Running GNOME Shell (using mutter 48.3) as a Wayland display server

It uses two experimental features. This might affect the system’s behaviour. Try to switch this off. Are you using screen scaling?

Jul 03 13:39:01 fedora gnome-shell[1827]: Enabling experimental feature 'scale-monitor-framebuffer'
Jul 03 13:39:01 fedora gnome-shell[1827]: Enabling experimental feature 'xwayland-native-scaling'

It cannot find a session file (were the logs taken at the point of going awake?) If so, this could be the reason why the system cannot continue where it went to sleep.

Jul 03 13:39:02 fedora gnome-shell[1827]: Failed to parse saved session file: Failed to open file “/var/lib/gdm/.config/mutter/sessions/104590c021552dd05e175156434131549900000018150000.ms”: No such file

Then is seems to have started after all.

Jul 03 13:39:03 fedora gnome-shell[1827]: Registering session with GDM

And then XWayland crashed:

Jul 03 13:39:15 fedora gnome-shell[1827]: Connection to xwayland lost
Jul 03 13:39:15 fedora gnome-shell[1827]: Xwayland terminated, exiting since it was mandatory
Jul 03 13:39:15 fedora gnome-shell[1827]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly :///org/gnome/shell/ui/init.js:21:20
Jul 03 13:39:15 fedora gnome-shell[1827]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception

And another instance started, see the higher PID:

Jul 03 13:39:12 fedora gnome-shell[2703]: Running GNOME Shell (using mutter 48.3) as a Wayland display server
...
Jul 03 13:39:13 fedora gnome-shell[2703]: Using public X11 display :0, (using :1 for managed services)
Jul 03 13:39:13 fedora gnome-shell[2703]: Using Wayland display name 'wayland-0'
...
Jul 03 13:39:14 fedora gnome-shell[2703]: GNOME Shell started at Thu Jul 03 2025 13:39:14 GMT-0400 (Eastern Daylight Time)

And the info about the stashed password could indicate it had known the password already, so it used it open the session.

However, I am not the gnome-shell nor gdm maintainter, so the above is just a collection of assumptions.

4

Thank you. I just got back to this.

This problem always happens when returning from suspend. And while Fractional Scaling is enabled, I currently do not use it.

The logs were taken by.
Turning the computer on, logging in, going into suspend mode (closing the lid), waiting a few seconds to a minute, and then opening the lid back up.

I will look into the rest and report back. Thank you for the helpful pointers.