SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Kwin arbitrarily crashed fresh from boot/new session while sharing screen in Microsoft Edge for Linux. STEPS TO REPRODUCE 1. Run MS Teams from Edge on Linux 2. Start a meeting and share your screen 3. ??? (the sharing had been going on & off for 1+ hour) OBSERVED RESULT * The whole session crashed, taking down everything with it although it was able to spin a new Kwin_wayland instance EXPECTED RESULT * The desktop should keep functioning nominally. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.13-zen-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 Gio of RAM Graphics Processor: AMD Radeon RX 7900 XTX ADDITIONAL INFORMATION microsoft-edge-stable-bin: 111.0.1661.51-1 Backtrace & Coredump: * https://transfert.free.fr/GBRiycR Phrase is affected version including dots.
#0 0x00007f90785fdce4 _ZN7QRegionC1ERKS_ (libQt5Gui.so.5 + 0x3fdce4) #1 0x000055b0a8169d29 n/a (kwin_wayland + 0x80d29) #2 0x00007f9077ebeb41 n/a (libQt5Core.so.5 + 0x2beb41) #3 0x00007f9077ec109f _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2c109f) #4 0x00007f9077eb1c26 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1c26) #5 0x00007f9077578b5c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x178b5c) #6 0x00007f9077e8e028 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28e028) #7 0x00007f9077ed8583 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2d8583) #8 0x00007f9077ed8a32 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8a32) #9 0x000055b0a821d382 n/a (kwin_wayland + 0x134382) #10 0x00007f9077e8668c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28668c) #11 0x00007f9077e912f9 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2912f9) #12 0x000055b0a81392cb n/a (kwin_wayland + 0x502cb) #13 0x00007f9076d4c850 n/a (libc.so.6 + 0x23850) #14 0x00007f9076d4c90a __libc_start_main (libc.so.6 + 0x2390a) #15 0x000055b0a813aea5 n/a (kwin_wayland + 0x51ea5) I'm afraid the backtrace from the log isn't very helpful. Can you use your coredump to get a better backtrace with debug symbols?
(In reply to Nicolas Fella from comment #1) > #0 0x00007f90785fdce4 _ZN7QRegionC1ERKS_ (libQt5Gui.so.5 + 0x3fdce4) > #1 0x000055b0a8169d29 n/a (kwin_wayland + 0x80d29) > #2 0x00007f9077ebeb41 n/a (libQt5Core.so.5 + 0x2beb41) > #3 0x00007f9077ec109f _ZN6QTimer7timeoutENS_14QPrivateSignalE > (libQt5Core.so.5 + 0x2c109f) > #4 0x00007f9077eb1c26 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + > 0x2b1c26) > #5 0x00007f9077578b5c > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent > (libQt5Widgets.so.5 + 0x178b5c) > #6 0x00007f9077e8e028 > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + > 0x28e028) > #7 0x00007f9077ed8583 _ZN14QTimerInfoList14activateTimersEv > (libQt5Core.so.5 + 0x2d8583) > #8 0x00007f9077ed8a32 > _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEvents > FlagEE (libQt5Core.so.5 + 0x2d8a32) > #9 0x000055b0a821d382 n/a (kwin_wayland + 0x134382) > #10 0x00007f9077e8668c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE > (libQt5Core.so.5 + 0x28668c) > #11 0x00007f9077e912f9 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + > 0x2912f9) > #12 0x000055b0a81392cb n/a (kwin_wayland + 0x502cb) > #13 0x00007f9076d4c850 n/a (libc.so.6 + 0x23850) > #14 0x00007f9076d4c90a __libc_start_main (libc.so.6 + 0x2390a) > #15 0x000055b0a813aea5 n/a (kwin_wayland + 0x51ea5) > > I'm afraid the backtrace from the log isn't very helpful. Can you use your > coredump to get a better backtrace with debug symbols? There's a coredump in the uploaded archive but sure. ``` Reading symbols from /usr/bin/kwin_wayland... (No debugging symbols found in /usr/bin/kwin_wayland) warning: Can't open file /memfd:wayland-shm (deleted) during file-backed mapping note processing warning: Can't open file /memfd:gdk-wayland (deleted) during file-backed mapping note processing warning: Can't open file /memfd:wayland-cursor (deleted) during file-backed mapping note processing warning: Can't open file /memfd:pipewire-memfd:flags=0x0000000f,type=2,size=2100224 (deleted) during file-backed mapping note processing warning: Can't open file /memfd:kwayland-shared (deleted) during file-backed mapping note processing warning: Can't open file /memfd:JITCode:QtQml (deleted) during file-backed mapping note processing warning: Can't open file /memfd:xwayland-shared (deleted) during file-backed mapping note processing warning: Can't open file /memfd:pipewire-memfd:flags=0x0000000f,type=2,size=16384 (deleted) during file-backed mapping note processing warning: Can't open file /memfd:pipewire-memfd:flags=0x0000000f,type=2,size=2312 (deleted) during file-backed mapping note processing warning: Can't open file /dev/shm/wayland.mozilla.ipc.11 (deleted) during file-backed mapping note processing warning: Can't open file /dev/shm/wayland.mozilla.ipc.9 (deleted) during file-backed mapping note processing warning: Can't open file /dev/shm/wayland.mozilla.ipc.8 (deleted) during file-backed mapping note processing warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed mapping note processing warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed mapping note processing warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during file-backed mapping note processing warning: Can't open file /dev/shm/wayland.mozilla.ipc.10 (deleted) during file-backed mapping note processing [New LWP 4931] [New LWP 5043] [New LWP 5054] [New LWP 5044] [New LWP 4969] [New LWP 5053] [New LWP 5047] [New LWP 321848] [New LWP 6266] [New LWP 30964] [New LWP 327522] [New LWP 327524] [New LWP 6257] [New LWP 327531] [New LWP 327533] [New LWP 5045] [New LWP 5042] [New LWP 327526] [New LWP 327527] [New LWP 327532] warning: Section `.reg-xstate/4931' in core file too small. [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-'. Program terminated with signal SIGSEGV, Segmentation fault. warning: Section `.reg-xstate/4931' in core file too small. #0 0x00007f90785fdce4 in QRegion::QRegion(QRegion const&) () from /usr/lib/libQt5Gui.so.5 [Current thread is 1 (Thread 0x7f9072a658c0 (LWP 4931))] (gdb) bt #0 0x00007f90785fdce4 in QRegion::QRegion(QRegion const&) () at /usr/lib/libQt5Gui.so.5 #1 0x000055b0a8169d29 in () #2 0x00007f9077ebeb41 in () at /usr/lib/libQt5Core.so.5 #3 0x00007f9077ec109f in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #4 0x00007f9077eb1c26 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #5 0x00007f9077578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #6 0x00007f9077e8e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #7 0x00007f9077ed8583 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #8 0x00007f9077ed8a32 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #9 0x000055b0a821d382 in () #10 0x00007f9077e8668c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #11 0x00007f9077e912f9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #12 0x000055b0a81392cb in () #13 0x00007f9076d4c850 in () at /usr/lib/libc.so.6 #14 0x00007f9076d4c90a in __libc_start_main () at /usr/lib/libc.so.6 #15 0x000055b0a813aea5 in () ```
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!