Qdbus6 coredump

The odd thing is I run my qdbus6 kwin screen commands from within a bash script the script runs but I get only an error message. Annoying but not a disaster. If I run the qdbus6 commands from a terminal it crashes the whole thing immediately.

Getting this:

           PID: 12454 (qdbus6)
           UID: 1000 (dougrrr)
           GID: 1001 (dougrrr)
        Signal: 11 (SEGV)
     Timestamp: Sun 2026-03-29 14:29:04 EDT (2h 6min ago)
  Command Line: qdbus6 org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut $'Window Grow Horizontal '
    Executable: /usr/lib/qt6/bin/qdbus
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fhome\x2fdougrrr\x2fscripts\x2fxpand_only.sh@a4e6c20d46bc4a3281eb924fc0045c0c.service
          Unit: user@1000.service
     User Unit: app-\x2fhome\x2fdougrrr\x2fscripts\x2fxpand_only.sh@a4e6c20d46bc4a3281eb924fc0045c0c.service
         Slice: user-1000.slice
     Owner UID: 1000 (dougrrr)
       Boot ID: 4fa400af16bd49b0944d6e6a46785414
    Machine ID: 7290906c26be4c049b27d455ca649dbf
      Hostname: douglas-xpsm1330
       Storage: /var/lib/systemd/coredump/core.qdbus6.1000.4fa400af16bd49b0944d6e6a46785414.12454.1774808944000000.zst (present)
  Size on Disk: 191.7K
       Message: Process 12454 (qdbus6) of user 1000 dumped core.
                
                Stack trace of thread 12454:
                #0  0x00007fd6232a74d1 n/a (libQt6Core.so.6 + 0xa74d1)
                #1  0x00007fd6239b39eb n/a (libQt6DBus.so.6 + 0x5e9eb)
                #2  0x00007fd622c4fa61 n/a (libc.so.6 + 0x40a61)
                #3  0x00007fd622c4fb3e exit (libc.so.6 + 0x40b3e)
                #4  0x00007fd622c366c8 n/a (libc.so.6 + 0x276c8)
                #5  0x00007fd622c367f9 __libc_start_main (libc.so.6 + 0x277f9)
                #6  0x000055b87bfcf745 n/a (/usr/lib/qt6/bin/qdbus + 0x6745)
                
                Stack trace of thread 12457:
                #0  0x00007fd622cadf32 n/a (libc.so.6 + 0x9ef32)
                #1  0x00007fd622ca239c n/a (libc.so.6 + 0x9339c)
                #2  0x00007fd622ca23e4 n/a (libc.so.6 + 0x933e4)
                #3  0x00007fd622d1c2f6 ppoll (libc.so.6 + 0x10d2f6)
                #4  0x00007fd623108744 n/a (libglib-2.0.so.0 + 0x60744)
                #5  0x00007fd623108825 g_main_context_iteration (libglib-2.0.so.0 + 0x60825)
                #6  0x00007fd623672222 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x472222)
                #7  0x00007fd6233845d6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1845d6)
                #8  0x00007fd62349efa2 _ZN7QThread4execEv (libQt6Core.so.6 + 0x29efa2)
                #9  0x00007fd62398c50e n/a (libQt6DBus.so.6 + 0x3750e)
                #10 0x00007fd62354d483 n/a (libQt6Core.so.6 + 0x34d483)
                #11 0x00007fd622ca597a n/a (libc.so.6 + 0x9697a)
                #12 0x00007fd622d292bc n/a (libc.so.6 + 0x11a2bc)
                ELF object binary architecture: AMD x86-64

/home/dougrrr/scripts/xpand_only.sh

Bingo. A typo in my script. I wonder why it never showed up before. Anyway, thank you so much.

1 Like

A typo in a script leading to a segfault in qdbus6..
Crisis averted but the segfault still smells like bug to me.

1 Like

your suspicions are justified;

Thanks for the confirmation.

The issue is addressed with qt6-base 6.11.0-2 now available in the Manjaro unstable branch.

2 Likes