Package: bluez Version: 5.79-1 Followup-For: Bug #1087761 X-Debbugs-Cc: vent...@debian.org
Dear Maintainer, turns out that a workaround for this issue is to remove the device (i.e. "forgetting" it in Gnome Bluetooth settings) and then re-pair it. I'm not sure if this bug is related to the new version or just a coincidence. Cheers, Bastian -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.11.7-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=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 bluez depends on: ii dbus [default-dbus-system-bus] 1.14.10-6 ii init-system-helpers 1.67 ii kmod 33+20240816-2 ii libasound2t64 1.2.12-1+b1 ii libc6 2.40-3 ii libdbus-1-3 1.14.10-6 ii libdw1t64 0.192-4 ii libglib2.0-0t64 2.82.2-3 ii libreadline8t64 8.2-5 ii libudev1 257~rc2-3 ii udev 257~rc2-3 bluez recommends no packages. Versions of packages bluez suggests: pn pulseaudio-module-bluetooth <none> -- no debconf information
