| Summary: | Sleep mode does not work | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Konstantin <jon9097> |
| Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | d347h.1nc, kdedev, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Video
log |
||
|
Description
Konstantin
2025-07-16 15:38:43 UTC
This is odd. I'm not able to reproduce this in Plasma 6.4.3 or git-master. Can you get logs when you attempt to put the system to sleep? - Run this in a terminal: sudo journalctl -f - Attempt to put the system to sleep - Unlock the system when the lock screen appears - In the terminal Ctrl+C to exit the journalctl command Then copy and paste the journalctl output into a comment in this report. Thanks! Created attachment 183453 [details]
Video
Created attachment 183454 [details]
log
added videos and logs Same here but on Bazzite. Also Happens using Gnome. Sleep works just fine in Windows. I'm Assuming this is some Gigabyte specific problem as it seems their boards have had sleep issues on linux for years. Operating System: Bazzite 42 KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.15.6-105.bazzite.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 9600X 6-Core Processor Memory: 32 GiB of RAM (30.9 GiB usable) Graphics Processor: AMD Radeon RX 6800 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B850 AORUS ELITE WIFI7 System Version: Default string-CF-WCP-ADO As an update it seems to only happen if a M.2 slot that uses the southbridge and not the cpu for its lanes is populated. Apparently the m.2 SB slot wakes up linux for some reason but not windows. Using the first two ports on my board has sleep work just fine. Do you have a ssd in the third slot by chance Konstantin? According to your boards manual thats the southbridge connected one. Try only ports 1,2 and 4. (In reply to d347h.1nc from comment #6) > As an update it seems to only happen if a M.2 slot that uses the southbridge > and not the cpu for its lanes is populated. Apparently the m.2 SB slot wakes > up linux for some reason but not windows. > > Using the first two ports on my board has sleep work just fine. > > Do you have a ssd in the third slot by chance Konstantin? According to your > boards manual thats the southbridge connected one. Try only ports 1,2 and 4. Hello. I don't use m2. I have 3 SSDs and 1 hdd connected via sata Thanks for the details, this is helpful. (In reply to d347h.1nc from comment #6) > As an update it seems to only happen if a M.2 slot that uses the southbridge > and not the cpu for its lanes is populated. Apparently the m.2 SB slot wakes > up linux for some reason but not windows. Your issue definitely sounds hardware / kernel related. (In reply to Konstantin from comment #3) > Created attachment 183454 [details] > log From this part of the logs, the system reaches the suspend target, and then NetworkManager indicates a wake was requested. Do you happen to have Wake on LAN enabled in your BIOS/UEFI? ---------------- июл 23 15:11:36 Alex-PC systemd-logind[927]: Operation 'suspend' finished. июл 23 15:11:36 Alex-PC systemd[1]: Starting NVIDIA system resume actions... июл 23 15:11:36 Alex-PC systemd-resolved[855]: Closing all remaining TCP connections. июл 23 15:11:36 Alex-PC systemd-resolved[855]: Resetting learnt feature levels on all servers. июл 23 15:11:36 Alex-PC systemd[1]: Stopped target Suspend. июл 23 15:11:36 Alex-PC NetworkManager[1037]: <info> [1753272696.4227] manager: sleep: wake requested (sleeping: yes enabled: yes) июл 23 15:11:36 Alex-PC NetworkManager[1037]: <info> [1753272696.4227] device (enp12s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external') июл 23 15:11:36 Alex-PC kdeconnectd[1531]: 2025-07-23T15:11:36 kdeconnect.core: No local bluetooth adapter found июл 23 15:11:36 Alex-PC kdeconnectd[1531]: 2025-07-23T15:11:36 default: Error sending UDP packet: QAbstractSocket::NetworkError июл 23 15:11:36 Alex-PC suspend[2151]: nvidia-resume.service июл 23 15:11:36 Alex-PC logger[2151]: <13>Jul 23 15:11:36 suspend: nvidia-resume.service июл 23 15:11:36 Alex-PC systemd[1]: nvidia-resume.service: Deactivated successfully. июл 23 15:11:36 Alex-PC systemd[1]: Finished NVIDIA system resume actions. ---------------- (In reply to TraceyC from comment #9) > (In reply to Konstantin from comment #3) > > Created attachment 183454 [details] > > log > > From this part of the logs, the system reaches the suspend target, and then > NetworkManager indicates a wake was requested. Do you happen to have Wake on > LAN enabled in your BIOS/UEFI? No. I do not use this option on this PC. Thanks for confirming. I'll let the developers take it from here. This definitely seems like a kernel or firmware issue to me. I'd recommend talking to the kernel folks or Gigabyte's developers, if any of them are publicly available. |