Summary: | X11: turning the monitor off/on, causes the panel to disappear | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Ahmad Samir <a.samirh78> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ahpatent, geminiportkey, kustodian, mamoruessu, nate, nortexoid, notmart, plasma-bugs, roman |
Priority: | VHI | Keywords: | regression |
Version: | master | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/commit/9c04d5623687a833ed3b906451ce205b8723cedd | Version Fixed In: | 5.24 |
Sentry Crash Report: |
Description
Ahmad Samir
2022-01-04 14:18:33 UTC
I forgot to say that I have to restart plasmashell to get the panel back. I'm trying to reproduce it with master but without success so far. how is the setup? is it a desktop machine? (ie not laptop) hdmi connection? is the only connection the video card has? what monitor/video card is it? is the desktop actually "working"? ie is it drawing/refreshing and does the right mouse button menu work? the closest i got it to reproduce is plasma crashing but the compositor still painting the last known state of the desktop, so it"appears" only the panel is gone, but plasma isn't running anymore Desktop machine DisplayPort connection Single monitor nvidia GTX770, nouveau kernel module and modesetting driver Monitor is a 4K Samsung The rest of the session is OK, and the plasmashell process is running in the background but no panel; you mean right click on the desktop? (because right clicking in any app is OK). I'll test with a new user account, could be something broken in my current user account (given that no one else is seeing this issue :)). ok, managed to perfectly reproduce, nvm Tested with a new user account, the issue seems to happen only if I use `xset dpms force off` to turn the monitor off (I have a global shortcut that runs that command). A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1339 Git commit 9c04d5623687a833ed3b906451ce205b8723cedd by Marco Martin. Committed on 10/01/2022 at 09:22. Pushed by mart into branch 'master'. Delay setPrimaryOutputName on X11 nativeeventfilter if we do immediately setPrimaryOutputName, the name is still :0.0 because the app didn't have time to react yet (since here we are in the event filter, we are just before that by definition) so the output name can still be wrong. when we go from no outputs to one, at this point the name of the one QScreen instane is still wrong :0.0 which will be renamed right after. M +4 -1 shell/primaryoutputwatcher.cpp https://invent.kde.org/plasma/plasma-workspace/commit/9c04d5623687a833ed3b906451ce205b8723cedd *** Bug 447728 has been marked as a duplicate of this bug. *** *** Bug 446078 has been marked as a duplicate of this bug. *** I just encountered what seems to be this bug but the desktop wallpaper changes to the one that would display on a secondary display. So I think the panel doesn't show because it thinks my primary laptop display is a secondary display instead, on which no panel is configured. Oh whoops, I meant to say that this only happens for me on *wayland*, not X11. I have two machines (one Windows and one Linux) connected to two monitors using displayport connections through a dual-channel KVM switch. All worked perfectly until updating to 5.24, and I now this problem on Plasma/Xorg when either (a) switching monitors off and on again, or (b) switching away from my machine and back again using the KVM. So, if I switch Linux->Win->Linux, the panel will have vanished, and plasmashell is gone and has to be restarted. The Linux machine dual boots OpenSUSE Tumbleweed and Manjaro. Tumbleweed upgraded to 5.24 first and Manjaro about a week later, and the same happened on both OSs upon upgrade. The machine is Intel i7/NVidia GeForce GTX 1660. When I switch away and back, with plasmashell running from konsole, I get: trying to show an empty dialog trying to show an empty dialog trying to show an empty dialog trying to show an empty dialog requesting unexisting screen 2 kde.plasmashell: could not find primary screen "DP-0" requesting unexisting screen 2 kde.plasmashell: could not find primary screen "DP-0" requesting unexisting screen -1 requesting unexisting screen -1 file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:63: TypeError: Cannot read property 'pluginName' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:65: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:66: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:67: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:68: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:69: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:20: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:21: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:22: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:23: TypeError: Cannot read property 'configuration' of null requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:118:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:118:19: QML Loader: Binding loop detected for property "height" requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen 2 requesting unexisting screen -1 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen -1 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:63: TypeError: Cannot read property 'pluginName' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:65: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:66: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:67: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:68: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:69: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:20: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:21: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:22: TypeError: Cannot read property 'configuration' of null file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:23: TypeError: Cannot read property 'configuration' of null org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor" requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 2 requesting unexisting screen 2 trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:118:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:118:19: QML Loader: Binding loop detected for property "height" requesting unexisting screen 0 kde.plasmashell: could not find primary screen ":0.0" requesting unexisting screen 0 kde.plasmashell: could not find primary screen ":0.0" ... [ repeated lots] ... requesting unexisting screen 0 kde.plasmashell: could not find primary screen ":0.0" requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor" requesting unexisting screen 0 [... repeated lots ... ] requesting unexisting screen 0 That particular issue has been fixed in Plasma 5.24.3. Hey! I faced exact same issue too, but on version 5.24.5 using nvidia drivers 510.68.02-1 and xorg-server 21.1.3-6 I'm new here so, please, advice, if there is any additional info I could provide. It's likely a subtly different one; can you file a new bug report? Thanks! |