https://bugs.kde.org/show_bug.cgi?id=511985

            Bug ID: 511985
           Summary: Desktop PC can no longer suspend to RAM since upgrade
                    from Debian 12 to 13 (KDE Plasma 6.3.6)
    Classification: I don't know
           Product: kde
      Version First unspecified
       Reported In:
          Platform: Debian stable
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY

Since a recent successful upgrade from Debian 12 to 13, the Suspend
functionality no longer works, whatever the method (from the login screen, from
the Kickoff menu, using X11 or Wayland, running 'systemctl suspend' from a
terminal).
My PC starts entering the sleep state (the monitor no longer receives video
input, the keyboard LEDs go OFF), but my PC is still awake (LEDs are ON, I can
hear the fans spinning).
The only way to exit this weird state is to reboot my PC (via a dedicated
physical button on my desktop tower).

STEPS TO REPRODUCE
1. Start the desktop PC.
2. Ask it to suspend to RAM (whatever the method).

OBSERVED RESULT
The PC doesn't fully suspend to RAM (it's still running).
But there's no way to exit this weird state without rebooting the PC (the
keyboard and display are OFF).

EXPECTED RESULT
The PC should suspend to RAM completely.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux 13.1 running Linux kernel
6.12.48+deb13-amd64
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION

Last messages logged to systemd's journal:

nov. 08 13:50:36 Latour systemd-logind[690]: The system will suspend now!
[...]
nov. 08 13:50:36 Latour kscreenlocker_greet[9569]: PAM unable to
dlopen(pam_sss.so): /usr/lib/security/pam_sss.so: Ne peut ouvrir le fichier
d'objet partagé: Aucun fichier ou dossier de ce nom
nov. 08 13:50:36 Latour kscreenlocker_greet[9569]: PAM adding faulty module:
pam_sss.so
nov. 08 13:50:37 Latour systemd[1]: Reached target sleep.target - Sleep.
nov. 08 13:50:37 Latour systemd[1]: Starting systemd-suspend.service - System
Suspend...
nov. 08 13:50:37 Latour systemd[1]: session-3.scope: Unit now frozen-by-parent.
nov. 08 13:50:37 Latour systemd[1]: user.slice: Unit now frozen.
nov. 08 13:50:37 Latour systemd[1]: user-1000.slice: Unit now frozen-by-parent.
nov. 08 13:50:37 Latour systemd[1]: [email protected]: Unit now
frozen-by-parent.
nov. 08 13:50:37 Latour systemd-sleep[9606]: Successfully froze unit
'user.slice'.
nov. 08 13:50:37 Latour systemd-sleep[9606]: Performing sleep operation
'suspend'...
nov. 08 13:50:37 Latour kernel: PM: suspend entry (deep)

Then after having rebooted the PC:

-- Boot d564030b884f41c687a934d8562a6365 --
nov. 08 13:55:38 Latour kernel: Linux version 6.12.48+deb13-amd64
(debian-kernel@lists . debian . org) (x86_64-linux-gnu-gcc-14 (Debian
14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP
PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to