Created attachment 171203 [details] crash log from journalctl SUMMARY KWin seg fault after running for many days without user input STEPS TO REPRODUCE 1. Start Kwin with tty (`/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland`) 2. wait many days probably over a week 3. hope crash is reproducible OBSERVED RESULT Seg fault is logged in journalctl, but kwin restarts since plasmashell did not crash EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.6-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-12400 Memory: 62.5 GiB of RAM Graphics Processor: NV176 [AKA RTX 3060 12G running Nouveau driver] ADDITIONAL INFORMATION Sorry in advance about the missing debug symbols in the stack trace. However, there does seem to be the C++ mangled names for Qt, and that might be enough to go on when using a demangler like https://demangler.com/. There I was able to get the source of the seg fault being in `QCoreApplication::notifyInternal2(QObject*, QEvent*)` where the core application is KWin.
Comment on attachment 171203 [details] crash log from journalctl >... >~1 of this exact log per second >Jun 30 10:53:00 supe chromium[123494]: [123494:123494:0630/105300.684863:ERROR:page_load_metrics_update_dispatcher.cc(179)] Invalid first_paint 3.215 s for first_image_paint 2.246 s >... >Jun 30 10:53:06 supe kernel: traps: kwin_wayland[112862] general protection fault ip:73f0aa344dac sp:7fff34502bd0 error:0 in libQt6Core.so.6.7.1[73f0aa28a000+394000] >Jun 30 10:53:06 supe systemd-coredump[3021022]: Process 112862 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing... >Jun 30 10:53:06 supe systemd[1]: Started Process Core Dump (PID 3021022/UID 0). >Jun 30 10:53:06 supe systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. >Jun 30 10:53:06 supe chromium[123494]: [123494:123494:0630/105306.161261:ERROR:page_load_metrics_update_dispatcher.cc(179)] Invalid first_paint 3.215 s for first_image_paint 2.246 s >Jun 30 10:53:07 supe systemd-coredump[3021023]: Process 112862 (kwin_wayland) of user 1000 dumped core. > > Stack trace of thread 112862: > #0 0x000073f0aa344dac _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144dac) > #1 0x000073f0aa4c3c38 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x2c3c38) > #2 0x000073f0aa4c6308 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2c6308) > #3 0x000073f0aadf95b3 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x5f95b3) > #4 0x000073f0aa34f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e) > #5 0x000073f0aa34945d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x14945d) > #6 0x0000650de9970069 n/a (kwin_wayland + 0x3c069) > #7 0x000073f0a9c39c88 n/a (libc.so.6 + 0x25c88) > #8 0x000073f0a9c39d4c __libc_start_main (libc.so.6 + 0x25d4c) > #9 0x0000650de9975fc5 n/a (kwin_wayland + 0x41fc5) > > Stack trace of thread 112899: > #0 0x000073f0a9ca34e9 n/a (libc.so.6 + 0x8f4e9) > #1 0x000073f0a9ca5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9) > #2 0x000073f0a069d47e n/a (nouveau_dri.so + 0x9d47e) > #3 0x000073f0a067b22c n/a (nouveau_dri.so + 0x7b22c) > #4 0x000073f0a069d3ad n/a (nouveau_dri.so + 0x9d3ad) > #5 0x000073f0a9ca6ded n/a (libc.so.6 + 0x92ded) > #6 0x000073f0a9d2a0dc n/a (libc.so.6 + 0x1160dc) > > Stack trace of thread 112916: > #0 0x000073f0a9d1c39d __poll (libc.so.6 + 0x10839d) > #1 0x000073f0a8e8a8fd n/a (libglib-2.0.so.0 + 0xbe8fd) > #2 0x000073f0a8e27f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) > #3 0x000073f0aa5a28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd) > #4 0x000073f0aa34f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e) > #5 0x000073f0aa440e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00) > #6 0x000073f0aa4c96e7 n/a (libQt6Core.so.6 + 0x2c96e7) > #7 0x000073f0a9ca6ded n/a (libc.so.6 + 0x92ded) > #8 0x000073f0a9d2a0dc n/a (libc.so.6 + 0x1160dc) > > Stack trace of thread 112917: > #0 0x000073f0a9d2a4e2 epoll_wait (libc.so.6 + 0x1164e2) > #1 0x000073f0a009d197 n/a (libspa-support.so + 0x15197) > #2 0x000073f0a008ea21 n/a (libspa-support.so + 0x6a21) > #3 0x000073f093d76103 n/a (libpipewire-0.3.so.0 + 0x1c103) > #4 0x000073f0a9ca6ded n/a (libc.so.6 + 0x92ded) > #5 0x000073f0a9d2a0dc n/a (libc.so.6 + 0x1160dc) > > Stack trace of thread 112900: > #0 0x000073f0a9d1c39d __poll (libc.so.6 + 0x10839d) > #1 0x000073f0a8e8a8fd n/a (libglib-2.0.so.0 + 0xbe8fd) > #2 0x000073f0a8e27f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) > #3 0x000073f0aa5a28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd) > #4 0x000073f0aa34f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e) > #5 0x000073f0aa440e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00) > #6 0x000073f0aa4c96e7 n/a (libQt6Core.so.6 + 0x2c96e7) > #7 0x000073f0a9ca6ded n/a (libc.so.6 + 0x92ded) > #8 0x000073f0a9d2a0dc n/a (libc.so.6 + 0x1160dc) > > Stack trace of thread 112892: > #0 0x000073f0a9d1c39d __poll (libc.so.6 + 0x10839d) > #1 0x000073f0a8e8a8fd n/a (libglib-2.0.so.0 + 0xbe8fd) > #2 0x000073f0a8e27f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) > #3 0x000073f0aa5a28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd) > #4 0x000073f0aa34f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e) > #5 0x000073f0aa43a4e0 _ZN7QThread4execEv (libQt6Core.so.6 + 0x23a4e0) > #6 0x000073f0ab223dfe n/a (libQt6DBus.so.6 + 0x2ddfe) > #7 0x000073f0aa4c96e7 n/a (libQt6Core.so.6 + 0x2c96e7) > #8 0x000073f0a9ca6ded n/a (libc.so.6 + 0x92ded) > #9 0x000073f0a9d2a0dc n/a (libc.so.6 + 0x1160dc) > ELF object binary architecture: AMD x86-64 >Jun 30 10:53:07 supe systemd[1]: systemd-coredump@11-3021022-0.service: Deactivated successfully. >... >--Logs of all apps crashing since Wayland compositor died-- >... >Jun 30 10:53:07 supe kwin_wayland[3021102]: No backend specified, automatically choosing drm >Jun 30 10:53:07 supe ksmserver[112993]: The X11 connection broke (error 1). Did the X11 server die? >Jun 30 10:53:07 supe systemd[810]: plasma-xdg-desktop-portal-kde.service: Main process exited, code=exited, status=255/EXCEPTION >Jun 30 10:53:07 supe systemd[810]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'. >Jun 30 10:53:07 supe drkonqi-coredump-processor[3021024]: "/usr/bin/kwin_wayland" 112862 "/var/lib/systemd/coredump/core.kwin_wayland.1000.dd64c44f914f4131b4949fde2b289097.112862.1719759186000000.zst" >Jun 30 10:53:07 supe systemd[810]: Started Launch DrKonqi for a systemd-coredump crash (PID 3021024/UID 0). >Jun 30 10:53:07 supe drkonqi-coredump-launcher[3021111]: Unable to find file for pid 112862 expected at "kcrash-metadata/kwin_wayland.dd64c44f914f4131b4949fde2b289097.112862.ini" >Jun 30 10:53:07 supe systemd[1]: drkonqi-coredump-processor@11-3021022-0.service: Deactivated successfully. >Jun 30 10:53:07 supe systemd[810]: plasma-plasmashell.service: Main process exited, code=exited, status=255/EXCEPTION >Jun 30 10:53:07 supe systemd[810]: plasma-plasmashell.service: Failed with result 'exit-code'. >Jun 30 10:53:07 supe systemd[810]: plasma-krunner.service: Main process exited, code=exited, status=255/EXCEPTION >Jun 30 10:53:07 supe systemd[810]: plasma-krunner.service: Failed with result 'exit-code'.
You can follow the instructions on https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to make the stack trace useful for us. Can you do that? Thanks!
(In reply to Nate Graham from comment #2) > You can follow the instructions on > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > to make the stack trace useful for us. Can you do that? Thanks! I can't unfortunately. The debug symbols version has already updated KWin v6.1.1 on Arch Linux, so it's not compatible with my coredump. I can wait until the crash happens again now that I have the debug symbols and KDE version match.
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. Closing as RESOLVED WORKSFORME.