Hi, I have a remote output from Kodi in my network, also with pulseaudio. That makes it possible for me to manage the kodi volume right from the Plasma-pa applet. Awesome! Really :) While it is awesome to be able to do so, i don't quite use it. It just sits there. That was all just fine till Plasma 5.12. Ever since i upgraded to 5.12 the plasma-pa applet "somehow" has a deep desire to put that sink as default. Time and time again. I'm guessing it does so when it sees it, most certainly after reboots but i've had more weird sound changes where i didn't know what went wrong till i discovered this. Also, i'd like to point out that this very same issue has been teasing plasma-pa ever since it exists. In most releases it's fine, but i've had this issue before and it was fixed some releases ago. Would it be possible for this - rather important applet - to be a lot more conservative when it it changes defaults? As an example, i would _not_ change the default is something suddenly appears online on the network. It could be from any source and anyone, it should most certainly be verified if that's going to be my default output source. Not just.. change it. I would *ask* to change the default if there is a device change (like a headphone plugged in) and then do whatever i pick as the next default action for a similar change (headphone unplugged, another headphone plugged, etc..). You probably need more information but i'm not quite sure what to give. Feel free to ask if that helps the debugging and fixing process. Best regards, Mark
To add to the above. Rebooting sets the default output to my remote sink. Logging out and back in resets it to the remote sink as well. Changing it via pavucontrol and then doing one of the above has the same result (output set on remote sink)
plasma-pa does not change your preferred sink ("default") and never did. This behavior is still the same since around Plasma 5.5 release. It uses preferred sink for volume control with keyboard shortcuts and scrolling over applet icon. So in your setup you should ensure that preferred sink is always correctly set to the sink you want in pulseaudio.
Hmm. Something changed in the flow of playing audio, that's for sure. It could be pulseaudio itself or a combination of non-compatible modules... I wonder, could it be that module again that's loaded for KDE specifically that interferes with module-switch-on-connect ;) Just a thought. I'm going to debug some more to try and figure this out.
You should probably disable module-device-manager in /usr/bin/start-pulseaudio-x11
I did, unless something re-added that (which an update could have done). To be continued.
This is the only thing in KDE/Plasma that would interfere with streams routing, if you have it disabled (and not loaded) then the blame is on pulseaudio.