Package: blueman Version: 2.1.4-1+b1 Severity: normal Dear Maintainer,
When I open `blueman-manager` and try to connect to a Bluetooth speaker by clicking *Device* and then *Connect*, I often get the error: > Connection failed: Software caused connection abort This will keeps happening the first few times I try connecting, but it always connects eventually. I was expecting that when I clicked *Connect*, than Blueman would then connect to the device (perhaps automatically retry upon failure) instead of me having to repeatedly click on the same menu item. -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 blueman depends on: ii adwaita-icon-theme 3.38.0-1 ii bluez 5.55-3 ii bluez-obexd 5.55-3 ii dbus 1.12.20-2 ii dbus-user-session [default-dbus-session-bus] 1.12.20-2 ii dbus-x11 [dbus-session-bus] 1.12.20-2 ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2 ii gir1.2-ayatanaappindicator3-0.1 0.5.5-3 ii gir1.2-gdkpixbuf-2.0 2.42.2+dfsg-1 ii gir1.2-glib-2.0 1.66.1-1+b1 ii gir1.2-gtk-3.0 3.24.24-3 ii gir1.2-nm-1.0 1.30.0-2 ii gir1.2-pango-1.0 1.48.2-1 ii gnome-icon-theme 3.12.0-3 ii libbluetooth3 5.55-3 ii libc6 2.31-11 ii libglib2.0-0 2.66.8-1 ii libpulse-mainloop-glib0 14.2-2 ii librsvg2-common 2.50.3+dfsg-1 ii notification-daemon 3.20.0-4 ii policykit-1 0.105-30 ii python3 3.9.2-3 ii python3-cairo 1.16.2-4+b2 ii python3-gi 3.38.0-2 ii python3-gi-cairo 3.38.0-2 Versions of packages blueman recommends: ii pulseaudio-module-bluetooth 14.2-2 blueman suggests no packages.
