Bug 438604

Summary:	removing HDMI audio results in disappearing audio device
Product:	[Applications] systemsettings	Reporter:	r.kunschke
Component:	kcm_pulseaudio	Assignee:	David Rosca <nowrep>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	nate, nicolas.fella, plasma-bugs-null, r.kunschke
Priority:	NOR
Version First Reported In:	5.22.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description r.kunschke 2021-06-14 09:53:15 UTC

I use a notebook with an "build-in audio" device. The internal speakers use a profile "analog stereo duplex". When I plug a HDMI device more HDMI profiles appearing. 
So far everything is okay. 
When I unplug the HDMI cable the "build in audio" device disappears from the audio-settings menu. It is deactivated now and I have to re-enable it from the "configure" menu by selecting another Profile.
plasma should select profiles automatically cause this behavior is very confusing. For the user it looks like his audio device is just disappeared.
The second problem appears if the notebook is entering sleep mode while removing the HDMI cable because the lid is closed in this moment. Than and sometimes even without doing this, audio profiles disappearing randomly. (this might be an problem with pipewire maybe?) I am not able to get any audio output in this case before i restart the system.


SOFTWARE/OS VERSIONS
Arch Linux with latest git-version of KDE
KDE 5.22 shows the same behavior

pipewire as pulseaudio replacement

Comment 1 Nate Graham 2021-06-15 14:47:57 UTC

This is a PipeWire bug; please report upstream. It bugs me too. :)

Comment 2 r.kunschke 2021-06-15 15:30:09 UTC

I think I found two issues reporting this behavior in a slightly different way. B
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1303
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1038

Comment 3 Nicolas Fella 2021-06-16 22:23:56 UTC

heh, I just filed https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1316

Comment 4 Nicolas Fella 2022-01-22 13:50:48 UTC

Please report this to Pipewire. Plasma is not involved in determining where audio should play, except for the case where the user explicitly moves a stream. But even then it should be PipeWire's responsibility to ensure that the stream is switched away once the device becomes unavailable

Comment 5 Nicolas Fella 2022-01-22 13:51:26 UTC

(In reply to Nicolas Fella from comment #4)
> Please report this to Pipewire. Plasma is not involved in determining where
> audio should play, except for the case where the user explicitly moves a
> stream. But even then it should be PipeWire's responsibility to ensure that
> the stream is switched away once the device becomes unavailable

Oops, that comment was meant for another report