Panel disappears when the monitor wakes up from sleep (off) state

The panel (bar) is not displayed when the monitor is woken up after being turned off earlier by the system (power saving) or by the keyboard. To restore the correct display it is necessary to restart the Plasma environment (plasmashell --replace) or a full system reboot.

Physically turning off the monitor (with the monitor button) does not cause problems.

Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-9-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 Ɨ 11th Gen IntelĀ® Coreā„¢ i5-11600 @ 2.80GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa IntelĀ® Graphics
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D18
System Version: 1.0

1 Like

Let’s run a test, cause this to happen again and before you do anything else rightclick the desktop and chose ā€œEnter Edit Modeā€. See if your panel shows up. Plasma 6.0 and above has a issue with panels not always showing or only partially showing after a reboot or suspend.

I just discovered that when I turn off the screen with the keyboard button, I have a black screen with the cursor. The previously described phenomenon occurred after turning off the screen for a long time (an hour+), now a few minutes.

I checked again. Turning off the screen for a while leads to a black screen. It does not display the menu when you click the right button.

Now I will turn off for a longer period of time and see if I can carry out this experiment.

An hour has passed. Black screen. No menu when right mouse button is pressed. The login screen works normally. Previously there was wallpaper, now there is a black screen. I don’t know what has changed.

I executed in the terminal:

killall plasmashell
plasmashell

I turned off the screen with the button on the keyboard and here is the result:

plasmashell
KPackageStructure of KPluginMetaData(pluginId:"org.kde.kupapplet", fileName: "/usr/share/plasma/plasmoids/org.kde.kupapplet/metadata.json") does not match requested format "Plasma/Applet"
kf.plasma.quick: Applet preload policy set to 1
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:195:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
kf.kio.core: Malformed JSON protocol file for protocol: "trash" , number of the ExtraNames fields should match the number of ExtraTypes fields
Toolbox not loading, toolbox package is either invalid or disabled.
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
kf.kio.core: Malformed JSON protocol file for protocol: "trash" , number of the ExtraNames fields should match the number of ExtraTypes fields
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:162:21: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:162:21: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) : 
kameleon supported false
kameleon enabled true
qml: SystemTray ItemLoader: Invalid state, cannot determine source!
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:45: TypeError: Value is null and could not be converted to an object
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
error getting max screen brightness via dbus: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/org/kde/Solid/PowerManagement/Actions/BrightnessControl'")
error getting max keyboard brightness via dbus QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/org/kde/Solid/PowerManagement/Actions/KeyboardBrightnessControl'")
Process "nordvpn status" already running. Pid: 1464607
kf5idletime_wayland: This plugin does not support polling idle time
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
file:///usr/share/plasma/plasmoids/org.kde.plasma.keyboardindicator/contents/ui/main.qml:61:13: Unable to assign [undefined] to bool
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
file:///usr/share/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:76: TypeError: Cannot read property 'pulseProperties' of undefined
org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
file:///usr/share/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:76: TypeError: Cannot read property 'pulseProperties' of undefined
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
file:///usr/share/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:76: TypeError: Cannot read property 'pulseProperties' of undefined
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
xdg_surface#193: error -1: invalid window geometry size (0x0)
The Wayland connection experienced a fatal error: Błąd protokołu

I confirm it reappears after entering edit mode. This has been happening for a while. I’m using Wayland, I don’t know if that could be the culprit?

I wonder if this is related to my issue? Though my panel was ā€œshrinkingā€ instead of disappearing completely, and would go back to normal after entering the editing mode. But maybe it’s related?

Is your panel set to ā€œfit contentā€? The solution was to set it to ā€œcustom sizeā€.

I’m having the same issue. Is there some information I could provide to help track the issue down or have a proper bug report filed?

Hi! It could be related to what @anonnetuser mentioned above, but it might also be worth taking a look at the following bug report, as it sounds like it could be the same situation? 497806 – Turning off "Lock after waking from sleep" and closing lid to sleep causes black desktop and missing panels

Hello there. I’m having the very same issue. For me tt is happening only with the usb-connected external monitor. After waking up from sleep or just unlocking locked desktop. Unplugging and connecting the monitor again fixes the issue instantly. Happy to help resolve the issue, let me know how can I help.

Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.11-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 Ɨ AMD Ryzen 5 PRO 5650U with Radeon Graphics
Memory: 30.2 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 20XLS0M20M
System Version: ThinkPad T14 Gen 2a

I have the same problem.

My laptop has an external monitor connected to it that I use all the time. After the monitor wakes up from sleep mode due to long inactivity, I often see that the panel and desktop are missing, but all the application windows are there and I can switch between them.

At the same time, in the terminal where plasmashell is running, I see new entries

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

To get everything back, I either reconnect the HDMI cable or run plasmashell --replace.

2 Likes

I have the exact same issue for months now.
my laptop is connected to an external monitor via usb-c and the output is set to the external monitor only.
It’s only my hunch but I feel like it could be related to the monitor waking up with a slight delay and isn’t ready when the system thinks it should be.

logs:

qt.qpa.wayland: There are no outputs - creating placeholder screen
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.
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:130: TypeError: Cannot read property 'screenGeometry' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:260: TypeError: Cannot read property 'plasmoid' of undefined
QThreadStorage: Thread 0x55dc8514cde0 exited after QThreadStorage 8 destroyed

