View previous topic :: View next topic |
Author |
Message |
HuskyDog Tux's lil' helper
Joined: 20 Feb 2003 Posts: 81 Location: Wiltshire, UK
|
Posted: Wed Dec 11, 2024 10:14 pm Post subject: Plasma desktop crashes when monitor turned off |
|
|
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! |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 9333
|
Posted: Wed Dec 11, 2024 11:32 pm Post subject: |
|
|
That's a nasty bug. Firing up krunner you can easily restart plasmashell though without losing your session. |
|
Back to top |
|
|
HuskyDog Tux's lil' helper
Joined: 20 Feb 2003 Posts: 81 Location: Wiltshire, UK
|
Posted: Thu Dec 12, 2024 12:29 am Post subject: |
|
|
Quote: | 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. |
|
Back to top |
|
|
sokhapkin n00b
Joined: 13 Jan 2005 Posts: 55 Location: N Ft Myers, FL
|
Posted: Fri Dec 13, 2024 5:10 pm Post subject: Re: Plasma desktop crashes when monitor turned off |
|
|
HuskyDog wrote: | 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. |
|
Back to top |
|
|
Yamakuzure Advocate
Joined: 21 Jun 2006 Posts: 2305 Location: Adendorf, Germany
|
Posted: Sat Dec 14, 2024 9:05 am Post subject: |
|
|
HuskyDog wrote: | Quote: | 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: | plasmashell --replace | in krunner might fix that.
If it doesn't you at least learn what was not the problem.
Code: | kwin_x11 --replace # or kwin_wayland --replace | might also worth a try if plasmashell wasn't the culprit. _________________ Edited 220,176 times by Yamakuzure |
|
Back to top |
|
|
HuskyDog Tux's lil' helper
Joined: 20 Feb 2003 Posts: 81 Location: Wiltshire, UK
|
Posted: Sat Dec 14, 2024 9:45 pm Post subject: |
|
|
OK, running Code: | 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: | 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: | 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? |
|
Back to top |
|
|
GuN_jAcK l33t
Joined: 23 Mar 2005 Posts: 834 Location: Prague, Czech Republic
|
Posted: Tue Dec 17, 2024 7:04 am Post subject: |
|
|
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: |
❯ 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)
|
_________________ Rispondi in maniera intelligente anche a chi ti tratta stupidamente. |
|
Back to top |
|
|
NeglectedRudderPug n00b
Joined: 04 Oct 2023 Posts: 38
|
Posted: Thu Dec 19, 2024 12:40 am Post subject: |
|
|
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. |
|
Back to top |
|
|
GuN_jAcK l33t
Joined: 23 Mar 2005 Posts: 834 Location: Prague, Czech Republic
|
Posted: Mon Jan 13, 2025 11:06 am Post subject: |
|
|
Several Plasma updates have been released, but I keep experiencing the same issue. Is it still happening to you as well? _________________ Rispondi in maniera intelligente anche a chi ti tratta stupidamente. |
|
Back to top |
|
|
kasav n00b
Joined: 09 Dec 2014 Posts: 5
|
Posted: Sat Jan 18, 2025 2:47 pm Post subject: |
|
|
GuN_jAcK wrote: | 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... |
|
Back to top |
|
|
sokhapkin n00b
Joined: 13 Jan 2005 Posts: 55 Location: N Ft Myers, FL
|
Posted: Sun Jan 19, 2025 11:57 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
sokhapkin n00b
Joined: 13 Jan 2005 Posts: 55 Location: N Ft Myers, FL
|
Posted: Mon Jan 20, 2025 6:07 pm Post subject: |
|
|
My workaround: System Settings/Power Management:
Turn off screen - Never
Run command or script - When inactive
When inactive - run after 10 minutes
Command: Code: |
/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". |
|
Back to top |
|
|
Ralphred l33t
Joined: 31 Dec 2013 Posts: 705
|
Posted: Mon Jan 20, 2025 6:11 pm Post subject: |
|
|
Quote: | 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. |
|
Back to top |
|
|
|