| Summary: | Plasmashell seems to crash sometimes after waking from standby with Wayland+KDE (default wallpaper, no panel, ...) | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | myndstream |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CLOSED DOWNSTREAM | ||
| Severity: | normal | CC: | kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.18.8 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
myndstream
2022-08-17 13:59:54 UTC
killall plasmashell and kstart5 plasmashell doesn't work to get it working again: it looks just like before. Please don't just say Debian has an old version of KDE. *IF* that is the cause of this then please do something about it. Now something similar happened: after resuming from the lockscreen the resolution of my properly detected screen (I checked with systemsettings5) is turned down to the resolution used on the other screen and lockscreen is still visible but in a surrounded by black and mostly covered with konsole messages about deprecated Qt syntax. When I maximize the browser the display issues disappear. I'm not using a proprietary graphics driver or alike. Maybe the screenshot worked so I can attach it > Linux/KDE Plasma: Debian 11 > KDE Plasma Version: 5.20.5 I'm afraid Plasma 5.20.5 is no longer maintained because it's almost impossible to debug issues like this on old versions of Plasma. The fact that Debian chooses to ship unmaintained versions of Plasma to users which are undebuggable by Plasma developers is a decision that frequently causes frustration for both Debian users and KDE developers and Debian's packagers. If you would like to stick with Debian, I would recommend that you upgrade to 5.24 or 5.25 by using Debian unstable, or wait until Debian Stable ships a newer version. Furthermore, if something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports. I don't know if something crashed, maybe there is something specific that I could check if it's running. It could also be two concurrent bugs. I suspect it has something to do with the display settings done after connecting the other display which still shows under Displays even when not turned on. In specific, that I checked "For only this specific display arrangement" rather than "For any display arrangement" may be the cause / may be the needed setting to replicate this bug (the two displays have different resolutions). When waking from standby the login screen only showed my user and "Switch user" when I click on "Switch user" the resolution of the lockscreen is back to how it should be and when I login it's still the screwed up resolution (too small and graphical flickering glitch bugs). The only thing that works is loging out via (killing some specific process or) running qdbus org.kde.Shutdown /Shutdown logout. What could be done when the bottom panel doesn't show and the wallpaper is set to the default one when restarting plasmashell doesn't help with that without having to log out (and close all apps)? Further input and potential help may be found here: https://unix.stackexchange.com/questions/714159/what-causes-plasmashell-to-crash-after-waking-from-standby-wallpaper-set-to-def It is related to the (connection to the) display and sometimes (maybe even always by now as I'd need to test this) turning on the display ends the session. Maybe I'll revisit this once Debian has upgraded to Debian 12 with a newer version of KDE. |