https://bugs.kde.org/show_bug.cgi?id=518172
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WORKSFORME |--- CC| |[email protected] | |m Ever confirmed|0 |1 Status|RESOLVED |REOPENED --- Comment #5 from [email protected] --- Hi, I also face this issue on KDE Plasma 6.7.0. Here is how I trigger it: 1. Log out of the current KDE Plasma session (Wayland). 2. At the login screen, wait a few seconds and log back in immediately. 3. A crash notification appears indicating that drkonqi-coredump-launcher has crashed. System information: Operating System: CachyOS Linux KDE Plasma Version: 6.7.0 KDE Frameworks Version: 6.27.0 Qt Version: 6.11.1 Kernel Version: 7.0.12-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 8 GiB of RAM (7.7 GiB usable) Graphics Processor: Intel® HD Graphics 5500 Here is the full log: PID: 5319 (drkonqi-coredum) UID: 1000 (nguyen) GID: 1000 (nguyen) Signal: 6 (ABRT) Timestamp: Sat 2026-06-20 08:55:36 +07 (2min 55s ago) Command Line: /usr/lib/drkonqi-coredump-launcher Executable: /usr/lib/drkonqi-coredump-launcher Control Group: /user.slice/user-1000.slice/[email protected]/app.slice/drkonqi-coredump-launcher@91-4163-5295_13491-0.service Unit: [email protected] User Unit: drkonqi-coredump-launcher@91-4163-5295_13491-0.service Slice: user-1000.slice Owner UID: 1000 (nguyen) Boot ID: ca979dc93b66467684c81d9aef7ceeaa Machine ID: 5d4979dc068a4f01a2b7e523a310f3b5 Hostname: dell Storage: /var/lib/systemd/coredump/core.drkonqi-coredum.1000.ca979dc93b66467684c81d9aef7ceeaa.5319.1781920536000000.zst (present) Size on Disk: 821.4K Message: Process 5319 (drkonqi-coredum) of user 1000 dumped core. Stack trace of thread 5319: #0 0x00007f6d732adfbb pthread_kill (libc.so.6 + 0xadfbb) #1 0x00007f6d73244c88 raise (libc.so.6 + 0x44c88) #2 0x00007f6d73225795 abort (libc.so.6 + 0x25795) #3 0x00007f6d73c96c82 n/a (libQt6Core.so.6 + 0x96c82) #4 0x00007f6d73c97c14 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x97c14) #5 0x00007f6d744e7447 n/a (libQt6Gui.so.6 + 0xe7447) #6 0x00007f6d745c5258 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x1c5258) #7 0x00007f6d73d9edd5 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x19edd5) #8 0x00007f6d745c5384 _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x1c5384) #9 0x00007f6d745b9ece _ZN15QGuiApplicationC2ERiPPci (libQt6Gui.so.6 + 0x1b9ece) #10 0x000055b58f76bdf2 n/a (drkonqi-coredump-launcher + 0x6df2) #11 0x00007f6d73227c8e n/a (libc.so.6 + 0x27c8e) #12 0x00007f6d73227dcb __libc_start_main (libc.so.6 + 0x27dcb) #13 0x000055b58f76dd65 n/a (drkonqi-coredump-launcher + 0x8d65) Stack trace of thread 5325: #0 0x00007f6d73347b1d syscall (libc.so.6 + 0x147b1d) #1 0x00007f6d73dfd01b n/a (libQt6Core.so.6 + 0x1fd01b) #2 0x00007f6d73d98e72 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x198e72) #3 0x00007f6d740f8ce0 n/a (libQt6Core.so.6 + 0x4f8ce0) #4 0x00007f6d72dad02d n/a (libglib-2.0.so.0 + 0x6c02d) #5 0x00007f6d72dae558 n/a (libglib-2.0.so.0 + 0x6d558) #6 0x00007f6d72dae6b2 g_main_context_iteration (libglib-2.0.so.0 + 0x6d6b2) #7 0x00007f6d740f584b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4f584b) #8 0x00007f6d73da78b4 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1a78b4) #9 0x00007f6d73eedffe _ZN7QThread4execEv (libQt6Core.so.6 + 0x2edffe) #10 0x00007f6d7436a2c9 n/a (libQt6DBus.so.6 + 0x3a2c9) #11 0x00007f6d73fb6f79 n/a (libQt6Core.so.6 + 0x3b6f79) #12 0x00007f6d732abd58 n/a (libc.so.6 + 0xabd58) #13 0x00007f6d7334a5dc n/a (libc.so.6 + 0x14a5dc) ELF object binary architecture: AMD x86-64 -- You are receiving this mail because: You are watching all bug changes.
