So, I switched back to the original package:
$ apt policy pulseaudio-module-bluetooth
pulseaudio-module-bluetooth:
Installed: 1:13.99.1-1ubuntu10
Candidate: 1:13.99.1-1ubuntu10
Version table:
*** 1:13.99.1-1ubuntu10 500
500 http://pl.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
Then I deleted the device from BlueZ:
$ bluetootctl
[bluetooth]# devices
...
Device 94:DB:56:52:BC:64 WH-1000XM4
[bluetooth]# remove 94:DB:56:52:BC:64
[DEL] Device 94:DB:56:52:BC:64 WH-1000XM4
Device has been removed
Afterwards I have removed user-wide PulseAudio configuration (actually
moved it to a different location):
mv ~/.config/pulse ~/.config/pulse.b4
And restarted the OS.
Then I had to pair the headphones anew. So I did that using
bluetoothctl:
[bluetooth]# scan on
Discovery started
[bluetooth]# devices
...
Device 94:DB:56:52:BC:64 WH-1000XM4
...
[bluetooth]# pair 94:DB:56:52:BC:64
Attempting to pair with 94:DB:56:52:BC:64
[CHG] Device 94:DB:56:52:BC:64 Connected: yes
[WH-1000XM4]#
And the problem was still there :( I re-did the steps above using the
Plasma applet, but same result.
Additional note: bluetoothctl by itself is not a workaround. The thing
that helps, is restarting bluetooth.service (sudo systemctl restart
bluetooth.service). I just used bluetoothctl to illustrate my actions, I
can also connect using Plasma applet (and it works exactly the same as
bluetoothctl: they both use DBus API for Bluez). I guess Gnome Control
Center also uses DBus to contact Bluez
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891648
Title:
[0cf3:e301 Qualcomm Atheros]Cannot switch to A2DP profile w/o
restarting bluetooth.service [pulseaudio: Refused to switch profile to
a2dp_sink: Not connected]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891648/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
