Package: bluez Version: 5.71-1 Followup-For: Bug #995399 X-Debbugs-Cc: mar...@tonusoo.ee
I observed pretty much the identical behavior described by Flavio Amieiro after upgrading to 5.71-1. The bluetooth speaker connected for ~5 seconds, after which the bluetoothd segfaulted: [Thu Jan 25 23:37:29 2024] input: Bedroom speaker (AVRCP) as /devices/virtual/input/input36 [Thu Jan 25 23:37:36 2024] bluetoothd[8904]: segfault at 5621e0155f79 ip 0000562480a64375 sp 00007ffd9e9c66e0 error 4 in bluetoothd[562480a42000+ec000] likely on CPU 0 (core 0, socket 0) [Thu Jan 25 23:37:36 2024] Code: 00 31 c0 e9 54 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 41 55 41 54 55 53 48 83 ec 08 48 8b 2a 48 8b 7a 08 <48> 8b 45 20 4c 8b ad 88 00 00 00 4c 8b 20 48 85 ff 74 19 c7 47 08 Upgrading to 5.72 from the upstream fixed this issue. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bluez depends on: ii dbus [default-dbus-system-bus] 1.14.10-4 ii init-system-helpers 1.66 ii kmod 31-1 ii libasound2 1.2.10-3 ii libc6 2.37-14 ii libdbus-1-3 1.14.10-4 ii libdw1 0.190-1+b1 ii libglib2.0-0 2.78.3-2 ii libreadline8 8.2-3 ii libudev1 255.3-1 ii udev 255.3-1 bluez recommends no packages. Versions of packages bluez suggests: ii pulseaudio-module-bluetooth 16.1+dfsg1-3 -- Configuration Files: /etc/bluetooth/main.conf changed [not included] -- no debconf information
