Description of problem:
Bluetooth headphones fail to reconnect after a successful pairing.
MB: Asus ROG STRIX B360-I Gaming
BT: Intel 9460/9560
Headphones: Sony WH-1000XM2
Steps to Reproduce:
1. Pair headphones
2. Power off headphones
3. Turn on headphones
4. Nothing happens
5. Go to "Settings -> Bluetooth -> WH-1000XM2"
a) click on "Connection" makes switch spinning for several seconds with no result
b) click on "Connection" makes switch spinning for several seconds with no result
c) click on "Connection" connect headphones
Headphones fail to automatically reconnect. Manual reconnect takes at least 3 times of trying before succeeding.
Headphones reconnect automatically.
Manual reconnect works from the first try.
Everything works as a charm on Fedora 34 with following software versions
Sep 15 15:32:33 fedora kernel: input: WH-1000XM2 (AVRCP) as /devices/virtual/input/input32
Sep 15 15:32:33 fedora systemd-logind: Watching system buttons on /dev/input/event24 (WH-1000XM2 (AVRCP))
Sep 15 15:32:42 fedora systemd: app-gnome-gnome\x2dbluetooth\x2dpanel-4807.scope: Consumed 10.428s CPU time.
(power off headphones):
Sep 15 15:34:05 fedora gsd-media-keys: Unable to get default sink
Sep 15 15:34:05 fedora wireplumber: <WpDefaultProfile:0x55eaf7f56880> failed to get current profile on device: pipewire proxy destroyed before finishing
(turn headphones on):
(1-st click on "Connection"):
Sep 15 15:34:59 fedora bluetoothd: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 70:26:05:39:EF:7B: Host is down (112)
(2-nd click on "Connection"):
Sep 15 15:35:06 fedora bluetoothd: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 70:26:05:39:EF:7B: Host is down (112)
(3-rd click on "Connection"):
Sep 15 15:35:09 fedora kernel: input: WH-1000XM2 (AVRCP) as /devices/virtual/input/input33
Sep 15 15:35:09 fedora systemd-logind: Watching system buttons on /dev/input/event24 (WH-1000XM2 (AVRCP))
Works only after I do "systemctl --user restart pipewire".
The issue is tracked here:
Claimed to be fixed in master:
Can't test it yet.
There's a new wireplumber update now:
which should have the fix, I believe. Can you check that? Thanks!
wireplumber-0.4.3-1.fc35 fixed the issue for me, thanks!
OK, that update is pushed stable now, so we can close this.