SUMMARY Not sure whether relevant, but I tried to unmaximize a Firefox window with `Meta + Pg Up`, afterwards the session crashed. Backtraces from coredumpctl: Core was generated by `/usr/bin/kwin_wayland --xwayland --exit-with-session=/usr/lib/startplasma-wayla'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007ff5f9ea6d30 in ?? () [Current thread is 1 (LWP 18434)] (gdb) bt #0 0x00007ff5f9ea6d30 in ?? () Backtrace stopped: Cannot access memory at address 0x7fff3e6add70 Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f1ca1e41615 in raise () from /usr/lib/libc.so.6 (gdb) bt #0 0x00007f1ca1e41615 in raise () from /usr/lib/libc.so.6 #1 0x00007f1ca1e2a862 in abort () from /usr/lib/libc.so.6 #2 0x00007f1ca223c9ac in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #3 0x00007f1ca282f646 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/libQt5Gui.so.5 #4 0x00007f1ca282fae1 in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/libQt5Gui.so.5 #5 0x00007f1ca2466936 in QCoreApplicationPrivate::init() () from /usr/lib/libQt5Core.so.5 #6 0x00007f1ca2832b20 in QGuiApplicationPrivate::init() () from /usr/lib/libQt5Gui.so.5 #7 0x00007f1ca30fd6aa in QApplicationPrivate::init() () from /usr/lib/libQt5Widgets.so.5 #8 0x000055bd7f37e328 in ?? () #9 0x00007f1ca1e2c152 in __libc_start_main () from /usr/lib/libc.so.6 #10 0x000055bd7f37f1de in ?? () Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f6215b5e615 in raise () from /usr/lib/libc.so.6 [Current thread is 1 (Thread 0x7f6211e9c840 (LWP 18517))] (gdb) bt #0 0x00007f6215b5e615 in raise () at /usr/lib/libc.so.6 #1 0x00007f6215b5e6a0 in <signal handler called> () at /usr/lib/libc.so.6 #2 0x00007f6215b5e615 in raise () at /usr/lib/libc.so.6 #3 0x00007f6215b47862 in abort () at /usr/lib/libc.so.6 #4 0x00007f6215f599ac in () at /usr/lib/libQt5Core.so.5 #5 0x00007f6211a570fa in () at /usr/lib/libQt5WaylandClient.so.5 #6 0x00007f6211a65491 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5 #7 0x00007f62161b4070 in () at /usr/lib/libQt5Core.so.5 #8 0x00007f62161b75a0 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #9 0x00007f62161b7dad in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x00007f6216e15752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x00007f621617ccda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x00007f62161d6556 in () at /usr/lib/libQt5Core.so.5 #13 0x00007f62145f3914 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #14 0x00007f62146477d1 in () at /usr/lib/libglib-2.0.so.0 #15 0x00007f62145f2121 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #16 0x00007f62161d5941 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #17 0x00007f621617b65c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #18 0x00007f6216183af4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #19 0x00005623cae24f99 in () #20 0x00007f6215b49152 in __libc_start_main () at /usr/lib/libc.so.6 #21 0x00005623cae251de in () (plasmashell seems to have crashed twice consecutively)
Cannot reproduce it in git master. Does Firefox run as an X11 client?
I don't know, I guess it uses XWayland by default? I did not change defaults in that regard that I can think of. Also this might be a rare crash, I do not think this can be reproduced easily.
> #5 0x00007f6211a570fa in () at /usr/lib/libQt5WaylandClient.so.5 > #6 0x00007f6211a65491 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5 We will need to know what goes inside () to have any hope of debugging this any further. If you're still experiencing it, can you please install debug symbols and get a new backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks!
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!