| Summary: | Option Standby when closing the Lid dose not work on Thinkpad l390 | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Arthur <a.erlich> |
| Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | kdedev, nate |
| Priority: | NOR | Keywords: | efficiency-and-performance, regression |
| Version First Reported In: | 6.5.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | output from "sudo journalctl --since "2min ago" > ~/log.txt" | ||
|
Description
Arthur
2025-11-13 06:50:48 UTC
I'm not able to reproduce this on a laptop running Plasma built from git-master. The system goes to sleep both with the power button (configured to trigger sleep) and by closing the lid. Can you gather some system logs and attach them as a text file to this report? First, trigger the bug and log back in. Then, run this in a terminal: sudo journalctl --since "2min ago" > ~/log.txt And attach ~/log.txt to this report. Also, what is the output of cat /proc/acpi/wakeup | grep enabled Thanks. Created attachment 186796 [details]
output from "sudo journalctl --since "2min ago" > ~/log.txt"
Waking the device up from sleep, closing the lid and open it again shortly after.
Screen was off, so i closed the lid again and waited some seconds, opened the lid up ageing and the login prompt is shown.
Wakeup output is:
GLAN S4 *enabled pci:0000:00:1f.6
XHC S3 *enabled pci:0000:00:14.0
RP09 S4 *enabled pci:0000:00:1d.0
RP13 S4 *enabled pci:0000:00:1d.4
SLPB S3 *enabled platform:PNP0C0E:00
LID S4 *enabled platform:PNP0C0D:00
Is there something i can have a look my self?
For me it looks the event for the lid event is regeisterd and sleep/supsend is engeage but somhow it wakes up again?
I do not like the "Stopped target Sleep."
And then the NetworkManager dose some stuff while the lid is closed...
Thanks for the logs. Those more familiar with this will have to take a look from here. *** This bug has been marked as a duplicate of bug 510992 *** |