From: thom1982@gmail.com   
      
   Package: dbus-broker   
   Version: 37-2   
   Severity: important   
   X-Debbugs-Cc: thom1982@gmail.com   
      
   Dear Maintainer,   
      
   I experienced system crashes on both my office PC and home laptop last week.   
   Both systems use dbus-broker 37-2 (from the Debian stable release).   
      
   After diving deeper into the issue, I found the following coredumps:   
      
   ls -la /var/lib/systemd/coredump/   
   -rw-r-----+  1 root root  171555 Feb 10 23:14 core.dbus-broker.1   
   03.0baeeead1fa4433faf59ac21769b6f34.119538.1770729295000000.zst   
   -rw-r-----+  1 root root 1497429 Feb 10 19:23 core.kwin_x11.1003   
   0baeeead1fa4433faf59ac21769b6f34.643643.1770715425000000.zst   
   -rw-r-----+  1 root root 1054550 Feb 10 23:14 core.wireplumber.1   
   03.0baeeead1fa4433faf59ac21769b6f34.119541.1770729295000000.zst   
      
      
   Unfortunately, I do not have debug symbols installed, so I am not sure if the   
   backtrace will be useful.   
      
   == home laptop ==   
      
   Reading symbols from /usr/bin/dbus-broker...   
   (No debugging symbols found in /usr/bin/dbus-broker)   
   [New LWP 3295]   
   [Thread debugging using libthread_db enabled]   
   Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".   
   Core was generated by `/usr/bin/dbus-broker --log 11 --controller 10   
   --machine-id 31401a4ff1b14510b6092ba1b5ff3fcc --max-bytes 100000000000000   
   --max-fds 25000000000000 --max-matches 5000000000'.   
   Program terminated with signal SIGSEGV, Segmentation fault.   
   #0 0x00007fac89513259 in ?? () from /lib/x86_64-linux-gnu/libc.so.6   
   (gdb) bt   
   #0 0x00007fac89513259 in ?? () from /lib/x86_64-linux-gnu/libc.so.6   
   #1 0x00005566944e08fb in ?? ()   
   #2 0x00005566944e0bfa in ?? ()   
   #3 0x00005566944e18f7 in ?? ()   
   #4 0x00005566944d8b31 in ?? ()   
   #5 0x00005566944d5d62 in ?? ()   
   #6 0x00005566944cfe94 in ?? ()   
   #7 0x00005566944d48ad in ?? ()   
   #8 0x00005566944dd980 in ?? ()   
   #9 0x00005566944c4bdc in ?? ()   
   #10 0x00005566944c3fa8 in ?? ()   
   #11 0x00007fac893d6ca8 in ?? () from /lib/x86_64-linux-gnu/libc.so.6   
   #12 0x00007fac893d6d65 in __libc_start_main () from /lib/x86_64-   
   inux-gnu/libc.so.6   
   #13 0x00005566944c4311 in ?? ()   
   (gdb)   
      
      
   == office pc ==   
      
   Reading symbols from /usr/bin/dbus-broker...   
   (No debugging symbols found in /usr/bin/dbus-broker)   
   [New LWP 119538]   
   [Thread debugging using libthread_db enabled]   
   Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".   
   Core was generated by `/usr/bin/dbus-broker --log 11 --controller 10   
   --machine-id 643e593e8e114aa78b1476d6b1f83289 --max-bytes 100000000000000   
   --max-fds 25000000000000 --max-matches 5000000000'.   
   Program terminated with signal SIGSEGV, Segmentation fault.   
   #0  0x00007f51d6ab1259 in ?? () from /lib/x86_64-linux-gnu/libc.so.6   
   (gdb) bt   
   #0  0x00007f51d6ab1259 in ?? () from /lib/x86_64-linux-gnu/libc.so.6   
   #1  0x00005582010378fb in ?? ()   
   #2  0x0000558201037bfa in ?? ()   
   #3  0x00005582010388f7 in ?? ()   
   #4  0x000055820102fb31 in ?? ()   
   #5  0x000055820102cd62 in ?? ()   
   #6  0x0000558201026e94 in ?? ()   
   #7  0x000055820102b8ad in ?? ()   
   #8  0x0000558201034980 in ?? ()   
   #9  0x000055820101bbdc in ?? ()   
   #10 0x000055820101afa8 in ?? ()   
   #11 0x00007f51d6974ca8 in ?? () from /lib/x86_64-linux-gnu/libc.so.6   
   #12 0x00007f51d6974d65 in __libc_start_main () from /lib/x86_64-   
   inux-gnu/libc.so.6   
   #13 0x000055820101b311 in ?? ()   
   (gdb)   
      
      
   As I can see, there is a closed bug with similar symptoms:   
   #1123876 (dbus-broker: Crashes when trying to mount encrypted USB from Plasma).   
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123876   
      
      
   Could you please consider cherry-picking the fix from version 37-4   
   into a point release for Trixie stable (via trixie-proposed-updates)   
   or providing an updated version through trixie-backports?   
      
      
   Thank you!   
      
      
      
      
   -- System Information:   
   Debian Release: 13.3   
     APT prefers stable-updates   
     APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990,   
   'stable'), (500, 'proposed-updates'), (100, 'trixie-fasttrack'), (100,   
   'trixie-backports-staging')   
   Architecture: amd64 (x86_64)   
      
   Kernel: Linux 6.18.5+deb13-amd64 (SMP w/12 CPU threads; PREEMPT)   
   Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE   
   Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to   
   C.UTF-8), LANGUAGE not set   
   Shell: /bin/sh linked to /usr/bin/dash   
   Init: systemd (via /run/systemd/system)   
   LSM: AppArmor: enabled   
      
   Versions of packages dbus-broker depends on:   
   ii  dbus-system-bus-common  1.16.2-2   
   ii  init-system-helpers     1.69~deb13u1   
   ii  libapparmor1            4.1.0-1   
   ii  libaudit1               1:4.0.2-2+b2   
   ii  libc6                   2.41-12+deb13u1   
   ii  libcap-ng0              0.8.5-4+b1   
   ii  libexpat1               2.7.1-2   
   ii  libselinux1             3.8.1-1   
   ii  libsystemd0             257.9-1~deb13u1   
   ii  systemd-sysv            257.9-1~deb13u1   
      
   Versions of packages dbus-broker recommends:   
   ii  dbus-bin  1.16.2-2   
      
   dbus-broker suggests no packages.   
      
   -- no debconf information   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)