| Summary: | External HDMI monitor doesn't automatically wake up from sleep | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Jinu <jinujohnjoseph> |
| Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | bshah, frederick888, nate, postix, xaver.hugl |
| Priority: | NOR | Keywords: | regression |
| Version First Reported In: | 6.5.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Output of "journalctl -b --user -u plasma-powerdevil.service"
Output of "journalctl -b --user -u plasma-powerdevil.service" - December 13, 2025 Log - December 13, 2025 KDebugsettings Log - December 14, 2025 Black screens after resuming from sleep/suspend until hitting keyboard |
||
|
Description
Jinu
2025-12-10 00:39:23 UTC
When you say the external monitor doesn't wake up automatically, do you also mean that the internal one does wake up without any additional interaction? (In reply to Zamundaaa from comment #1) > When you say the external monitor doesn't wake up automatically, do you also > mean that the internal one does wake up without any additional interaction? I have KDE switch only to the external monitor with the internal monitor turned off. However I switched KDE to the internal screen and the same thing happens. The internal screen also fails to turn on automatically unless I move my mouse. Can you please reproduce this bug, and then provide "journalctl -b --user -u plasma-powerdevil.service"? Also can you clarify how do you resume from sleep? Is it through power button? or lid wakeup or? (In reply to Bhushan Shah from comment #4) > Also can you clarify how do you resume from sleep? Is it through power > button? or lid wakeup or? The lid is open. I press the power button to resume from sleep Please provide logs mentioned in comment #3. (In reply to Bhushan Shah from comment #3) > Can you please reproduce this bug, and then provide "journalctl -b --user -u > plasma-powerdevil.service"? How do I post the output here? I tried, but it's being marked as spam automatically You can put it in the file and attach the file. Created attachment 187564 [details]
Output of "journalctl -b --user -u plasma-powerdevil.service"
(In reply to Bhushan Shah from comment #6) > Please provide logs mentioned in comment #3. Hi, I have provided the requested log as a text file attachement Hi Jinu, unfortunately in log you provided it seems there is no instance of sleep/suspend being performed? Created attachment 187591 [details]
Output of "journalctl -b --user -u plasma-powerdevil.service" - December 13, 2025
(In reply to Bhushan Shah from comment #11) > Hi Jinu, unfortunately in log you provided it seems there is no instance of > sleep/suspend being performed? Hi Bhushan, I have attached another log taken today. Please see it. It show several instances of sleep events. (In reply to Jinu from comment #13) > (In reply to Bhushan Shah from comment #11) > > Hi Jinu, unfortunately in log you provided it seems there is no instance of > > sleep/suspend being performed? > > Hi Bhushan, I have attached another log taken today. Please see it. > It show several instances of sleep events. See attachment Output of "journalctl -b --user -u plasma-powerdevil.service" - December 13, 2025 Created attachment 187595 [details]
Log - December 13, 2025
(In reply to Jinu from comment #14) > (In reply to Jinu from comment #13) > > (In reply to Bhushan Shah from comment #11) > > > Hi Jinu, unfortunately in log you provided it seems there is no instance of > > > sleep/suspend being performed? > > > > Hi Bhushan, I have attached another log taken today. Please see it. > > It show several instances of sleep events. > > See attachment Output of "journalctl -b --user -u plasma-powerdevil.service" > - December 13, 2025 Hi disregard "Output of "journalctl -b --user -u plasma-powerdevil.service", as the same log was uploaded twice, see Log - December 13, 2025 for latest log Ah, extremely sorry! I completely missed that messages I am looking for are marked as debug messages so they would not be enabled by default. Can you, 1) enable all debug messages for Powerdevil from kdebugsettings (See attached screenshots) 2) Restart powerdevil with "systemctl --user restart plasma-powerdevil" 3) Reproduce bug and upload log? Created attachment 187636 [details]
KDebugsettings
Created attachment 187641 [details]
Log - December 14, 2025
(In reply to Bhushan Shah from comment #17) > Ah, extremely sorry! > > I completely missed that messages I am looking for are marked as debug > messages so they would not be enabled by default. > > Can you, > > 1) enable all debug messages for Powerdevil from kdebugsettings (See > attached screenshots) > 2) Restart powerdevil with "systemctl --user restart plasma-powerdevil" > 3) Reproduce bug and upload log? I have attached output as requested. See "Log - December 14, 2025" (In reply to Bhushan Shah from comment #17) > Ah, extremely sorry! > > I completely missed that messages I am looking for are marked as debug > messages so they would not be enabled by default. > > Can you, > > 1) enable all debug messages for Powerdevil from kdebugsettings (See > attached screenshots) > 2) Restart powerdevil with "systemctl --user restart plasma-powerdevil" > 3) Reproduce bug and upload log? Hello, were you able to check the logs? (In reply to Bhushan Shah from comment #17) > Ah, extremely sorry! > > I completely missed that messages I am looking for are marked as debug > messages so they would not be enabled by default. > > Can you, > > 1) enable all debug messages for Powerdevil from kdebugsettings (See > attached screenshots) > 2) Restart powerdevil with "systemctl --user restart plasma-powerdevil" > 3) Reproduce bug and upload log? Hi Bhushaan/Nate, just following up on this, were you able to find anything in the log? This isn't my area of expertise; the logs don't mean anything to me, I'm afraid. It'll have to be Bhushan or someone else. (In reply to Nate Graham from comment #23) > This isn't my area of expertise; the logs don't mean anything to me, I'm > afraid. It'll have to be Bhushan or someone else. Hi is there any development for this bug? Any possible fixes in the upcoming 6.6 release? The log just shows > Wakeup source of type QFlags<SuspendController::WakeupSource>(UnknownSource) resumed from sleep Which means powerdevil should be enabling the screen on its own. I can't think of any explanation of why it wouldn't work. https://invent.kde.org/plasma/kwin/-/merge_requests/8282 *could* help, if the cause is some race condition, but I wouldn't count on it. Created attachment 189025 [details] Black screens after resuming from sleep/suspend until hitting keyboard I'm facing exactly the same issue after migrating from X11 to Wayland a few days ago. I usually leave my laptop's lid closed and use external displays only at my desk (i.e. clamshell mode). The steps to reproduce this issue from me are very similar: 1. Sleep (suspend to RAM) 2. Wake up the laptop using either keyboard or Wake-on-LAN 3. All displays, including the laptop's internal one, stay black 4. Hit any key on the keyboard, external displays will lit up My environment: Operating System: Arch Linux KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 64 GiB of RAM (62.5 GiB usable) Graphics Processor 1: Intel® Iris® Xe Graphics Graphics Processor 2: NVIDIA GeForce RTX 3080 Ti Laptop GPU Manufacturer: LENOVO Product Name: 21DECTO1WW System Version: ThinkPad X1 Extreme Gen 5 Drivers: iGPU: i915 NVIDIA: nvidia-open-dkms 590.48.01-2 Two displays connected via HDMI and USB-C (DP Alt) each. Here's my `journalctl -b` output with irrelevant lines removed. I also enabled Full Debug logs & restarted Powerdevil beforehand. I opened my laptop's lid to reach the internal keyboard this time, so that the 'Lid opened / closed' logs could serve as dividers. One thing I noticed was that kwin spammed a lot of "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" when the screens were black, and stopped after the screens are back. BTW Bug 511811 might be the same? (In reply to Frederick Zhang from comment #26) > NVIDIA: nvidia-open-dkms 590.48.01-2 That's your problem: > Detected GPU reset on secondary GPU /dev/dri/card0 Which is to say, your Nvidia driver is not set up correctly, though I don't see why KWin wouldn't still recover from that. Either way, the bug you're describing is very different from what this bug report is about, please open a new one about your problem for KWin. (In reply to Zamundaaa from comment #27) > (In reply to Frederick Zhang from comment #26) > > NVIDIA: nvidia-open-dkms 590.48.01-2 > That's your problem: > > Detected GPU reset on secondary GPU /dev/dri/card0 > Which is to say, your Nvidia driver is not set up correctly, though I don't > see why KWin wouldn't still recover from that. Either way, the bug you're > describing is very different from what this bug report is about, please open > a new one about your problem for KWin. Hi Zamundaa, Is there anything I can do to help with this bug? Any other logs that I can provide that might help? You can test Plasma 6.6, but like I already wrote, I can't think of any reason it would happen. |