| 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, nate, 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 |
||
|
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. |