Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1057767: pipewire: Last upgrade completely broke bluetooth connection: : org.bluez.Error.Failed br-connection-unknown
47 views
Skip to first unread message
arne anka
Dec 8, 2023, 4:50:06 AM12/8/23
to
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
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
debian-bugs
Dec 11, 2023, 5:10:06 AM12/11/23
to
Resumed from hibernate today and again got the error
Failed to connect: org.bluez.Error.Failed br-connection-unknown
despite downgrading those 4 pipewire packages.
After reboot and _before_ logging on to KDE, I switched to a console and
connected the RemoteMic+. That worked.
After login the RemoteMic+ still was connected and found by PulseAudio
with both A2DP and HSP/HFP and works.
May there be some miscommunication between bluez and PulseAudio?
(I fail to understand why _any_ PipeWire stuff is pulled in at all when
I use PulseAudio _only_ -- PW fails miserably to work with RemoteMic+,
even in version 1.0.0).
On 08/12/2023 10:48, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1057767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057767.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
> deb...@ginguppin.de
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
> Utopia Maintenance Team <pkg-utopia-...@alioth-lists.debian.net>
>
> If you wish to submit further information on this problem, please
> send it to 105...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
Failed to connect: org.bluez.Error.Failed br-connection-unknown
After reboot and _before_ logging on to KDE, I switched to a console and
connected the RemoteMic+. That worked.
After login the RemoteMic+ still was connected and found by PulseAudio
with both A2DP and HSP/HFP and works.
May there be some miscommunication between bluez and PulseAudio?
(I fail to understand why _any_ PipeWire stuff is pulled in at all when
I use PulseAudio _only_ -- PW fails miserably to work with RemoteMic+,
even in version 1.0.0).
On 08/12/2023 10:48, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1057767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057767.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
> deb...@ginguppin.de
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
> Utopia Maintenance Team <pkg-utopia-...@alioth-lists.debian.net>
>
> If you wish to submit further information on this problem, please
> send it to 105...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
Dylan Aïssi
Dec 12, 2023, 5:30:05 AM12/12/23
to
Hi,
Le ven. 8 déc. 2023 à 10:48, arne anka <deb...@ginguppin.de> a écrit :
>
> * 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.
Did you try downgrading only firmware-iwlwifi to the last working version
without downgrading pipewire? Was the kernel updated at the same time?
If you can confirm that the problem comes from pipewire, it's worth filling
a bug report upstream at:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues
Best regards,
Dylan
Le ven. 8 déc. 2023 à 10:48, arne anka <deb...@ginguppin.de> a écrit :
>
> * 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.
without downgrading pipewire? Was the kernel updated at the same time?
If you can confirm that the problem comes from pipewire, it's worth filling
a bug report upstream at:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues
Best regards,
Dylan
debian-bugs
Dec 13, 2023, 1:10:06 PM12/13/23
to
That was the first thing.
Only after that didn't help I downgraded those four packages.
From my POV I _don't_ use PipeWire -- I have no idea why those packages
are pulled in since I sue PulseAudio.
Since I don't know what exactly happens I am unable to say if it is PW
related (and if it were, wouldn't that make it a Debian issue since I
don't use PW, but PA and do try to actively avoid PW?).
Only after that didn't help I downgraded those four packages.
From my POV I _don't_ use PipeWire -- I have no idea why those packages
are pulled in since I sue PulseAudio.
Since I don't know what exactly happens I am unable to say if it is PW
related (and if it were, wouldn't that make it a Debian issue since I
don't use PW, but PA and do try to actively avoid PW?).
debian-bugs
Jan 10, 2024, 3:00:05 AM1/10/24
to
Seems to be solved with the latest update I ran on Friday (all 4
packages to 1.0.0.-3).
packages to 1.0.0.-3).
0 new messages