Bug 506259 - External HDMI monitor wakes back up with black display when closing laptop lid (single display, wayland)
Summary: External HDMI monitor wakes back up with black display when closing laptop li...
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.3.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen
Depends on:
Blocks: 506459 506893
  Show dependency treegraph
 
Reported: 2025-06-27 09:30 UTC by Oleg Gorobets
Modified: 2025-08-22 07:33 UTC (History)
7 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Gorobets 2025-06-27 09:30:08 UTC
SUMMARY

This issue is related to this one: https://bugs.kde.org/show_bug.cgi?id=493879

Power management is configured as follows:
When laptop lid is closed: Turn Off Screen
[x] Even when external monitor is connected

Now, when I close the lid external monitor fails to turn off (as described in the ticket above) and then after wakeup there is no plasmashell.

Some logs from journalctl:

чер 27 11:56:28 p15v systemd-logind[736]: Lid closed.
чер 27 11:56:40 p15v kclockd[1354]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v kactivitymanagerd[1118]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v kded6[1099]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v konsole[1436]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v DiscoverNotifier[1364]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v polkit-kde-authentication-agent-1[1178]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v kgpg[1370]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v xdg-desktop-portal-kde[1180]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v plasmashell[1130]: qt.qpa.wayland: There are no outputs - creating placeholder screen
чер 27 11:56:40 p15v plasmashell[1130]: kde.plasmashell: requesting unexisting screen available rect -1
чер 27 11:56:40 p15v plasmashell[1130]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
чер 27 11:56:40 p15v plasmashell[1130]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.


STEPS TO REPRODUCE
1. Connect external display via HDMI
2. Configure Display Configuration: External monitor to be the only one enabled
3. Configure Power Management: When laptop lid is closed: Turn Off Screen
4. Configure Power Management: Check "Even when external monitor is connected"
5. Close the lid

OBSERVED RESULT
Monitor turns off, then after a few seconds turns back on with no plasmashell (no task bar, no wallpaper etc)

EXPECTED RESULT
Plasmashell is present.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
Kernel Version: 6.12.28-1-lts (64-bit)
Graphics Platform: Wayland
Comment 1 TraceyC 2025-07-01 17:17:51 UTC
As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

Thanks.
Comment 2 Oleg Gorobets 2025-07-04 08:37:07 UTC
(In reply to TraceyC from comment #1)
> As the message at the top of the summary says, if something crashed, we need
> a backtrace of it so we can figure out what's going on. Can you please
> attach a backtrace of the crash using the coredumpctl command-line program,
> as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

I don't see these crashes in coredumpctl. Maybe it's not a "crash" in Plasma terms, maybe it is hidden or inactive for some reason. But the visible result that it is completely gone. What I see is black screen with which I cannot interact (no task panel, no wallpaper, no icons, can't get a context menu on right-click). The result is the same as described in my other ticket https://bugs.kde.org/show_bug.cgi?id=487134. I use this command to get Plasma back:

kquitapp6 plasmashell && kstart plasmashell &
Comment 3 TraceyC 2025-07-07 15:11:50 UTC
Thanks for explaining the symptoms in more detail. We've had a few reports of similar behavior on different systems, where the screen wakes back up after it's supposed to sleep. We've also had reports of similar blank / black display problems. 

Can you paste the output of kinfo into this report? I'm curious what GPU(s) are in the system. Thanks.
Comment 4 TraceyC 2025-07-07 15:18:25 UTC
I just saw in bug 493879 that the part about the display waking after being told to turn off may be fixed in 6.4.3
That wouldn't necessarily fix the problem with the screen not displaying Plasma correctly when waking
Comment 5 Oleg Gorobets 2025-07-07 20:34:42 UTC
> Can you paste the output of kinfo into this report? I'm curious what GPU(s) are in the system.

Sure, see below:

$ kinfo
libEGL warning: egl: failed to create dri2 screen
Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.12.28-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 31.0 GiB of RAM
Graphics Processor 1: Mesa Intel® Iris® Xe Graphics
Graphics Processor 2: zink Vulkan 1.4

I don't know why it shows "zink Vulkan 1.4" here, the actual GPU is NVidia T600.
Comment 6 Oleg Gorobets 2025-07-08 08:49:07 UTC
There is also another error in powerdevil, which might be relevant:

лип 08 10:34:32 p15v org_kde_powerdevil[1174]: [  1174] Error(s) opening ddc devices
лип 08 10:34:32 p15v org_kde_powerdevil[1174]: [  1174] Error EACCES(-13): Permission denied opening /dev/i2c-15
Comment 7 TraceyC 2025-07-08 16:23:11 UTC
Thanks for the additional information, that's helpful.
The powerdevil errors from your logs look different than in bug 493879, but it's possible this might also be fixed in 6.4.3, since the way kwin identifies outputs was updated.

As an aside:
> I don't know why it shows "zink Vulkan 1.4" here, the actual GPU is NVidia T600.
That's probably bug 499882, if you wanted to track it.

Please let us know if you still experience this screen waking bug with 6.4.3, which should be released Tue 2025-07-15.
I'll keep this report in NEEDSINFO so it reminds us in 15 days.
Comment 8 Oleg Gorobets 2025-07-08 18:45:17 UTC
(In reply to TraceyC from comment #7)

> The powerdevil errors from your logs look different than in bug 493879

I forgot to mention that powerdevil errors only occur during Plasma startup (not when the monitor is turned off), therefore it might be completely unrelated issue. I just thought that since ddcutil deals with monitors they might be related.
Comment 9 Bug Janitor Service 2025-07-23 03:46:58 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Oleg Gorobets 2025-07-31 09:11:17 UTC
(In reply to TraceyC from comment #7)

> Please let us know if you still experience this screen waking bug with
> 6.4.3, which should be released Tue 2025-07-15.

This is somewhat better on 6.4.3, but not completely solved. I can reproduce it occasionally, especially on the first try after reboot. On the subsequent tries it seem to work well.
Comment 11 TraceyC 2025-07-31 17:08:07 UTC
Well bummer. Thanks for letting us know. Are you still seeing errors related to org_kde_powerdevil in the system logs?
Comment 12 Oleg Gorobets 2025-07-31 18:35:20 UTC
(In reply to TraceyC from comment #11)

> Are you still seeing errors related to org_kde_powerdevil in the system logs?

Yes, same org_kde_powerdevil errors during startup.
Comment 13 TraceyC 2025-08-01 00:30:03 UTC
Thanks.