Plasma desktop crashes when monitor turned off

[HuskyDog]

Executive Summary: Raspberry Pi 5, Plasma icon panel and desktop wallpaper disappear when monitor is turned off.

I have a Raspberry Pi 5 with a single monitor connected via HDMI. The display and desktop have worked just fine for many months. I recently updated the Plasma desktop to 6.2.4. Since then I have run into a serious problem. I can login and operate all of the applications successfully until the monitor is switched off. When I switch it back on again, the icon panel at the bottom of the screen has disappeared and so has the wallpaper. Both are now black. The mouse pointer is still visible and any open applications continue to run properly.

Any of the following three actions count as "Switched off": Turning off the monitor via the power button, selecting a different monitor input port, allowing the computer to switch off the monitor to save power due to inactivity.

The effect is 100% reproduceable.

If I am logged out and looking at the SDDM login page, then switching off the monitor has no effect and I can login just fine afterwards.

Restarting the display-manager service re-sets the issue.

I have tried re-booting.

Any suggestions gratefully received!

[asturm]

That's a nasty bug. Firing up krunner you can easily restart plasmashell though without losing your session.

[HuskyDog]

Firing up krunner you can easily restart plasmashell though without losing your session.

I'm not sure that plasmashell is actually crashing. If I run "ps ax | grep plasma" before and after power cycling the monitor I get the same output both times.

[sokhapkin]

Executive Summary: Raspberry Pi 5, Plasma icon panel and desktop wallpaper disappear when monitor is turned off.

I'm getting the same (mis)behavior on Intel laptop after upgrade to Plasma 6.2. Both Wayland and X11.

[Yamakuzure]

Firing up krunner you can easily restart plasmashell though without losing your session.

I'm not sure that plasmashell is actually crashing. If I run "ps ax | grep plasma" before and after power cycling the monitor I get the same output both times.

plasmashell might be still there but stuck.

Code: Select all

plasmashell --replace

in krunner might fix that.

If it doesn't you at least learn what was not the problem.

Code: Select all

kwin_x11 --replace # or kwin_wayland --replace

might also worth a try if plasmashell wasn't the culprit.

[HuskyDog]

OK, running

Code: Select all

plasmashell --replace

seems to get the icon panel and wallpaper back again.

Interestingly, this might be allowing some error messages to appear. I ran the command in Konsole and got the following output:

Code: Select all

plasmashell --replace
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:136: TypeError: Cannot read property 'screenGeometry' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:250: TypeError: Cannot read property 'plasmoid' of undefined
kf.plasma.quick: Applet preload policy set to 1
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
Toolbox not loading, toolbox package is either invalid or disabled.
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) : 
error getting max keyboard brightness via dbus QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/org/kde/Solid/PowerManagement/Actions/KeyboardBrightnessControl'")
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
kameleon supported false
kameleon enabled true

I then switched the monitor off and on again and the following additional lines appeared, as did the bug.

Code: Select all

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

I stopped plasmashell with Ctrl-C and repeated the command and the icon bar was back again. Does this provide anyone with any more clues?

[GuN_jAcK]

I have the same bug on my desktop PC. When it goes into power-saving mode, the monitor turns off. After returning from power-saving mode and the two monitors turn back on, the primary monitor is black (no icons, taskbars, or wallpaper). Despite the crashed desktop, the mouse cursor is visible, and applications can be dragged.

Running plasmashell --replace restores functionality.

I also see the following errors in the console:

Code: Select all

❯ plasmashell --replace
kf.plasma.core: Applet invalid: Cannot find a package for "org.kde.netspeedWidget"
kf.plasma.quick: Applet preload policy set to 1
qml: false
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth":
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
Toolbox not loading, toolbox package is either invalid or disabled.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth":
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
Toolbox not loading, toolbox package is either invalid or disabled.
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/PulseAudio.qml:9:1: module "org.kde.plasma.private.volume" is not installed
kf.plasma.quick: File name empty!
kf.plasma.quick: error when loading applet "org.kde.netspeedWidget" QList("Errore durante il caricamento dell'applet: il pacchetto org.kde.netspeedWidget non esiste.")
error getting max keyboard brightness via dbus QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/org/kde/Solid/PowerManagement/Actions/KeyboardBrightnessControl'")
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
kameleon supported false
kameleon enabled true
kf.kio.gui: Failed to determine systemd version, falling back to extremely legacy forking mode.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

[NeglectedRudderPug]

Oof.

As a potential workaround and mostly if you're lucky. Your monitors own settings (on the monitors own menu, outside of your OS) may have an option to go into standby instead of switching off by button without telling the OS/GPU. The exact name and location of the option may vary from monitor to monitor, but on mine it's under Settings > Power button. There are two options:

