Created attachment 135656 [details] drkonqi crash file SUMMARY Plasma crashes when starting Thunderbird after resume from hibernate (firefox open, but does not react. (This firefox behavior occurs often after resume from hibernate. It helps to minimize the window, and after that to make it visible again.) STEPS TO REPRODUCE 1. The crash occurs only s0metimes. The firefox behavior nearly always. 2. 3. OBSERVED RESULT crash EXPECTED RESULT both windows (firefox and thunderbird) could become opened SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE TW 84.87.20180228.827b030 (available in About System) KDE Plasma Version: 5.20.5-1.2 KDE Frameworks Version: 5.78.0-2.2 Qt Version: 5.15.2 ADDITIONAL INFORMATION this should be a automatically generated crash info. But it got lost due to mismanagement on my side. So I tried to do it manually.
> #7 QMessageLogger::fatal (this=this@entry=0x7ffd021a5a30, msg=msg@entry=0x7f479f3ce0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 This means that KWin crashed. And when this happens, it takes all apps with it. Can you get the backtrace of the kwin_wayland process so we can figure out why it crashed?
Created attachment 135706 [details] coredumpctl drkonqi
(In reply to Nate Graham from comment #1) > > #7 QMessageLogger::fatal (this=this@entry=0x7ffd021a5a30, msg=msg@entry=0x7f479f3ce0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 > This means that KWin crashed. And when this happens, it takes all apps with > it. Can you get the backtrace of the kwin_wayland process so we can figure > out why it crashed? Does the added attachment give you the right info? Otherwise I need help to get the needed information how to get a backtrace of the kwin_wayland process.
I'm afraid not. Hopefully this is helpful: 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) > I'm afraid not. Hopefully this is helpful: > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl This is exactly what I did. I used this guideline, but there was only this one entry in coredumpctl with the right date. So this here must become closed because lack of data.?.! Or not? I found in /var/lib/systemd/coredump/core.drkonqi.1000.4ce6a59444604238a714217cb1aa6418.28126.1613209920000000.zst this file has 3.8 MB the right date and contains possibly more info, if I could open it, .... I will search for.
Oh so you did! My mistake, sorry. Here's the relevant part: Stack trace of thread 28126: #0 0x00007f47a0484ae5 raise (libc.so.6 + 0x3dae5) #1 0x00007f47a1d6ee70 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x6e70) #2 0x00007f47a0484b70 __restore_rt (libc.so.6 + 0x3db70) #3 0x00007f47a0484ae5 raise (libc.so.6 + 0x3dae5) #4 0x00007f47a046d864 abort (libc.so.6 + 0x26864) #5 0x00007f47a09010e7 qt_message_fatal (libQt5Core.so.5 + 0xbb0e7) #6 0x00007f479f349f79 _ZNK15QtWaylandClient15QWaylandDisplay10checkErrorEv (libQt5WaylandClient.so.5 + 0x70f79) #7 0x00007f479f358e0a _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x7fe0a) #8 0x00007f47a0b53900 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x30d900) #9 0x00007f47a0b7487c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x32e87c) #10 0x00007f47a0b1bcab _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d5cab) #11 0x00007f47a0b23f20 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2ddf20) #12 0x0000557b301b0189 n/a (drkonqi + 0x32189) #13 0x00007f47a046f152 __libc_start_main (libc.so.6 + 0x28152) #14 0x0000557b301b120e _start (drkonqi + 0x3320e)
This log shows plasmashell hit an error. The crash does not give us enough information to act upon this. Can you confirm this still happens in a newer version? If so can you run "WAYLAND_DEBUG=1 plasmashell --replace " before recreating the crash and attach an output.
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: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging 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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!