Application: kwin_x11 (5.27.11) Qt Version: 5.15.14 Frameworks Version: 5.116.0 Operating System: Linux 6.10.3 x86_64 Windowing System: X11 Distribution: Slackware 15.0 x86_64 (post 15.0 -current) DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Just going about, doing nothing of interest, switch desktops (7 open with fullscreen KPatience, Shisen-Sho, K3b, Kate, Dolphin), open applications, routine desktop navigation; nothing repeatable. AMD Ryzen 7 1700 , 16gb ram, Radeon RX 550/550 Series graphics. KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.116.0 Qt Version: 5.15.14 Kernel Version: 6.10.3 (64-bit) Graphics Platform: X11 Product Name: HP Pavilion Power Desktop 580-1xx Note: Filezilla sometimes crashes after a few minutes after remote connection, after restart runs fine for over an hour of remote editing in place. I suspect the Radeon kernel module, as this nonsense began within the past couple of months after years of no kabooms. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x0000000000000051 in ??? () #5 0x0000000000472070 in ??? () #6 0x000000000047295a in ??? () #7 0x0000000000473fc3 in ??? () #8 0x00007fabc8b97cfb in ??? () at /usr/lib64/libQt5DBus.so.5 #9 0x00007fabc8b9bc96 in ??? () at /usr/lib64/libQt5DBus.so.5 #10 0x00007fabc8b9c250 in ??? () at /usr/lib64/libQt5DBus.so.5 #11 0x00007fabc8b9e608 in ??? () at /usr/lib64/libQt5DBus.so.5 #12 0x00007fabca0ee5f6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x00007fabc8d7006e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x00007fabca0c3868 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x00007fabca0c6951 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #16 0x00007fabca11ac13 in ??? () at /usr/lib64/libQt5Core.so.5 #17 0x00007fabc57143dd in ??? () at /usr/lib64/libglib-2.0.so.0 #18 0x00007fabc5717327 in ??? () at /usr/lib64/libglib-2.0.so.0 #19 0x00007fabc571790c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #20 0x00007fabca11a339 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #21 0x00007fabca0c2412 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #22 0x00007fabca0ca400 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #23 0x000000000043b3a0 in ??? () #24 0x00007fabc8429d07 in __libc_start_call_main () at /lib64/libc.so.6 #25 0x00007fabc8429dc5 in __libc_start_main_impl () at /lib64/libc.so.6 #26 0x000000000043c801 in ??? () [Inferior 1 (process 2634) detached] Reported using DrKonqi
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong. Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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.