Bug 513150 - External HDMI monitor doesn't automatically wake up from sleep
Summary: External HDMI monitor doesn't automatically wake up from sleep
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Power management & brightness (other bugs)
Version First Reported In: 6.5.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-12-10 00:39 UTC by Jinu
Modified: 2025-12-22 21:58 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Output of "journalctl -b --user -u plasma-powerdevil.service" (79.00 KB, text/plain)
2025-12-12 23:09 UTC, Jinu
Details
Output of "journalctl -b --user -u plasma-powerdevil.service" - December 13, 2025 (79.00 KB, text/plain)
2025-12-13 17:38 UTC, Jinu
Details
Log - December 13, 2025 (28.25 KB, text/plain)
2025-12-13 18:22 UTC, Jinu
Details
KDebugsettings (42.49 KB, image/png)
2025-12-14 14:34 UTC, Bhushan Shah
Details
Log - December 14, 2025 (25.29 KB, text/plain)
2025-12-14 18:55 UTC, Jinu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jinu 2025-12-10 00:39:23 UTC
***
When resuming from sleep, external HDMI monitor doesn't wake up. Instead, I have to wake it up by mouse movements or keyboard presses.
***

SUMMARY


STEPS TO REPRODUCE
1. Put system to sleep
2. Resume system from sleep after monitor goes blank

OBSERVED RESULT
Monitor fails to power on

EXPECTED RESULT
Monitor should power on automatically when resumed from sleep/suspend

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux KDE
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
This bug was not present in KDE Plasma 6.3.
Bug seems to be present after upgrading to 6.5
Bug was present on 6.5.3 and 6.5.4

For context I have an Nvidia GeForce RTX 5090 laptop, and it is not an Nvidia driver issue as the driver remained the same but only KDE Plasma was updated. I tried upgrading the Nvidia driver just to see if the issue was fixed but it still persists. I can confidently say that this is definitely a KDE bug and not an Nvidia bug.

HARDWARE INFORMATION
Kernel Version: 6.12.48-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 24 × Intel® Core™ Ultra 9 275HX
Memory: 64 GiB of RAM (62.2 GiB usable)
Graphics Processor 1: Mesa Intel® Graphics
Graphics Processor 2: NVIDIA GeForce RTX 5090 Laptop GPU/PCIe/SSE2
Manufacturer: LENOVO
Product Name: 83F5
System Version: Legion Pro 7 16IAX10H
Comment 1 Zamundaaa 2025-12-10 19:26:32 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?
Comment 2 Jinu 2025-12-11 01:46:07 UTC
(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.
Comment 3 Bhushan Shah 2025-12-11 04:38:44 UTC
Can you please reproduce this bug, and then provide "journalctl -b --user -u plasma-powerdevil.service"?
Comment 4 Bhushan Shah 2025-12-11 04:39:15 UTC
Also can you clarify how do you resume from sleep? Is it through power button? or lid wakeup or?
Comment 5 Jinu 2025-12-11 08:47:32 UTC
(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
Comment 6 Bhushan Shah 2025-12-11 14:09:13 UTC
Please provide logs mentioned in comment #3.
Comment 7 Jinu 2025-12-12 01:36:19 UTC
(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
Comment 8 Nate Graham 2025-12-12 01:51:10 UTC
You can put it in the file and attach the file.
Comment 9 Jinu 2025-12-12 23:09:34 UTC
Created attachment 187564 [details]
Output of "journalctl -b --user -u plasma-powerdevil.service"
Comment 10 Jinu 2025-12-12 23:10:28 UTC
(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
Comment 11 Bhushan Shah 2025-12-13 11:23:40 UTC
Hi Jinu, unfortunately in log you provided it seems there is no instance of sleep/suspend being performed?
Comment 12 Jinu 2025-12-13 17:38:35 UTC
Created attachment 187591 [details]
Output of "journalctl -b --user -u plasma-powerdevil.service" - December 13, 2025
Comment 13 Jinu 2025-12-13 17:39:43 UTC
(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.
Comment 14 Jinu 2025-12-13 17:47:37 UTC
(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
Comment 15 Jinu 2025-12-13 18:22:29 UTC
Created attachment 187595 [details]
Log - December 13, 2025
Comment 16 Jinu 2025-12-13 18:24:07 UTC
(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
Comment 17 Bhushan Shah 2025-12-14 14:33:37 UTC
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?
Comment 18 Bhushan Shah 2025-12-14 14:34:44 UTC
Created attachment 187636 [details]
KDebugsettings
Comment 19 Jinu 2025-12-14 18:55:56 UTC
Created attachment 187641 [details]
Log - December 14, 2025
Comment 20 Jinu 2025-12-14 18:56:36 UTC
(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"
Comment 21 Jinu 2025-12-15 23:44:38 UTC
(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?
Comment 22 Jinu 2025-12-22 13:36:09 UTC
(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?
Comment 23 Nate Graham 2025-12-22 21:58:19 UTC
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.