Debian Bug report logs - #1018003
Plasmashell seems to crash (default wallpaper, no panel, ...) sometimes after waking from standby with Wayland+KDE after connecting a new monitor

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: mYnDstrEAm <[email protected]>

To: "[email protected]" <[email protected]>

Subject: Plasmashell seems to crash (default wallpaper, no panel, ...) sometimes after waking from standby with Wayland+KDE after connecting a new monitor

Date: Tue, 23 Aug 2022 22:59:12 +0000

[Message part 1 (text/plain, inline)]

Package: qtwayland5
Version: 5.15.2-3

Since I connected a new screen to my PC (and this may be unrelated) it sometimes happens that when I wake my PC from standby (with that other screen turned off before and after standby) plasma seems to have crashed:

- The wallpaper is the default one
- Desktop icons are gone
- Sometimes the lockscreen is the default one but sometimes it keeps my lockscreen (when I enter my password at the lockscreen I had to click on the password field or it didn't enter it)
- The panel at the bottom disappeared and when I click the Meta/Windows key nothing happens
- When I move windows like the konsole window, the window becomes invisible until it's at the new place

In system monitor it shows that plasmashell is running (started by systemd) and that startplasma-waylandsession is running (started by systemd->sddm->sddm-helper->startplasma-wayland->kwin_wayland) I'm using Wayland on Debian11(stable)/KDE. When I enter journalctrl -b it only shows very three entries for the day at the bottom like "systemd: Started konsole." and many for the previous day even though I had my computer running for quite a while today. (Note there's also a loss of bash history when using Wayland on Debian and I used to restore it from backups until this became too frequent. Wayland-KDE bugs really should get fixed.) Please let me know if there's anything else I could run to investigate this. I usually try running killall plasmashell and kstart5 plasmashell to get it working again and if that doesn't work I have to end the session and log in again.

My bug report at KDE: https://bugs.kde.org/show_bug.cgi?id=457996 (closed because Debian11 ships a version of KDE that's too old)

SE question with more details: https://unix.stackexchange.com/q/714159/233262

Because I got found this error message in the console:

qt.qpa.wayland: Ignoring unexpected wl_surface.leave received for output with id: {id} screen name: "HDMI-A-1" screen model: "HDMI-A-1-{id}" This is most likely a bug in the compositor.

it seems like this is a duplicate of this bug (see comment 16): https://bugs.kde.org/show_bug.cgi?id=420160#c16

which is a duplicate of this bug: https://bugs.kde.org/show_bug.cgi?id=438839

which apparently got fixed here: https://invent.kde.org/qt/qt/qtwayland/-/merge_requests/27

So the above fix should be applied for Debian11. I hope it really is a duplicate of that bug and that I filed this bug for the right package. Please see the SE question for more details, especially if it turns out not to be a duplicate bug.

[Message part 2 (text/html, inline)]

Message #10 received at [email protected] (full text, mbox, reply):

From: mYnDstrEAm <[email protected]>

To: "[email protected]" <[email protected]>

Subject: comment

Date: Sun, 09 Oct 2022 15:21:23 +0000

May also be related to "Plasmashell problems after changing the HDMI output and KDE does not recognize the new display": https://bugs.kde.org/show_bug.cgi?id=457755

Currently, it doesn't crash anymore but I often need to go to an alt+f3 (any number) terminal and run `loginctl unlock-session {id}` and `logout` to resume the session.

Message #15 received at [email protected] (full text, mbox, reply):

From: mYnDstrEAm <[email protected]>

To: "[email protected]" <[email protected]>

Subject: comment

Date: Sun, 09 Oct 2022 15:26:08 +0000

In the totally outdated issue tracker I can't edit the text: it doesn't crash anymore because as a workaround I have the monitor HDMI cable disconnected except when I use it.



When connecting the HDMI cable, the session ends only when the monitor that the HDMI cable is plugged into is turned off. The wallpaper is changed to a default one nevertheless. Currently, the remaining problem is that when doing one of these things to switch the monitor back again the sessions as well: a) pulling out the HDMI cable b) switching off the active second monitor c) press meta+p and selecting "Unify outputs" (haven't tried the other ones yet).

For the workout to be complete, I only need to find out how to switch back to the formerly active display without the session ending. I'll try a few more things later such as going into standby, then pulling out the HDMI cable, and waking it again. If somebody knows a working workaround, please comment.

Send a report that this bug log contains spam.