*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Crash of Copying. STEPS TO REPRODUCE 1. Copy large file from external USB SSD to external USB SSD 2. Open another Dolphin window to look at checksum and calculate hash or Use thunderbird to change default mail sound with dolphin dialog 3. OBSERVED RESULT Copying crashes and doesn't complete EXPECTED RESULT Files copied successfully SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Solus 4.7 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION
Thanks for reporting this crash. As it says in the template, we need a backtrace so we can investigate what's happening See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
(In reply to TraceyC from comment #1) > Thanks for reporting this crash. As it says in the template, we need a > backtrace so we can investigate what's happening > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports I dont know how to create a backtrace and the linked page doesn't explain.
Oh yes it does LOL Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'avahi-autoipd', 'systemd-journal', 'wheel' can see all messages. Pass -q to turn off this notice. PID: 95382 (dolphin) UID: 1000 (tim) GID: 1000 (tim) Signal: 11 (SEGV) Timestamp: Mon 2025-03-31 18:37:54 BST (1 day 1h ago) Command Line: /usr/bin/dolphin /run/media/tim/6EC3630B5CD252D3 Executable: /usr/bin/dolphin Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.dolphin@999dd0214804477d9da4fc973a8032d7.service Unit: user@1000.service User Unit: app-org.kde.dolphin@999dd0214804477d9da4fc973a8032d7.service Slice: user-1000.slice Owner UID: 1000 (tim) Boot ID: 78b16d142f0c42caae4777f9862a7ce3 Machine ID: 20929a07718146d2bfcc6e544e17dfcc Hostname: tim-solus Storage: /var/lib/systemd/coredump/core.dolphin.1000.78b16d142f0c42caae4777f9862a7ce3.95382.1743442674000000.zst (present) Size on Disk: 8.6M Message: Process 95382 (dolphin) of user 1000 dumped core. Stack trace of thread 95382: #0 0x00007f3e3a4aad4b pthread_kill (libc.so.6 + 0x9fd4b) #1 0x00007f3e3a44fb56 raise (libc.so.6 + 0x44b56) #2 0x00007f3e3cd9eeb4 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7eb4) #3 0x00007f3e3a44fc80 n/a (libc.so.6 + 0x44c80) #4 0x00007f3e3c02bebc _ZNK11QMainWindow7menuBarEv (libQt6Widgets.so.6 + 0x42bebc) #5 0x00007f3e305ecfed n/a (breeze6.so + 0x76fed) #6 0x00007f3e3ad388f4 n/a (libQt6Core.so.6 + 0x3388f4) #7 0x00007f3e3c8bfba5 n/a (libKF6ConfigCore.so.6 + 0x6bba5) #8 0x00007f3e3c8bfee0 _ZN14KConfigWatcher11qt_metacallEN11QMetaObject4CallEiPPv (libKF6ConfigCore.so.6 + 0x6bee0) #9 0x00007f3e3bb96f6e n/a (libQt6DBus.so.6 + 0x56f6e) #10 0x00007f3e3ad2e2aa _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x32e2aa) #11 0x00007f3e3be4d1a0 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x24d1a0) #12 0x00007f3e3be4e3e3 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x24e3e3) #13 0x00007f3e3acd74ff _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x2d74ff) #14 0x00007f3e3acd8813 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x2d8813) #15 0x00007f3e3afe34db n/a (libQt6Core.so.6 + 0x5e34db) #16 0x00007f3e379de288 n/a (libglib-2.0.so.0 + 0x76288) #17 0x00007f3e37a6a01a n/a (libglib-2.0.so.0 + 0x10201a) #18 0x00007f3e379dca74 g_main_context_iteration (libglib-2.0.so.0 + 0x74a74) #19 0x00007f3e3afe2db6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5e2db6) #20 0x00007f3e3ace2926 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2e2926) #21 0x00007f3e3acd7d4e _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x2d7d4e) #22 0x0000559432037105 n/a (dolphin + 0x79105) #23 0x00007f3e3a4362ec n/a (libc.so.6 + 0x2b2ec) #24 0x00007f3e3a4363a9 __libc_start_main (libc.so.6 + 0x2b3a9) #25 0x0000559432033795 n/a (dolphin + 0x75795) Stack trace of thread 95386: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a517883 ppoll (libc.so.6 + 0x10c883) #3 0x00007f3e37a69fcd n/a (libglib-2.0.so.0 + 0x101fcd) #4 0x00007f3e379dca74 g_main_context_iteration (libglib-2.0.so.0 + 0x74a74) #5 0x00007f3e3afe2db6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5e2db6) #6 0x00007f3e3ace2926 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2e2926) #7 0x00007f3e3ae05dfc _ZN7QThread4execEv (libQt6Core.so.6 + 0x405dfc) #8 0x00007f3e3bb9007e n/a (libQt6DBus.so.6 + 0x5007e) #9 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #10 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #11 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95387: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a5173fa __poll (libc.so.6 + 0x10c3fa) #3 0x00007f3e39198f69 n/a (libQt6WaylandClient.so.6 + 0x90f69) #4 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #5 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #6 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95388: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a5173fa __poll (libc.so.6 + 0x10c3fa) #3 0x00007f3e39198f69 n/a (libQt6WaylandClient.so.6 + 0x90f69) #4 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #5 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #6 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95420: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a517883 ppoll (libc.so.6 + 0x10c883) #3 0x00007f3e37a69fcd n/a (libglib-2.0.so.0 + 0x101fcd) #4 0x00007f3e379e38a6 n/a (libglib-2.0.so.0 + 0x7b8a6) #5 0x00007f3e37a224b1 n/a (libglib-2.0.so.0 + 0xba4b1) #6 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #7 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 96049: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a51807a __write (libc.so.6 + 0x10d07a) #3 0x00007f3e3ac8a9bf n/a (libQt6Core.so.6 + 0x28a9bf) #4 0x00007f3e3ac7d8e4 _ZN11QFileDevice9writeDataEPKcx (libQt6Core.so.6 + 0x27d8e4) #5 0x00007f3e3ac8f743 _ZN9QIODevice5writeEPKcx (libQt6Core.so.6 + 0x28f743) #6 0x00007f3e1df25ccb n/a (kio_file.so + 0x12ccb) #7 0x00007f3e1df26e72 n/a (kio_file.so + 0x13e72) #8 0x00007f3e3ce6ef06 n/a (libKF6KIOCore.so.6 + 0xc9f06) #9 0x00007f3e3ce680d1 n/a (libKF6KIOCore.so.6 + 0xc30d1) #10 0x00007f3e3ce61c34 n/a (libKF6KIOCore.so.6 + 0xbcc34) #11 0x00007f3e3cefed5f n/a (libKF6KIOCore.so.6 + 0x159d5f) #12 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #13 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #14 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95393: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a517883 ppoll (libc.so.6 + 0x10c883) #3 0x00007f3e37a69fcd n/a (libglib-2.0.so.0 + 0x101fcd) #4 0x00007f3e379dca74 g_main_context_iteration (libglib-2.0.so.0 + 0x74a74) #5 0x00007f3e3afe2db6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5e2db6) #6 0x00007f3e3ace2926 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2e2926) #7 0x00007f3e3ae05dfc _ZN7QThread4execEv (libQt6Core.so.6 + 0x405dfc) #8 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #9 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #10 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95419: #0 0x00007f3e3a5215bd syscall (libc.so.6 + 0x1165bd) #1 0x00007f3e37a28c3a n/a (libglib-2.0.so.0 + 0xc0c3a) #2 0x00007f3e37a224b1 n/a (libglib-2.0.so.0 + 0xba4b1) #3 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #4 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95421: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a517883 ppoll (libc.so.6 + 0x10c883) #3 0x00007f3e37a69fcd n/a (libglib-2.0.so.0 + 0x101fcd) #4 0x00007f3e379e1ecf g_main_loop_run (libglib-2.0.so.0 + 0x79ecf) #5 0x00007f3e33978ec0 n/a (libgio-2.0.so.0 + 0x178ec0) #6 0x00007f3e37a224b1 n/a (libglib-2.0.so.0 + 0xba4b1) #7 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #8 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) ELF object binary architecture: AMD x86-64
Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'avahi-autoipd', 'systemd-journal', 'wheel' can see all messages. Pass -q to turn off this notice. PID: 95382 (dolphin) UID: 1000 (tim) GID: 1000 (tim) Signal: 11 (SEGV) Timestamp: Mon 2025-03-31 18:37:54 BST (1 day 2h ago) Command Line: /usr/bin/dolphin /run/media/tim/6EC3630B5CD252D3 Executable: /usr/bin/dolphin Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.dolphin@999dd0214804477d9da4fc973a8032d7.service Unit: user@1000.service User Unit: app-org.kde.dolphin@999dd0214804477d9da4fc973a8032d7.service Slice: user-1000.slice Owner UID: 1000 (tim) Boot ID: 78b16d142f0c42caae4777f9862a7ce3 Machine ID: 20929a07718146d2bfcc6e544e17dfcc Hostname: tim-solus Storage: /var/lib/systemd/coredump/core.dolphin.1000.78b16d142f0c42caae4777f9862a7ce3.95382.1743442674000000.zst (present) Size on Disk: 8.6M Message: Process 95382 (dolphin) of user 1000 dumped core. Stack trace of thread 95382: #0 0x00007f3e3a4aad4b pthread_kill (libc.so.6 + 0x9fd4b) #1 0x00007f3e3a44fb56 raise (libc.so.6 + 0x44b56) #2 0x00007f3e3cd9eeb4 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7eb4) #3 0x00007f3e3a44fc80 n/a (libc.so.6 + 0x44c80) #4 0x00007f3e3c02bebc _ZNK11QMainWindow7menuBarEv (libQt6Widgets.so.6 + 0x42bebc) #5 0x00007f3e305ecfed n/a (breeze6.so + 0x76fed) #6 0x00007f3e3ad388f4 n/a (libQt6Core.so.6 + 0x3388f4) #7 0x00007f3e3c8bfba5 n/a (libKF6ConfigCore.so.6 + 0x6bba5) #8 0x00007f3e3c8bfee0 _ZN14KConfigWatcher11qt_metacallEN11QMetaObject4CallEiPPv (libKF6ConfigCore.so.6 + 0x6bee0) #9 0x00007f3e3bb96f6e n/a (libQt6DBus.so.6 + 0x56f6e) #10 0x00007f3e3ad2e2aa _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x32e2aa) #11 0x00007f3e3be4d1a0 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x24d1a0) #12 0x00007f3e3be4e3e3 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x24e3e3) #13 0x00007f3e3acd74ff _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x2d74ff) #14 0x00007f3e3acd8813 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x2d8813) #15 0x00007f3e3afe34db n/a (libQt6Core.so.6 + 0x5e34db) #16 0x00007f3e379de288 n/a (libglib-2.0.so.0 + 0x76288) #17 0x00007f3e37a6a01a n/a (libglib-2.0.so.0 + 0x10201a) #18 0x00007f3e379dca74 g_main_context_iteration (libglib-2.0.so.0 + 0x74a74) #19 0x00007f3e3afe2db6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5e2db6) #20 0x00007f3e3ace2926 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2e2926) #21 0x00007f3e3acd7d4e _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x2d7d4e) #22 0x0000559432037105 n/a (dolphin + 0x79105) #23 0x00007f3e3a4362ec n/a (libc.so.6 + 0x2b2ec) #24 0x00007f3e3a4363a9 __libc_start_main (libc.so.6 + 0x2b3a9) #25 0x0000559432033795 n/a (dolphin + 0x75795) Stack trace of thread 95386: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a517883 ppoll (libc.so.6 + 0x10c883) #3 0x00007f3e37a69fcd n/a (libglib-2.0.so.0 + 0x101fcd) #4 0x00007f3e379dca74 g_main_context_iteration (libglib-2.0.so.0 + 0x74a74) #5 0x00007f3e3afe2db6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5e2db6) #6 0x00007f3e3ace2926 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2e2926) #7 0x00007f3e3ae05dfc _ZN7QThread4execEv (libQt6Core.so.6 + 0x405dfc) #8 0x00007f3e3bb9007e n/a (libQt6DBus.so.6 + 0x5007e) #9 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #10 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #11 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95387: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a5173fa __poll (libc.so.6 + 0x10c3fa) #3 0x00007f3e39198f69 n/a (libQt6WaylandClient.so.6 + 0x90f69) #4 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #5 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #6 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95388: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a5173fa __poll (libc.so.6 + 0x10c3fa) #3 0x00007f3e39198f69 n/a (libQt6WaylandClient.so.6 + 0x90f69) #4 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #5 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #6 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95420: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a517883 ppoll (libc.so.6 + 0x10c883) #3 0x00007f3e37a69fcd n/a (libglib-2.0.so.0 + 0x101fcd) #4 0x00007f3e379e38a6 n/a (libglib-2.0.so.0 + 0x7b8a6) #5 0x00007f3e37a224b1 n/a (libglib-2.0.so.0 + 0xba4b1) #6 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #7 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 96049: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a51807a __write (libc.so.6 + 0x10d07a) #3 0x00007f3e3ac8a9bf n/a (libQt6Core.so.6 + 0x28a9bf) #4 0x00007f3e3ac7d8e4 _ZN11QFileDevice9writeDataEPKcx (libQt6Core.so.6 + 0x27d8e4) #5 0x00007f3e3ac8f743 _ZN9QIODevice5writeEPKcx (libQt6Core.so.6 + 0x28f743) #6 0x00007f3e1df25ccb n/a (kio_file.so + 0x12ccb) #7 0x00007f3e1df26e72 n/a (kio_file.so + 0x13e72) #8 0x00007f3e3ce6ef06 n/a (libKF6KIOCore.so.6 + 0xc9f06) #9 0x00007f3e3ce680d1 n/a (libKF6KIOCore.so.6 + 0xc30d1) #10 0x00007f3e3ce61c34 n/a (libKF6KIOCore.so.6 + 0xbcc34) #11 0x00007f3e3cefed5f n/a (libKF6KIOCore.so.6 + 0x159d5f) #12 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #13 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #14 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95393: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a517883 ppoll (libc.so.6 + 0x10c883) #3 0x00007f3e37a69fcd n/a (libglib-2.0.so.0 + 0x101fcd) #4 0x00007f3e379dca74 g_main_context_iteration (libglib-2.0.so.0 + 0x74a74) #5 0x00007f3e3afe2db6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5e2db6) #6 0x00007f3e3ace2926 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2e2926) #7 0x00007f3e3ae05dfc _ZN7QThread4execEv (libQt6Core.so.6 + 0x405dfc) #8 0x00007f3e3aeb0eeb n/a (libQt6Core.so.6 + 0x4b0eeb) #9 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #10 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95419: #0 0x00007f3e3a5215bd syscall (libc.so.6 + 0x1165bd) #1 0x00007f3e37a28c3a n/a (libglib-2.0.so.0 + 0xc0c3a) #2 0x00007f3e37a224b1 n/a (libglib-2.0.so.0 + 0xba4b1) #3 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #4 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) Stack trace of thread 95421: #0 0x00007f3e3a4b1072 n/a (libc.so.6 + 0xa6072) #1 0x00007f3e3a4a548c n/a (libc.so.6 + 0x9a48c) #2 0x00007f3e3a517883 ppoll (libc.so.6 + 0x10c883) #3 0x00007f3e37a69fcd n/a (libglib-2.0.so.0 + 0x101fcd) #4 0x00007f3e379e1ecf g_main_loop_run (libglib-2.0.so.0 + 0x79ecf) #5 0x00007f3e33978ec0 n/a (libgio-2.0.so.0 + 0x178ec0) #6 0x00007f3e37a224b1 n/a (libglib-2.0.so.0 + 0xba4b1) #7 0x00007f3e3a4a8ee4 n/a (libc.so.6 + 0x9dee4) #8 0x00007f3e3a523ddc n/a (libc.so.6 + 0x118ddc) ELF object binary architecture: AMD x86-64
[Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib64/libthread_db.so.1". --Type <RET> for more, q to quit, c to continue without paging-- Core was generated by `/usr/bin/dolphin /run/media/tim/6EC3630B5CD252D3'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f3e3a4aad4b in pthread_kill () from /usr/lib/glibc-hwcaps/x86-64-v3/libc.so.6 [Current thread is 1 (Thread 0x7f3e3348ba40 (LWP 95382))]
(In reply to Tim from comment #5) > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/usr/lib64/libthread_db.so.1". > --Type <RET> for more, q to quit, c to continue without paging-- > Core was generated by `/usr/bin/dolphin /run/media/tim/6EC3630B5CD252D3'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x00007f3e3a4aad4b in pthread_kill () from > /usr/lib/glibc-hwcaps/x86-64-v3/libc.so.6 > [Current thread is 1 (Thread 0x7f3e3348ba40 (LWP 95382))] Also seeing a crash in Simple-scan also with segmentation fault if that helps.
Thanks for the backtrace. Unfortunately it's missing some debug symbols for the following lines that we need to figure out exactly what's going wrong: #5 0x00007f3e305ecfed n/a (breeze6.so + 0x76fed) #6 0x00007f3e3ad388f4 n/a (libQt6Core.so.6 + 0x3388f4) Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window and getting a new backtrace? 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! (In reply to Tim from comment #6) > Also seeing a crash in Simple-scan also with segmentation fault if that > helps. That's likely a different crash with a different cause. If Dr Konqui crash reporter comes up, please use it to create a new bug report. Otherwise, you can create a new report and get another backtrace manually like you did for this report.
(In reply to TraceyC from comment #7) > Thanks for the backtrace. Unfortunately it's missing some debug symbols for > the following lines that we need to figure out exactly what's going wrong: > > > #5 0x00007f3e305ecfed n/a (breeze6.so + 0x76fed) > #6 0x00007f3e3ad388f4 n/a (libQt6Core.so.6 + 0x3388f4) > > Could you please install debug symbols and attach a new symbolicated > backtrace generated by using `coredumpctl gdb` in a terminal window and > getting a new backtrace? 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! > > (In reply to Tim from comment #6) > > Also seeing a crash in Simple-scan also with segmentation fault if that > > helps. > > That's likely a different crash with a different cause. If Dr Konqui crash > reporter comes up, please use it to create a new bug report. Otherwise, you > can create a new report and get another backtrace manually like you did for > this report. eopkg search cant find breeze6.so or libQt6Core.so.6 symbols. Also coredumpctl no longer sees the crash trace only Simple Scan trace is listed. I need some help here.
(In reply to Tim from comment #8) > eopkg search cant find breeze6.so or libQt6Core.so.6 symbols. With eopkg, I've found the easiest way to find debug packages is to do a search for a keyword and grep for "dbg" similar to this: eopkg sr breeze | grep dbg breeze-icons-dbginfo - Debug symbols for breeze-icons breeze-dbginfo - Debug symbols for breeze So then you'd install breeze-dbginfo For libQt6Core for instance: ❯ eopkg sr --name qt6 | grep dbg That gives a long list of things, but this is the one you want qt6-base-dbginfo - Debug symbols for qt6-base . Also > coredumpctl no longer sees the crash trace only Simple Scan trace is listed. Unfortunately, without a better backtrace, we won't be able to investigate where in the code the problem is. You can try: 1. See if there's still a file in /var/lib/systemd/coredump for dolphin 2. It might be easier to try to reproduce the crash and get the backtrace from that (after installing the debug packages)
(In reply to TraceyC from comment #9) > (In reply to Tim from comment #8) > > > eopkg search cant find breeze6.so or libQt6Core.so.6 symbols. > > With eopkg, I've found the easiest way to find debug packages is to do a > search for a keyword and grep for "dbg" similar to this: > > eopkg sr breeze | grep dbg > breeze-icons-dbginfo - Debug symbols for breeze-icons > breeze-dbginfo - Debug symbols for breeze > > So then you'd install breeze-dbginfo > For libQt6Core for instance: > > ❯ eopkg sr --name qt6 | grep dbg > > That gives a long list of things, but this is the one you want > > qt6-base-dbginfo - Debug symbols for qt6-base > > > . Also > > coredumpctl no longer sees the crash trace only Simple Scan trace is listed. > > Unfortunately, without a better backtrace, we won't be able to investigate > where in the code the problem is. You can try: > 1. See if there's still a file in /var/lib/systemd/coredump for dolphin > 2. It might be easier to try to reproduce the crash and get the backtrace > from that (after installing the debug packages) There is a file in Systemd/coredump for Dolphin what do I do to process it. Also have successfully installed the debug symbols.
The file is a .zst and tried extracting it and open with crash process viewer but doesn't work.
(In reply to Tim from comment #11) > The file is a .zst and tried extracting it and open with crash process > viewer but doesn't work. It's not necessary to extract the zst file. If you open the Crash Process Viewer, it will show all the crash logs on your system. Click on the most recent one for Dolphin, copy the information to the clipboard and then paste it into a comment in this report.
Created attachment 179967 [details] Screentshot of Crash Viewer after opening .zst file I tried that but as you can see from the attachment the crash viewer is empty
(In reply to Tim from comment #13) > Created attachment 179967 [details] > Screentshot of Crash Viewer after opening .zst file > > I tried that but as you can see from the attachment the crash viewer is empty I see what you mean in your screenshot. Did you open the Crash Viewer first or try to open the file?
(In reply to TraceyC from comment #14) > (In reply to Tim from comment #13) > > Created attachment 179967 [details] > > Screentshot of Crash Viewer after opening .zst file > > > > I tried that but as you can see from the attachment the crash viewer is empty > > I see what you mean in your screenshot. Did you open the Crash Viewer first > or try to open the file? Used 'Open with' then selected all installed programs then selected crash viewer. The crash viewer opened on its own has been empty for a couple of days now. According to time stamp the dolphin archive file is from Monday which would be correct.
The crash reporter is meant to be opened first. Close it out and re-open it. That should make it re-read the list of crashes. Then open the most recent entry for Dolphin.
(In reply to TraceyC from comment #16) > The crash reporter is meant to be opened first. Close it out and re-open it. > That should make it re-read the list of crashes. Then open the most recent > entry for Dolphin. Still doesn't work no crashes listed and .zst opens with ark so removed that from default applications and still get a blank window as per screenshot.
I'm confused why just opening Crashed Processes Viewer results in a blank window, since there are crash dumps. Can I ask you to reproduce the crash and get a new crash dump?
(In reply to TraceyC from comment #18) > I'm confused why just opening Crashed Processes Viewer results in a blank > window, since there are crash dumps. > Can I ask you to reproduce the crash and get a new crash dump? Unfortunately after reboot I am unable to reproduce the crash. I have checked my other plasma machines and only one is populated and that is a VM which has a fairly fresh install of Solus and it shows a crash way back in January. The dir for the crash logs has about 8 entries for the machine that crashed but none show in crashed processes viewer, looks like a bug with the viewer.
🐛🧹 ⚠️ 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.