Bug 499605

I apologise for raising this bug in a wrong format. 

STEPS TO REPRODUCE
    Connect a Bluetooth device (e.g., headphones or speaker).
    Select the LDAC profile and play media in Firefox (sound is output correctly).
    Switch to the mSBC profile (sound is still output correctly).
    Switch back to the LDAC profile (video is playing, but there is no sound).
    Switch to the mSBC profile again (sound is output correctly).
    Switch back to the ACC profile (video is playing, but there is no sound).
    Switch to the mSBC profile again (sound is output correctly).
    Set the LDAC profile again (no sound). Disconnect the Bluetooth device, reconnect, and select the LDAC profile (sound is output correctly).
    If the profile is changed and then set back to LDAC or other profile that's not mSBC, the issue persists: no sound output, and the following 

EXPECTED RESULT
Expecting when I switch the profiles I would have a sound. 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Operating System: openSUSE Tumbleweed 20250130
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.13.0-1-default (64-bit)
Graphics Platform: Wayland
Processors: 32 × 13th Gen Intel® Core™ i9-13900HX
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics

ADDITIONAL INFORMATION
    The issue is observed with both PipeWire and PulseAudio backends in KDE.
    Uninstalling PipeWire and using PulseAudio with KDE’s two available profiles still results in no sound after switching to LDAC.
    I am using wayland with KDE6 in case it makes a difference.
    I am using Sony headphones.

I tested this with Sony earbuds that support LDAC using the reproduction steps.
I'm unable to reproduce the bug on Plasma 6.2.5 or git-master. Both are using the pipewire backend. I heard sound no matter which codec I used (except CVSD which the hardware does not support). LDAC produced sound no matter how many times I switched away from and back to it

I did notice that after switching from mSBC to AAC, the mute button was automatically activated. I heard sound after unmuting the channel. Does the mute button show the output being muted when you hear no sound?

Also, the pastebin paste is no longer available. Can you attach that to the bug report itself as a text file? Thanks.

I managed to reproduce the issue. It’s the same as I previously reported—no matter which profile I choose (except mSBC), there is no sound.
Hi,

I have created new log files. From the logs, it seems that the system cannot find the device, even though the device is connected. 

Here is the new Pastebin link: https://pastebin.com/g3FNXK9q

I’m not sure if this is accurate, but someone mentioned earlier on the openSUSE subreddit that he is encountering the same issue, and he believes it is related to the PulseAudio version. He reverted the PulseAudio version to an older one.

Since I am using PipeWire, my pipewire-pulseaudio version is 1.2.7-1.4.

Are you using PulseAudio or PipeWire? What versions of these packages do you have? Are you running openSUSE Tumbleweed like me, or a different distro?

Thank you for your time.

I saw you said you are using pipewire. And I forgot to say that when i change profile the sound is not off.

Thanks for providing the logs. I'll let a maintainer more familiar with pulseaudio take it from here. 

Copying the paste here for better searchability, and so it doesn't expire

Feb 07 20:12:25 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:25 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:25 tuxedo01 bluetoothd[1523]: /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep5/fd0: fd(43) ready
Feb 07 20:12:30 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:30 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:30 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:33 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:33 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:34 tuxedo01 bluetoothd[1523]: /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep1/fd1: fd(43) ready
Feb 07 20:12:40 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:40 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:40 tuxedo01 bluetoothd[1523]: /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep1/fd2: fd(43) ready
Feb 07 20:12:44 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:44 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:44 tuxedo01 bluetoothd[1523]: /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep2/fd3: fd(43) ready
Feb 07 20:12:48 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:48 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:48 tuxedo01 bluetoothd[1523]: /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep5/fd4: fd(43) ready
Feb 07 20:12:51 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:12:51 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:23 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:23 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:23 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:26 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:26 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:28 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:28 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:30 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"
Feb 07 20:13:30 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object for name "bluez_output.10_4F_A8_DA_C2_E0.1"

Created attachment 178136 [details]
My setup

I can confirm the issue exists and I can reproduce it every day.
By default my sony xm3 only connects in headset mode. If I switch to any high quality profile there is no sound.