- Off
- Standby

Setting to 'Standby' might not inform the OS, where 'Off' usually does. (Since the OS detects the monitor as disconnected.)

Though, I tend to use this option so I can switch my secondary monitors on and off without the desktop being aware. For example while playing games.

It's not a fix, but it could be a useful workaround until you find a fix if the option is available to you.

[GuN_jAcK]

Several Plasma updates have been released, but I keep experiencing the same issue. Is it still happening to you as well?

[kasav]

Several Plasma updates have been released, but I keep experiencing the same issue. Is it still happening to you as well?

My system is up to date but I still have the same problem, defined a keyboard-shortcut to restart plasma-shell as workaround but it's frustrating...

[sokhapkin]

I just noticed that the problem happens on my laptop only when external monitor is connected, is primary and laptop screen is disabled. No problem when laptop screen is primary or outputs are unified.

[sokhapkin]

My workaround: System Settings/Power Management:

Turn off screen - Never
Run command or script - When inactive
When inactive - run after 10 minutes
Command:

Code: Select all

/bin/sh -c "kscreen-doctor output.eDP-1.enable; kscreen-doctor --dpms off; sleep 5; kscreen-doctor output.eDP-1.disable"

If you run X11 session replace " kscreen-doctor --dpms off" with "xset dpms force off".

[Ralphred]

When I switch it back on again, the icon panel at the bottom of the screen has disappeared and so has the wallpaper. Both are now black.

There was a similar symptom when I was switching my "secondary" monitor off/on for gaming, the desktop settings and widget config (including panels) were all stored with some unique ID for that specific monitor or layout, and whatever was responsible for doing the "identification" identified it as a different monitor to the one that it saw at first login - from the point of a Pi5 this may sound odd, but have you tried just booting up using the other HDMI port?

This problem went away for me once I got my xorg.conf to match what xrandr and xorg.0.log were reporting, but I'm old school with my xorg.conf as I want the same monitor layout, resolution and frequencies present in a twm session as a plasma one. Before that I discovered that the "second time the monitor was identified" it was identified the same way subsequently, so for a while I essentially just had "three desktop layouts" stored by kscreen(?):

• Monitor 1
• Monitor 2
• Monitor 2 "after power cycling"

My problem wasn't related to any plasma upgrade, so I've just included as much info as I can remember just in case it helps. I also spotted a new(ish?) feature when a plasma desktop is in "edit mode",the "Panel and Desktop Management" button, and thinking how useful it might have been when I was having issues.

I haven't seen this issue in a while, or been in a position to as I now use udev and xrandr to turn off my secondary monitor when my gamepad connects, but a quick test shows I'm not affected. I'm going to remove my xorg.conf and do another quick test - will report back.

EDIT: Confirmed, I can replicate this bug at will by removing xorg.conf
Once my second monitor is switched back on it's also not shown in the "Panel and Desktop Management" dialog.
Any tests anyone wants run feel free to ask, I can switch to a single gpu set-up too if it matters.

I'm now going to delete sections of xorg.conf and see which one is responsible for "muting" the bug - Once again will report back.
EDIT 2:It's not specifically related to having an entry in xorg.conf, but rather provoked by using "Display Configuration" in systemsettings: By removing my second monitor from xorg.conf the output isn't on in either sddm or plasma. If I switch it on with xrandr and power cycle the monitor everything behaves, if I switch it on by ticking "enable" in "Display Configuration" then power cycle it, it bugs.

[sokhapkin]

It looks like Plasma 6.2.5 update fixed the problem.

[HuskyDog]

It looks like Plasma 6.2.5 update fixed the problem.

Sadly, it doesn't seem to have done so for me!!

[sokhapkin]

It looks like Plasma 6.2.5 update fixed the problem.

Sadly, it doesn't seem to have done so for me!!

Yep. The taskbar not crashes now, but some unneeded KDE daemons like kaccess could still crash. But I can live without.

[freifunk_connewitz]

It looks like Plasma 6.2.5 update fixed the problem.

Sadly, it doesn't seem to have done so for me!!

In my case, too. Plasma 6.2.5, switching monitor off lets plasmashell crash, panel und desktop background disappear.

[Ralphred]

Is it out of order to suggest you gentlemen "turn off" your monitors programmatically instead of literally. Nothing is "crashing", as noted above, if you can't report "symptoms" without objective pragmatism you are just going to become the noise that devs with the ability to fix your issue are going to ignore for the sake of sanity.

Devs are people too, they have husbands and wives, son and daughters - It's nothing more than basic respect to try and understand what the issue is before infringing on their time!

[sokhapkin]

I made a false positive report. The plasmashell still crashes sometime when monitor turns off.

