Created attachment 174840 [details] Perhaps the Panel should be refreshed if there's an external monitor? My notebook was connected to my 4K (4096x2160p) TV via a PS5's HDMI, I locked the session and went to sleep. Then I logged in and immediately noticed that my panel (Vertical, Left Corner, Dodge Windows, Not Floating) wasn't there. The app launcher spawned at the middle of the screen. Operating System: Arch Linux KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz Memory: 8.1 GB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: LENOVO Product Name: 82MG System Version: IdeaPad Gaming 3 15IHU6
Which means the panel thinks it's running somewhere. Is it reliably reproducible? If you run "plasmashell --replace" whilst in this state does the panel come back?
(In reply to David Edmundson from comment #1) > Which means the panel thinks it's running somewhere. > > Is it reliably reproducible? > If you run "plasmashell --replace" whilst in this state does the panel come > back? That shouldn't be the case because I picked the option that only displays with the external monitor (my TV). Unfortunately I'm no longer with this glitch because I've rebooted and plugged the HDMI after login in.
It happened once again when I was dragging a file, then I plugged my 4K TV via HDMI, then dropped the file. 1- My cursor was stuck on the holding sprite. 2- Then the whole screen went black. 3- Then the screen came back, got the notification that Plasma crashed (That for some reason it's not in the notification history), and the menu was doing that weird thing of appearing in the middle of the screen. Maybe the issue is that Plasma is not rebooting properly after dealing with crashes involving external monitors?
You plugged in a monitor with one hand while, with the other hand, you were in the middle of dragging a file? It sounds like you've figured out a way to make Plasma crash. Can you see if it's reproducible, and if it is, attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
(In reply to Nate Graham from comment #4) > You plugged in a monitor with one hand while, with the other hand, you were > in the middle of dragging a file? > > It sounds like you've figured out a way to make Plasma crash. Can you see if > it's reproducible, and if it is, attach a backtrace of the crash? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl All subsequent attempts of doing the same thing didn't work. However I think the real issue is that KDE Plasma is not handling the recovering process from a crash properly, which I think it's what really happened when I was sleeping. For some reason when recovering, Plasma doesn't spawn the vertical panel, and the app launcher spawns at the center of the screen. Is there a command to force Plasma to crash and recover?
Maybe, but we need to troubleshoot the issue. When this happens, does the desktop wallpaper turn black or change? Or does that remain the same, and only the panel disappears? You can restart plasma with `plasmashell --replace`
(In reply to Nate Graham from comment #6) > Maybe, but we need to troubleshoot the issue. > > When this happens, does the desktop wallpaper turn black or change? Or does > that remain the same, and only the panel disappears? > > You can restart plasma with `plasmashell --replace` It was just like the video attached.
(In reply to Nate Graham from comment #6) > Maybe, but we need to troubleshoot the issue. > > When this happens, does the desktop wallpaper turn black or change? Or does > that remain the same, and only the panel disappears? > > You can restart plasma with `plasmashell --replace` The screen was shut down the first time, and in the second time the screen turned completely black, then the wallpaper reappeared and gave me the notification.
And to be clear, you can't make it happen again?
I've ran the "plasmashell --replace", then after I've closed the Konsole the whole screen and the whole screen is black, there's only the cursor, which I can control at a normal framerate.
Created attachment 175781 [details] It's fully dependent on Konsole being open. This is likely another issue, but plasmashell is fully dependent on the Konsole being open now. $ plasmashell --replace 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": 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" qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) : kde.dataengine.weather: Could not find ion to request source for: "" kde.dataengine.weather: Could not find ion to request source for: "" error getting max keyboard brightness via dbus QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/org/kde/Solid/PowerManagement/Actions/KeyboardBrightnessControl'") qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
That's because you're running Plasma in Konsole, which makes it a child process. If you kill the parent, the child dies too. You can detch Plasma from Konsole by hitting Ctrl+Z, and then typing "bg" and then "disown". But anyway, that's completely unrelated to the original issue here; let's try to stay on target. It sounds like you can't reproduce the original issue anymore, right?
(In reply to Nate Graham from comment #12) > That's because you're running Plasma in Konsole, which makes it a child > process. If you kill the parent, the child dies too. You can detch Plasma > from Konsole by hitting Ctrl+Z, and then typing "bg" and then "disown". But > anyway, that's completely unrelated to the original issue here; let's try to > stay on target. It sounds like you can't reproduce the original issue > anymore, right? Yes, I can't crash the DE again.
Then I'm afraid this isn't actionable, sorry. With no crash backtrace or consistent way to reproduce, it's impossible to debug.