Temporary workaround:
Remove the bluetooth device and re-pair it. This case the high quality audio will be available and will work.

(In reply to TraceyC from comment #5)
> Thanks for providing the logs. I'll let a maintainer more familiar with
> pulseaudio take it from here. 
> 
> Copying the paste here for better searchability, and so it doesn't expire
> 
> Feb 07 20:12:25 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:25 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:25 tuxedo01 bluetoothd[1523]:
> /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep5/fd0: fd(43) ready
> Feb 07 20:12:30 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:30 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:30 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:33 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:33 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:34 tuxedo01 bluetoothd[1523]:
> /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep1/fd1: fd(43) ready
> Feb 07 20:12:40 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:40 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:40 tuxedo01 bluetoothd[1523]:
> /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep1/fd2: fd(43) ready
> Feb 07 20:12:44 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:44 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:44 tuxedo01 bluetoothd[1523]:
> /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep2/fd3: fd(43) ready
> Feb 07 20:12:48 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:48 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:48 tuxedo01 bluetoothd[1523]:
> /org/bluez/hci0/dev_10_4F_A8_DA_C2_E0/sep5/fd4: fd(43) ready
> Feb 07 20:12:51 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:12:51 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:23 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:23 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:23 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:26 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:26 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:28 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:28 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:30 tuxedo01 kded6[5461]: org.kde.pulseaudio: No object for name
> "bluez_output.10_4F_A8_DA_C2_E0.1"
> Feb 07 20:13:30 tuxedo01 plasmashell[5551]: org.kde.pulseaudio: No object
> for name "bluez_output.10_4F_A8_DA_C2_E0.1"

Thank you for your help.

(In reply to dansity from comment #6)
> Created attachment 178136 [details]
> My setup
> 
> I can confirm the issue exists and I can reproduce it every day.
> By default my sony xm3 only connects in headset mode. If I switch to any
> high quality profile there is no sound.
> 
> Temporary workaround:
> Remove the bluetooth device and re-pair it. This case the high quality audio
> will be available and will work.

Unfortunately the workaround is not working reliably and the device goes back to headset. Waiting for a fix.

This can't be a Plasma bug as we don't actually control the playback of audio; everything is delegated to the PulseAudio/PipeWire/Wireplumber libraries. So this would be something you need to report either upstream, or to your distro, so they can sort it out.

FWIW, we've been getting a lot of similar bug reports lately, so I do think it's likely something changed in the audio stack recently. It's not anything we have control over, though.

Thank you for your response. I will try reporting to the pipewire devs. 

Sent from Proton Mail Android


-------- Original Message --------
On 19/02/2025 15:36, Nate Graham <bugzilla_noreply@kde.org> wrote:

>  https://bugs.kde.org/show_bug.cgi?id=499605
>  
>  Nate Graham <nate@kde.org> changed:
>  
>             What    |Removed                     |Added
>  ----------------------------------------------------------------------------
>                   CC|                            |nate@kde.org
>               Status|REPORTED                    |RESOLVED
>           Resolution|---                         |UPSTREAM
>  
>  --- Comment #9 from Nate Graham <nate@kde.org> ---
>  This can't be a Plasma bug as we don't actually control the playback of audio;
>  everything is delegated to the PulseAudio/PipeWire/Wireplumber libraries. So
>  this would be something you need to report either upstream, or to your distro,
>  so they can sort it out.
>  
>  FWIW, we've been getting a lot of similar bug reports lately, so I do think
>  it's likely something changed in the audio stack recently. It's not anything we
>  have control over, though.
>  
>  --
>  You are receiving this mail because:
>  You reported the bug.

For me the issue was with the microphone. Something I cannot exactly tell have changed with the way the default microphone is selected and the High Quality options were not available as the microphone of the headset was always on. Any time you interact with the volume panel or something the microphone is probed to show the levels hence the option to switch to a high quality output is not available.
I have plug in a jack into my mic outlet on the motherboard and now it thinks I always have a mic. I made that microphone a default and after a reboot now I'm able to use the LDAC driver as before.

Someone with a bit of deeper knowledge can tell maybe why it was not happening before and why it is happening after upgrading to 6.3