[trics]

This problem went away for me once I got my xorg.conf to match what xrandr and xorg.0.log were reporting

Thanks, I did this and the black desktop went away, I can now turn my monitor off/on at will w/o consequence.
I also checked the "panel and desktop managment" secition in edit mode, and my actual desktop was listed as belonging to "unconnected monitor 2".

[HuskyDog]

This problem went away for me once I got my xorg.conf to match what xrandr and xorg.0.log were reporting

Thanks, I did this and the black desktop went away, I can now turn my monitor off/on at will w/o consequence.
I also checked the "panel and desktop managment" secition in edit mode, and my actual desktop was listed as belonging to "unconnected monitor 2".

Could you possibly explain in rather more detail (step by step would be good) exactly what you did to fix the problem? For a kick-off, I don't seem to have an xorg.conf file, but rather an xorg.conf.d folder. Also, I didn't have xrandr installed, but I've done so now so hopefully that will help.

[Ralphred]

Start by posting the output of xrandr |grep -v "^ " then run X :1 -configure and post the file it produces, should be able to marry the two from that and make a working xorg.conf.

[HuskyDog]

Start by posting the output of xrandr |grep -v "^ " then run X :1 -configure and post the file it produces, should be able to marry the two from that and make a working xorg.conf.

Code: Select all

# xrandr | grep -v "^ "
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
HDMI-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
HDMI-2 disconnected (normal left inverted right x axis y axis)
# X :1 -configure

X.Org X Server 1.21.1.15
X Protocol Version 11, Revision 0
Current Operating System: Linux percypi 6.1.64-v8-16k+ #1702 SMP PREEMPT Wed Nov 29 14:26:42 GMT 2023 aarch64
Kernel command line: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=D8:3A:DD:C3:28:6F vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 root=/dev/nvme0n1p2 rootfstype=ext4 fsck.repair=yes usbhid.mousepoll=0 rootwait cma=256M@256M
 
Current version of pixman: 0.44.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed Feb 12 23:17:43 2025
List of video drivers:
        modesetting
No devices to configure.  Configuration failed.
(EE) Server terminated with error (2). Closing log file.

[Ralphred]

Code: Select all

No devices to configure.

What GPU/kernel driver/xorg driver are you using?

[HuskyDog]

Code: Select all

No devices to configure.

What GPU/kernel driver/xorg driver are you using?

Code: Select all

$ equery u xorg-drivers
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for x11-base/xorg-drivers-21.1-r2:
 U I
 - - input_devices_evdev     : INPUT_DEVICES setting to build driver for evdev input devices
 + + input_devices_libinput  : INPUT_DEVICES setting to build driver for libinput input devices
 - - input_devices_synaptics : INPUT_DEVICES setting to build driver for synaptics input devices
 - - video_cards_amdgpu      : VIDEO_CARDS setting to build driver for AMDGPU video cards
 - - video_cards_freedreno   : VIDEO_CARDS setting to build reverse-engineered driver for Qualcomm Adreno cards
 - - video_cards_radeon      : VIDEO_CARDS setting to build driver for ATI radeon video cards
 - - video_cards_radeonsi    : VIDEO_CARDS setting to build only Southern Islands based chips code for radeon
 - - video_cards_tegra       : VIDEO_CARDS setting to build driver for tegra video cards
 + + video_cards_vc4         : VIDEO_CARDS setting to build driver for vc4 video cards
$ lsmod | grep vc
vc4                   409600  48
drm_display_helper     65536  1 vc4
cec                    81920  1 vc4
drm_dma_helper         65536  1 vc4
drm_kms_helper        229376  4 drm_dma_helper,vc4
snd_soc_core          311296  2 vc4,snd_soc_hdmi_codec
rpivid_hevc            81920  0
v4l2_mem2mem           81920  1 rpivid_hevc
videobuf2_dma_contig    65536  2 pisp_be,rpivid_hevc
drm                   622592  47 gpu_sched,drm_kms_helper,drm_dma_helper,v3d,vc4,drm_shmem_helper,drm_display_helper
videobuf2_v4l2         65536  3 pisp_be,rpivid_hevc,v4l2_mem2mem
videobuf2_common      114688  6 pisp_be,videobuf2_dma_contig,videobuf2_v4l2,rpivid_hevc,v4l2_mem2mem,videobuf2_memops
videodev              311296  5 pisp_be,videobuf2_v4l2,videobuf2_common,rpivid_hevc,v4l2_mem2mem
mc                     98304  7 videodev,snd_usb_audio,pisp_be,videobuf2_v4l2,videobuf2_common,rpivid_hevc,v4l2_mem2mem

Is that the information you are looking for?