On 27/12/2020 20:07, Luya Tshimbalanga wrote:
On 2020-12-21 3:31 a.m., Tom Hughes via devel wrote:
> On 20/11/2020 16:26, Ben Cotton wrote:
>> - bluetooth devices, connect as usual and verify working behaviour
>> with PipeWire. Check volume changes etc.
> I was unable to get this to work.
Works with Galaxy Buds+ as highlighted below:
I was trying it with Bose QC35 headphones.
> The first problem is that bluetooth is not actually enabled
> by default so you have to edit /etc/pipewire/pipewire.conf and
> tell it to add "-e bluez5" when starting the session manager.
Which version of pipewire was used on your system? Pipewire 0.3.18
enabled a bluetooth headphone i.e. Galaxy Buds+ with issue related to
resuming for the reopened lid of a laptop. Workaround is with the
command for terminal "systemctl --user restart pipewire.service
pipewire-pulse.service". See attached pipewire.conf with include bleuz5
enabled by default.
It was 0.3.18 and as I say it was showing up as a device but
with no node that I could route audio to.
That configuration you attached still seems to be missing the
extra "-e bluez5" on the pipewire-media-session line? or is the
comment there wrong when it says that is required?
> The final straw though was that fast user switching seems to
> completely break it. I assume that the daemon doesn't release
> the audio device when you switch to a different desktop to
> something because once I started a second session things got
> horribly confused and I wound up with one desktop where audio
> worked and one where it didn't work at all.
No issue on my desktop running Rawhide. Maybe some issues are user error
like using old version of pipewire. Update your system and make sure
pipewire version is 0.3.18 whose pipewire-pulseaudio properly handle
dependencies. Should you see Steam from RPM Fusion being removed, grab
the latest version from their Koji page which fixes the problem.
I don't use steam so it's nothing to do with that.
Tom Hughes (tom(a)compton.nu)