Force logout when connecting bluetooth headset after setting handsfree as input device

Hi, I just started using EndeavourOS and tried to connect my Galaxy Buds 3 Pro via bluetooth.

Right after connecting it, there was no problem. I could run audio outut device test and it worked perfectly. But changing audio input device to handsfree variant(there was two input devices from buds, as I recall), I got logged out and also GNOME extensions turned off.

After it happened, I get logged out every time I try to connect buds.

Is this a expected behavior of invalid device setting? (i.e. using headphone audio output and handsfree audio input at the same time, I guess)
If so, how can I stop this force logout and use buds for at least output device?

If it helps, when I connect this buds to a Windows 11 desktop and open VoiceMeeter virtual sound mixer, I see this device as:
Input Device:
WDM (WASAPI): Buds3 Pro (16000 Hz, 1 Ch)
KS (Kernel Streaming):
MME (Multimedia): Buds3 Pro Hands-Free (16000 Hz, 1 Ch)
Output Device:
WDM (WASAPI): Buds3 Pro (48000 Hz, 2 Ch)
KS (Kernel Streaming): Buds3 Pro (48000 Hz, 2 Ch), Buds3 Pro Hands-Free (16000 Hz,1 Ch)
MME (Multimedia): Buds3 Pro (48000 Hz, 2 Ch)

Hi there!!! I reported this about a week ago…there is a bug with the current version of wireplumber…the current “fix” for Gnome users is to downgrade to wireplumber & libwireplumber version 15.2.

Look at my thread for more info: Crash with Bluetooth headphones after Wireplumber 5.13-1 update

You will need to install downgrade & then do both packages:

sudo downgrade wireplumber libwireplumber

then select version 15.2–make sure to “lock” both packages when asked. Then keep an eye in the thread of mine for when it is “safe” to upgrade. Upstream knows about the problem (only with Gnome) & a fix is in the pipeline.

By the way….Welcome to the forums…you will find we are a nice bunch…..

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.