Bug 440094

Summary: Intermittent Kwin crash on wayland
Product: [Plasma] kwin Reporter: harry
Component: wayland-genericAssignee: harry
Severity: crash CC: aleixpol, jodr666, nate
Priority: NOR    
Version: 5.22.3   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Kwin core dump
journalctl logs
kwin_wayland backtrace dump with debuging symbols

Description harry 2021-07-21 03:14:34 UTC
Created attachment 140222 [details]
Kwin core dump

Hi there I have a reoccurring bug where kwin will crash on wayland. This crash then causes all x11 programs to crash (firefox running in X11 mode, spotify) and also all of plasma (producing lots of "Dr Konqi" windows). Sometimes its possible to reopen the application after, other times a full restart happens.

It happens fairly regularly (once a day or so), but doesn't seem to be caused by any specific action and I can't see any logs that look suspicious. 

1. Run kwin in native wayland mode
2. Wait for it to crash


Kwin crashes, as does firefox, spotify and all of plasma. Other applications seem to survive (e.g. system monitor). 


It shouldn't crash

Operating System: Kubuntu 21.04
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-22-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

Comment 1 harry 2021-07-21 03:15:33 UTC
Created attachment 140223 [details]
journalctl logs

attached journalctl logs around time of failure
Comment 2 harry 2021-07-21 03:16:21 UTC
It also looks similar to https://bugs.kde.org/show_bug.cgi?id=437709 but has a different stack trace
Comment 3 Tony 2021-07-27 18:27:17 UTC
(In reply to harry from comment #1)
> Created attachment 140223 [details]
> journalctl logs
> attached journalctl logs around time of failure

The crash logged here is for plasmashell
Comment 4 Tony 2021-07-27 18:27:47 UTC
The core dump is missing debug symbols.
Comment 5 Tony 2021-07-27 18:29:24 UTC
Comment 6 Bug Janitor Service 2021-08-11 04:36:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 harry 2021-08-13 02:27:58 UTC
Created attachment 140678 [details]
kwin_wayland backtrace dump with debuging symbols

Hi, here's the crash with the right debuging symbols. Sorry it took a while for me to work out which ones I need to install. (Can also upload the coredump if needed but its 300MB)

All the other things that crash at the same time have this in their stacktrace if that helps:
QMessageLogger::fatal (this=this@entry=0x7fffac3b1980, msg=msg@entry=0x7fcbb2f9d0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
Comment 8 Aleix Pol 2021-09-21 17:18:13 UTC
In this case it would make sense to have the debugging symbols from kwin. You only have them on Qt which is nice but doesn't tell us much about where it crashes.

On the journalctl logs we see other processes crashing with kwin.

Can you still reproduce this issue? if so could you check with kwin-wayland-dbgsym installed?

Also I know it's a bit more troublesome but testing against the beta would be very helpful to us as it might be something that already has been fixed for the next release.
Comment 9 Aleix Pol 2021-09-21 17:22:45 UTC

*** This bug has been marked as a duplicate of bug 438097 ***