SUMMARY Shortly after login plasmashell crashes. Trigger may be opening the application launcher possibly. Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139932488866240) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139932488866240) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139932488866240, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x00007f449681f476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f44968057f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x00007f4496cc1ba3 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914 #10 QMessageLogger::fatal (this=this@entry=0x7ffdc2f8f240, msg=msg@entry=0x7f4494f2b078 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #11 0x00007f4494e8ee45 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at ./src/client/qwaylanddisplay.cpp:209 #12 QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at ./src/client/qwaylanddisplay.cpp:204 #13 0x00007f4494e9f11a in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x561606b967b0) at ./src/client/qwaylanddisplay.cpp:222 #14 0x00007f4496f227b8 in doActivate<false> (sender=0x561606bb6140, signal_index=4, argv=0x7ffdc2f8f340) at kernel/qobject.cpp:3898 #15 0x00007f4496f1ba97 in QMetaObject::activate (sender=sender@entry=0x561606bb6140, m=m@entry=0x7f4497188840 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #16 0x00007f4496ee7857 in QAbstractEventDispatcher::awake (this=this@entry=0x561606bb6140) at .moc/moc_qabstracteventdispatcher.cpp:149 #17 0x00007f4496f4413b in QEventDispatcherGlib::processEvents (this=0x561606bb6140, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #18 0x00007f4496ee974b in QEventLoop::exec (this=this@entry=0x7ffdc2f8f460, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x00007f4496ef1ce4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #20 0x0000561606564dce in main (argc=<optimized out>, argv=<optimized out>) at ./shell/main.cpp:238 [Inferior 1 (process 2043) detached] STEPS TO REPRODUCE 1. Login to user 2. Attempt to open application launcher OBSERVED RESULT Plasmashell crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3
> The Wayland connection broke. Did the Wayland compositor die The crash log only tells us that KWin crashed; sadly it's a known and unavoidable issue that when kwin_wayland crashes, all apps crash too (see https://bugreports.qt.io/browse/QTBUG-85631). The app crash logs are not useful; all they do is tell us that KWin crashed. But we need to know why KWin crashed. For that, we need a backtrace of the KWin crash itself. You may be able to retrieve it with `coredumpctl`. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Ah, I see. I just tried now and I get "No coredumps found.", so I guess I'll have to wait until it crashes again.
Got another crash shortly after login, here's the coredumpctl output: https://pastebin.com/TPJSukRu I would paste it in the comment here for searchability but the log is over the ~65k character limit.
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!
Log files posted.
That log shows us a plasmashell crash. It's expected that plasmashell crashes when kwin crashes; we need a log of the kwin_wayland crash.
And how do I get that? I just pasted a backtrace following the instructions in the link into the pastebin in Comment 3.
Whatever you did to get the backtrace of the plasmashell crash, do it again, but for the kwin_wayland crash. `coredumpctl` can show them to you.
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!