Created attachment 185913 [details] filtered jounalctl after closing and opening lid and waking up with a button SUMMARY When lid close is set to suspend and the lid gets closed, the laptop does not go into "deep" sleep and fails over to "s2idle". It seems like it is caused by Kwin_wayland not being able to postpone the sleep for the GPU to go to sleep properly. Aside from high power usage, this also causes the laptop to not wake up when the lid gets opened and needs to be waken up using the power button. The system sleeps properly when i sleep it manually using the sleep button in the "Application Launcher". This does NOT happen in Plasma 6.4.4 I am not sure if this happens on Intel laptops but my Thinkpad T14 Gen 2 with an AMD CPU does it. I included some logs. STEPS TO REPRODUCE 1. Get Plasma 6.5 Beta (doesn't matter if 1 or 2) 2. Set "Power Management" -> "When laptop lid closed" to "Suspend" 3. Close the laptop's lid OBSERVED RESULT The sleep LED blink does not start. Battery drains quickly and laptop heats up. When lid opened the laptop doesn't wake up. EXPECTED RESULT The sleep LED blink starts. No excessive battery drain in sleep. When lid opened the laptop wakes up. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.4.91 KDE Frameworks Version: 6.19.0 Qt Version: 6.10.0 Kernel Version: 6.17.3-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 5850U with Radeon Graphics Memory: 32 GiB of RAM (30.2 GiB usable) Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION My journal after trying to suspend by closing the lid is attached.
Can you confirm what login manager (SDDM/GDM you use. And output of `loginctl list-sessions`
(In reply to David Edmundson from comment #1) > Can you confirm what login manager (SDDM/GDM you use. > > And output of `loginctl list-sessions` I am using SDDM, I also tried plasma-login. vasek@argon ~ loginctl list-sessions SESSION UID USER SEAT LEADER CLASS TTY IDLE SINCE 2 1000 vasek seat0 994 user tty2 no - 3 1000 vasek - 1014 manager - no - 2 sessions listed.
Still present in the 6.5 release, could it be a bug in Arch?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
That warning isn't related to suspend happening or not. What seems to be happening is that some part of the device doesn't properly go to sleep: říj 20 08:19:43 argon kernel: PM: suspend entry (deep) říj 20 08:19:44 argon kernel: printk: Suspending console(s) (use no_console_suspend to debug) říj 20 08:19:44 argon kernel: PM: Some devices failed to suspend, or early wake event detected říj 20 08:19:44 argon kernel: PM: suspend exit říj 20 08:19:44 argon kernel: PM: suspend entry (s2idle) říj 20 08:20:00 argon kernel: printk: Suspending console(s) (use no_console_suspend to debug) říj 20 08:20:00 argon kernel: amdgpu 0000:07:00.0: amdgpu: Power consumption will be higher as BIOS has not been configured for suspend-to-idle. To use suspend-to-idle change the sleep mode in BIOS setup. říj 20 08:20:00 argon systemd-sleep[3036]: System returned from sleep operation 'suspend'. říj 20 08:20:00 argon kernel: PM: suspend exit There were some changes in powerdevil that might've caused this
I know this is old bug but bug that I was tracking previously is different so marking this as duplicate. *** This bug has been marked as a duplicate of bug 510992 ***