Bug 392388

Summary: Audio output devices are no longer detected
Product: [Frameworks and Libraries] Phonon Reporter: tobias.kuendig
Component: generalAssignee: Harald Sitter <sitter>
Status: RESOLVED WORKSFORME    
Severity: normal CC: myriam, romain.perier
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: 4.8   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description tobias.kuendig 2018-03-27 05:45:06 UTC 
I am running the latest version of KDE Neon. After installing updates yesterday and restarting my computer I no longer see any audio output devices in my system settings.

A pulse devices is listed but I cannot play any sounds over it.

I even connected a pair of bluetooth headphones but they don't work any longer and are not listed under the audio settings.

See here for a list of screenshots: https://imgur.com/a/6XdjB

Running `rm -rf .config/pulse && pulseaudio -k` makes a `Pulseaudio Server` available in the settings screen and lets me play music via internal speakers. I still am unable to connect my bluetooth headphones. I can see the following message in syslog:


Mar 27 07:42:28 dell bluetoothd[1221]: a2dp-sink profile connect failed for 10:4F:A8:7E:2C:AD: Protocol not available
Comment 1 tobias.kuendig 2018-03-27 05:52:56 UTC 
Somehow `pulseaudio-module-bluetooth` was missing on my system. After installing it I was able to connect my bluetooth headphones. 

Unfortunately I can only play using the HSP/HFP profile (which sounds very bad). When selecting A2DP via the Phonon Audio settings dialog nothing happens.

Using a manual call to `pactl set-card-profile bluez_card.10_4F_A8_7E_2C_AD a2dp_sink` fails with status: 1
Comment 2 tobias.kuendig 2018-03-29 05:17:00 UTC 
After uncommenting the following line in my /etc/pulse/default.pa everyhting went back to normal:

load-module module-role-cork
Comment 3 Justin Zobel 2022-11-18 04:30:24 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-03 05:18:05 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 Bug Janitor Service 2022-12-18 05:16:06 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!