Your message dated Mon, 29 Apr 2024 14:32:48 +0200
with message-id 
<CA+6XHwQF+9aDg72ihJTLrv1yGFQa_De_D8=R97j=ei3zthh...@mail.gmail.com>
and subject line Re: Bug#1057767: Info received (Bug#1057767: pipewire: Last 
upgrade completely broke bluetooth connection: : org.bluez.Error.Failed 
br-connection-unknown)
has caused the Debian Bug report #1057767,
regarding pipewire: Last upgrade completely broke bluetooth connection: : 
org.bluez.Error.Failed br-connection-unknown
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1057767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057767
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pipewire
Version: 1.0.0-1
Severity: important
Tags: a11y

Dear Maintainer,

after a recent upgrade, my BT headset (for lack of a better word, see below) 
won't connect anymore.
I always get 
Failed to connect: org.bluez.Error.Failed br-connection-unknown



   * What led up to the situation?

On Dec 6 I upgraded and since the my BT thingy does not connect to my PC 
anymore.
I am hearing impaired and need to use a BT thingy called RemoteMic+ (by 
Starkey) to be able to listen to music or make calls/attend meetings via PC. 
So, this is a major issue for me.
Among others these packages were upgraded:

firmware-iwlwifi

libpipewire-0.3-0
libpipewire-0.3-common
libspa-0.2-bluetooth
libspa-0.2-modules


   * What exactly did you do (or not do) that was effective (or
     ineffective)?

First I downgraded firmware-iwlwifi to version 20230210-5 -- to no avail.

Next, I downgraded

libpipewire-0.3-0
libpipewire-0.3-common
libspa-0.2-bluetooth
libspa-0.2-modules

to version 0.3.85-1 again -- and things started to work again.
Since those packages depend on another, I couldn't downgrade just one, hence 
the report on the source package -- but I suspect a change in 
libspa-0.2-bluetooth to be responsible.

BT adapter:
ID 8087:0029 Intel Corp. AX200 Bluetooth


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Version: 1.0.0-3

Le mer. 10 janv. 2024 à 08:57, debian-bugs <[email protected]> a écrit :
>
> Seems to be solved with the latest update I ran on Friday (all 4
> packages to 1.0.0.-3).
>

--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to