System parameters:

Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.14.2-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 Ɨ AMD Ryzen 9 6900HS with Radeon Graphics
Memory: 14.8 GiB of RAM
Graphics Processor 1: AMD Radeon RX 6700S
Graphics Processor 2: AMD Radeon 680M
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G14 GA402RJ_GA402RJ
System Version: 1.0

Please help because this is driving me nuts. every time I restart plasma shell for this, all the entries in the panel are shuffled.

Update: I found a correlation between this issue and the active GPU selection.

I’m on an all-AMD laptop. There are 3 modes for GPU selection (using supergfxctl):

  • Integrated - makes only the built-in monitor work, no external monitor.
  • dGPU (discreet GPU) - when this issue happens.
  • Hybrid - external monitor works but the default GPU is the iGPU. the issue doesn’t happen in this mode (or super rarely)

Hello

I have the same setup as leonbur and user17: External screen connected via USB.

After waking, the panel and desktop background are missing. I solve the issue by disconnecting the external screen; as soon as the laptop screen turns on, everything works fine again. I have not yet tested restarting plasmashell.

I’m also running Wayland.

This issue seems to occur on at least AMD and Intel graphics cards, so it’s probably not a graphics driver issue.

Unfortunately, the bug was closed due to inactivity. Can it be reopened?

Noting similar issue here on FreeBSD/plasma6/X11. After using the monitor toggle button to switch from the HDMI to another monitor connection (on DisplayPort), when I return, the panel has disappeared with the same error as reported

requesting unexisting screen available rect -1

I cannot right click to edit the panel. It returns with a restart of plasmashell. This was not happening on plasma5/FreeBSD 14.2/X11.

Operating System: FreeBSD 14.3
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.3
Kernel Version: 14.3-RELEASE-p5 (64-bit)
Graphics Platform: X11
Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2

I have a similar issue and have not been able to get the panel back. I restarted plasmashell, I restarted the PC, I turned it off completely and turned it on again, every time the panel is gone. I use a desktop PC with two monitors and wayland. The issue occured first day before yesterday and is since then persistent. First the PC started properly after a system upgrade (Manjaro Testing), then it went to sleep (standby mode) and after waking it up the panel (control panel with app menu, activity panel, system tray) was gone. I make heavy use of virtual desktops, but I can’t now as I don’t have a virtual desktop switcher accessible.

In editing mode I see the panel, but I can’t work in editing mode, of course. As soon as the editing mode is off, the panel is gone (or invisible, but a right click on the area where the panel is supposed to be does not reveal a matching context menu, but only one for the regular desktop - I tried several locations for this).

I do not use autohide or any of that stuff, I never had any issues of that sort so far. Hence I guess it is wayland, since I switched to it only a few months ago.

I can confirm this issue and want to add some details that may help narrowing it down.

Observed behavior:

  • Panels (taskbar / window list) are present after login.

  • After several hours of uptime, they suddenly disappear.

  • No logout, no reboot, no crash dialog.

  • plasmashell is still running.

  • Sometimes panels come back on their own, sometimes not.

  • Running plasmashell --replace immediately restores all panels.

Important detail:
This does not happen right after login. It only occurs after the system has been running for some time.

Trigger seems to be monitor power events (DPMS):

  • Monitor turning off due to power saving

  • Monitor waking up

  • Possibly short signal loss on DisplayPort

After such events, the panel containment seems to get lost internally, while plasmashell itself keeps running.

Environment:

  • openSUSE Tumbleweed

  • KDE Plasma (current Tumbleweed version)

  • X11 session (not Wayland)

  • Multi-monitor setup

  • Panels with task manager / system tray

What it is NOT:

  • Not a broken plasma-org.kde.plasma.desktop-appletsrc

  • Not a startup/login issue

  • Not related to logout or shutdown

  • Panels are fine initially and only disappear at runtime

Workaround (not a fix):


plasmashell --replace

restores panels every time.

This looks like a runtime containment loss triggered by output changes (outputsChanged) under X11/DPMS, not a persistent configuration problem.

Hope this helps to pinpoint the cause. Let me know if additional logging or testing would be useful.

Same behavior occurring here (CachyOS). I have nothing new to contribute though, so I’ll keep this message short.

Getting same behavior here as well (also CachyOS).

Doesn’t matter if my monitor goes to sleep or I toggle the KVM switch to go between my desktop and work laptop. Seems anything related to the monitor ā€˜disconnecting’ causes the panel loss.

I have to keep a terminal session open and ready to restart plasma to get things back as it doesn’t come back on it’s own.

systemctl restart --user plasma-plasmashell

Okay so spent some time fiddling with this and did manage to come up with a bit of a stopgap to address this more seamlessly.

worked by combining a udev rule and a script to fire off when there’s a monitor connect/disconnect event.

replace with your username.

This is because the restart command needs to run as your user and not sudo/root

Restart script located in /opt/

#!/bin/sh
sudo systemctl --machine=<usernamehere>@.host --user restart plasma-plasmashell

next in /etc/udev/rules.d create the following as a rule (i did 95-monitor-hotplug.rules)

KERNEL=="card1", SUBSYSTEM=="drm", RUN+="/opt/restart_plasma.sh"

then either reboot or run

sudo udevadm control --reload-rules

now when the monitor disconnects/reconnects it’ll automatically call to restart plasma and get your toolbar/background back.