You are not logged in.
Hello Arch veterans, I've been having problems with my bluetooth after I moved from Pulseaudio to PipeWire/Wireplumber.
I installed the packages "pipewire pipewire-pulse wireplumber" and enabled all on systemd, for a first moment my bluetooth was down, so I made the first option that is restarting the PC, then my bluetooth was working, but I tried to connect to my headset or my keyboard and it would be blank, after some time I received a bluez error and from this forward any bluetoothctl command just gives me the answer "No default controller available", I've tried looking on various topics but none helped me on my specific case, so I'm here as a last resort, thanks in advance.
Offline
Pipewire can't break bluetooth entirely so this is more likely a coincidence rather than the cause.
More likely a kernel/firmware bug, check/post dmesg and journal logs on a connection attempt and potentially try downgrading the kernel.
Offline
Pipewire can't break bluetooth entirely so this is more likely a coincidence rather than the cause.
More likely a kernel/firmware bug, check/post dmesg and journal logs on a connection attempt and potentially try downgrading the kernel.
Thanks for the reply, fortunately my bluetooth started working again for reasons.
I think is the first time something fix itself and doesn't destroy itself without explanation in my experience with Linux lol.
Offline
I too had Bluetooth service not working till I forcibly removed Pipewire.
Offline