Application: kwin_x11 (5.27.11) Qt Version: 5.15.14 Frameworks Version: 5.116.0 Operating System: Linux 6.9.12 x86_64 Windowing System: X11 Distribution: Slackware 15.0 x86_64 (post 15.0 -current) DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Used Dolphin to create a zip archive of a 10gb directory to upload for a friend using Windows who can't use a xz-compressed tarball. Click OK, screen went blank then came back, Dolphin created the 5gb zip archive as advertised, up popped this Bug Report. This happened quite often, particulary when using Filezilla to navigate a remote KDE directory tree, until I set folding@home to run only when idle. Those crashes ceased. This is new. I tried to upgrade Plasma using kdesrc-build so K3b could create 50gb Bluray discs, but the build halted on error; troubleshooting that is on to-do list. One of these days I'll get around to looking for a memory leak with valgrind, soon as I can build KWin with debug symbols. Running Slackware-current, kernel 6.9.12, Ryzen 7 1700, X11, Q5.15.14, Frameworks 5.116.14 , Plasma 5.27.11. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x000000000047206a in ??? () #5 0x000000000047295a in ??? () #6 0x0000000000473fc3 in ??? () #7 0x00007fcc83f2bcfb in ??? () at /usr/lib64/libQt5DBus.so.5 #8 0x00007fcc83f2fc96 in ??? () at /usr/lib64/libQt5DBus.so.5 #9 0x00007fcc83f30250 in ??? () at /usr/lib64/libQt5DBus.so.5 #10 0x00007fcc83f32608 in ??? () at /usr/lib64/libQt5DBus.so.5 #11 0x00007fcc854ee5f6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x00007fcc8417006e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x00007fcc854c3868 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #14 0x00007fcc854c6951 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #15 0x00007fcc8551ac13 in ??? () at /usr/lib64/libQt5Core.so.5 #16 0x00007fcc80b143dd in ??? () at /usr/lib64/libglib-2.0.so.0 #17 0x00007fcc80b17327 in ??? () at /usr/lib64/libglib-2.0.so.0 #18 0x00007fcc80b1790c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x00007fcc8551a339 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #20 0x00007fcc854c2412 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #21 0x00007fcc854ca400 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #22 0x000000000043b3a0 in ??? () #23 0x00007fcc83829d07 in __libc_start_call_main () at /lib64/libc.so.6 #24 0x00007fcc83829dc5 in __libc_start_main_impl () at /lib64/libc.so.6 #25 0x000000000043c801 in ??? () [Inferior 1 (process 15275) 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! Though I suspect this is bug 475030 from the little information that is there.
🐛🧹 ⚠️ 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.