Bug 508919 - Sound doesn't work with JBL Flip 6 speaker until audio profile is changed
Summary: Sound doesn't work with JBL Flip 6 speaker until audio profile is changed
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Bluetooth widget (other bugs)
Version First Reported In: 6.4.4
Platform: EndeavourOS Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-30 05:35 UTC by ibuiltasonic+bugskde
Modified: 2025-09-17 18:12 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ibuiltasonic+bugskde 2025-08-30 05:35:21 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
When connecting to my JBL Flip 6 speaker via bluetooth, sound doesn't come out of the device until I switch the audio profile. It doesn't matter what profile it starts on (Codec SBC or Codec SBC-XQ). It initially does not work until I switch the profile to the one it didn't start on.

STEPS TO REPRODUCE
1. Turn on speaker
2. Pair with computer and select speaker as audio out
3. Audio does not come out
4. Right click on widget, mouse over "Audio Profiles for <speaker name>", select whatever it's not on currently
5. Sound works

OBSERVED RESULT
Sound does not work after pairing until audio profile is switched 

EXPECTED RESULT
Sound works immediately upon pairing and selecting speaker as audio device

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.16.3-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
None
Comment 1 Nate Graham 2025-09-17 18:12:19 UTC
This is an issue somewhere in the Bluetooth or audio stack. I'd recommend contacting your distro about it.