Bug 452933

Summary:	When bluetooth headset connects, the audio does not change it to default
Product:	[Unmaintained] Bluedevil	Reporter:	Cane Kostovski <trekjunky>
Component:	general	Assignee:	David Rosca <nowrep>
Status:	CLOSED DOWNSTREAM
Severity:	normal	CC:	nate, plasma-bugs-null, trekjunky
Priority:	NOR
Version First Reported In:	5.24.4
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Cane Kostovski 2022-04-24 06:36:38 UTC

SUMMARY
***
Turning on my bluetooth headset used to connect right away and change the default audio output to the headset


STEPS TO REPRODUCE
1. Turn on bluetooth headset
2. headset connects
3. Audio doesn't change default audio output to headset

OBSERVED RESULT
Using the bluetooth tray app, I can disconnect the headset and reconnect the headset and THEN it will change the default audio output to the headset

EXPECTED RESULT
as soon as I turn on my bluetooth headset, when it connects, the audio app should right away change the headset to the default audio output

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220422
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.17.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: Radeon RX 570 Series

ADDITIONAL INFORMATION

Comment 1 Nate Graham 2022-04-25 17:58:06 UTC

I believe openSUSE Tumbleweed is still using PulseAudio and has not switched to PipeWire yet. In PulseAudio, this does not happen automatically; you need to configure it that way in the Audio Volume page in System Settings. Whether to do this by default or not is a distro decision. With PipeWire, it happens automatically.

Comment 2 Cane Kostovski 2022-04-25 23:55:39 UTC

Loading repository data...
Reading installed packages...
'pipewire' is already installed.
No update candidate for 'pipewire-0.3.50-1.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.

Still have the problem

Comment 3 Cane Kostovski 2022-04-25 23:57:05 UTC

Opensuse sabotaged it. How did they do it? How can I fix it?

Comment 4 Nate Graham 2022-04-26 00:06:15 UTC

Interesting.

Anyway, all the output switching decisions take place in PipeWire, so I'm afraid there's nothing for KDE to do here. You might try opening a bug report on openSUSE's bug tracker.

Comment 5 Cane Kostovski 2022-04-26 06:37:00 UTC

Opensuse banned me from their forum forever because they refuse to fix it. I need your help. I have no where to turn to. Isn't there anything you can do?

Comment 6 Cane Kostovski 2022-04-26 06:37:59 UTC

What file was the one that caused my problem in older versions?

Comment 7 Nate Graham 2022-04-26 13:46:22 UTC

This is a bug tracker, not a user support hotline. The bug isn't in KDE software, so it has to be tracked elsewhere. I'm afraid there is nothing more I can do to help here. If you can't get help on the openSUSE forum, there is always their own bug tracker (for reporting bugs), or you could report it directly to the PipeWire devs, or you could try to get help on the r/opensuse subreddit.