Bug 499266 - Auto-hide panel stops re-appearing when touched after HDMI-connected screen turns off and then back on again
Summary: Auto-hide panel stops re-appearing when touched after HDMI-connected screen t...
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (other bugs)
Version First Reported In: 6.2.5
Platform: NixOS Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland-only
Depends on:
Blocks: 478797
  Show dependency treegraph
 
Reported: 2025-01-29 08:21 UTC by jakub
Modified: 2026-01-12 20:37 UTC (History)
5 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 jakub 2025-01-29 08:21:42 UTC
SUMMARY
Plasma taskbar disappears after turning the display back on.

STEPS TO REPRODUCE
1. Use an HDMI display
2. Set the taskbar panel Visbility to auto hide (not sure if it's relevant)
3. Enable Turn off screen in Power Management, but disable Suspending
4. Go idle for a while until the screen turns off
5. Turn off the display physically if it doesn't do so on its own (mine does after 15min of no signal being received)
6. Wait a little while for good measure
7. Turn the screen on, then wake the computer up

OBSERVED RESULT
Half the time, Plasma taskbar doesn't show up anymore, the start menu works when pressing Super but the only way to bring plasma widgets back is `systemctl --user restart plasma-plasmashell`.

EXPECTED RESULT
Plasma widgets should be there as normal

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS 25.05
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Nvidia: 565.77

ADDITIONAL INFORMATION
I'm guessing this is caused by the HDMI display not reporting its resolution anymore when it powers down for real. It's an LG G2 TV.
KWin does have other issues with my HDMI displays, like it sometimes won't remember what refresh rate I'd chosen and defaults to 60. I don't have any displayport displays to test at the moment.
Comment 1 Nate Graham 2025-01-29 19:11:52 UTC
Are there any other negative effects, such as the desktop background turning black?

Is this happening on X11, Wayland, or both?
Comment 2 jakub 2025-01-29 20:20:04 UTC
This is on wayland, I haven't tested X11 (yet). Background remains the same as before, doesn't turn black.
Comment 3 jakub 2025-02-11 12:11:18 UTC
I've tested X11 for a bit and did not experience this. Will update if I do manage to reproduce it there.
Comment 4 gvgeo 2025-02-14 15:52:13 UTC
Same problem here
Wayland only
AMD gpu
DisplayPort QHD 165hz Monitor
Also tested combinations with hdmi HD TV. While it was connected there were no issues; even as the solo display output, disconnecting did not cause the problem.

Crashes occur only when the single monitor is disconnected, either by
idle timeout, or
removing cable or
turning it off completely (by default goes to standby and reports info).

Operating System: Garuda Linux (Arch)
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-zen1-1-zen (64-bit)

Related plasmashell output when the taskbar crashes:
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
qt.qpa.wayland: There are no outputs - creating placeholder screen
kde.plasmashell: requesting unexisting screen available rect -1
kde.plasmashell: requesting unexisting screen available rect -1
kde.plasmashell: requesting unexisting screen available rect -1
kde.plasmashell: requesting unexisting screen available rect -1
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
org.kde.applets.brightness: D-Bus action "KeyboardBrightnessControl" is not available at service "org.kde.Solid.PowerManagement"
org.kde.applets.brightness: D-Bus action "KeyboardBrightnessControl" is not available at service "org.kde.Solid.PowerManagement"
Comment 5 Haakon Nilsen 2025-02-15 07:38:28 UTC
It looks like several of the comments on #497204 (including mine) describe this same problem.

I'm definitely seeing the same thing on Plasma 6.3, also with HDMI, although with an Intel GPU.
Comment 6 gvgeo 2025-02-21 14:56:59 UTC
(In reply to Haakon Nilsen from comment #5)
> It looks like several of the comments on #497204 (including mine) describe
> this same problem.
> 
> I'm definitely seeing the same thing on Plasma 6.3, also with HDMI, although
> with an Intel GPU.

Indeed #497204 is very similar and probably same cause. 

I did check again. And although X11 does not appear to crash the panel(maybe it does, but recovers it too fast) when turning off the display,  soon turns on again as it does in wayland.
And has the same 2 errors in log without crashing:
kde.plasmashell: requesting unexisting screen available rect -1
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.

Marking as duplicate, for now. If more differentiated info comes up, can reopen.

*** This bug has been marked as a duplicate of bug 497204 ***
Comment 7 jakub 2025-11-05 17:32:13 UTC
So I don't see any mentions of qDeleteAll<QList<QSGCurveAbstractNode*> in my logs. my plasma shell just kind of disappears. I have a KWin script detect when the dock window of plasma closes and I make it run a systemctl restart plasma-plasmashell to recover.

For a while, this was masked by #506650 because KWin itself would lose my whole video output when switching displays. Now that NVidia seems to have fixed some HDMI output bugs in 580.105.08, I am still getting this on plasma 6.5.1.
Comment 8 Nate Graham 2025-12-08 23:11:11 UTC
The use of workaround scripts like those are going to cause a lot of issues and make it difficult to debug the issue, I'm afraid.

If pressing the super key works, then Plasmashell hasn't crashed (or at least, if it did crash, it restarted itself, so the issue should then be gone).
Comment 9 TraceyC 2025-12-24 19:47:26 UTC
I'd like to try to reproduce this. I have a question about your steps to reproduce.

STEPS TO REPRODUCE
1. Use an HDMI display
2. Set the taskbar panel Visbility to auto hide (not sure if it's relevant)

Is this a single screen setup, where the HDMI monitor is the only display?
Comment 10 Bug Janitor Service 2026-01-08 03:46:59 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 11 jakub 2026-01-08 12:26:36 UTC
(In reply to TraceyC from comment #9)
> I'd like to try to reproduce this. I have a question about your steps to
> reproduce.
> 
> STEPS TO REPRODUCE
> 1. Use an HDMI display
> 2. Set the taskbar panel Visbility to auto hide (not sure if it's relevant)
> 
> Is this a single screen setup, where the HDMI monitor is the only display?

I have two HDMI monitors but only ever use one at a time. I change between them with an atomic kscreen-doctor command
Comment 12 TraceyC 2026-01-09 01:29:56 UTC
Thanks for detailing your setup. To clarify the problems in bug 497204, that is a crash with a backtrace. This issue doesn't appear to involve a crash. So while the symptoms may look the same, the cause appears to be different and bug 497204 is different than this.

I'm not able to reproduce this using the same setup and steps on Plasma built from git-master, using a mouse. Unfortunately, I don't have an HDMI screen that supports touch to test with.

I'll leave this open in case others can reproduce.
Comment 13 Haakon Nilsen 2026-01-09 10:51:50 UTC
I believe I can reproduce this reliably. I use Arch Linux and have Wayland, Plasma 6.5.4, Qt 6.10.1, Linux 6.17.9.

My setup is a laptop with its lid closed and an external monitor connected to the laptop with HDMI.

The most immediate way to reproduce is to simply turn off the monitor. When I turn it back on again, the plasma-shell is no longer visible. I can still press Super to open the menu.

journalctl shows (among other noise during monitor off/on) these that might be of interest:

    plasmashell[1483741]: There are no outputs - creating placeholder screen
    plasmashell[1483741]: requesting unexisting screen available rect -1
    plasmashell[1483741]: Exposed with no visual parent. Window positioning broken.

I go through this every morning when I wake the laptop off. The laziest way I have found to wake plasma-shell up again is to lift the laptop's lid up for a second and then close it.

Hope this helps, and let me know what else I can do.
Comment 14 jakub 2026-01-09 12:02:52 UTC
(In reply to Haakon Nilsen from comment #13)
> I go through this every morning when I wake the laptop off. The laziest way
> I have found to wake plasma-shell up again is to lift the laptop's lid up
> for a second and then close it.

If you want to automate the recovery, I detailed the script I use in bug 497204. It's a KWin script that detects the dock window disappearing and restarts the plasma shell with systemd. https://bugs.kde.org/show_bug.cgi?id=497204#c44
Comment 15 TraceyC 2026-01-12 20:37:26 UTC
(In reply to Haakon Nilsen from comment #13)
> The most immediate way to reproduce is to simply turn off the monitor. When
> I turn it back on again, the plasma-shell is no longer visible. I can still
> press Super to open the menu.

I tried this, and still can't reproduce on Plasma built from git-master or 6.5.4. Display problems like this can be affected by differences in the displays themselves and other hardware, so that's not definitive. 

> journalctl shows (among other noise during monitor off/on) these that might
> be of interest:
> 
>     plasmashell[1483741]: There are no outputs - creating placeholder screen
>     plasmashell[1483741]: requesting unexisting screen available rect -1
>     plasmashell[1483741]: Exposed with no visual parent. Window positioning
> broken.

This is useful. I don't see that in my logs.