Bug 488296

Summary: Pairing bluetooth speaker triggers constant reconnecting and bluetooth profile switching
Product: [Unmaintained] Bluedevil Reporter: MK <michele.kipiel>
Component: daemonAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 6.0.5   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description MK 2024-06-10 10:58:42 UTC 
SUMMARY
When I pair my bluetooth speaker (JBL Charge 3) the following loop is triggered: first it connects as a high quality audio device (a2dp profile) then it disconnects (back to in-built analog audio), then it connects as a low quality audio device (HSP profile), and again. The loop goes on forever, switching audio output every couple seconds.

The speaker worked perfectly before the latest update.

STEPS TO REPRODUCE
1.  Be on plasma 6.0.5
2. Pair a bluetooth speaker 

OBSERVED RESULT
Endless loop in which the bluetooth speaker connection goes up and down

EXPECTED RESULT
Bluetooth speaker is connected at once and a2dp audio sink works

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240607
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520

ADDITIONAL INFORMATION
This worked flawlessly prior to the latest update.
Comment 1 Nate Graham 2024-06-10 17:00:03 UTC 
Were any non-KDE packages updated too? This kind of behavior change is typically caused by a regression in the bluetooth stack beneath Plasma.
Comment 2 MK 2024-06-18 13:32:47 UTC 
(In reply to Nate Graham from comment #1)
> Were any non-KDE packages updated too? This kind of behavior change is
> typically caused by a regression in the bluetooth stack beneath Plasma.

Might very well be, are you aware of any specific packages/versions I should be wary of?
Comment 3 Nate Graham 2024-06-19 15:20:23 UTC 
The kernel, bluez, potentially also pulseaudio or pipewire.
Comment 4 Bug Janitor Service 2024-07-04 03:47:28 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 MK 2024-07-04 07:05:46 UTC 
The problem appears to be fixed after the latest updates