I'm trying to centralize the conversation here rather than in a bunch of disjointed bug reports, because I feel like that's made it difficult to discuss the issue.
If enabling source switching in plasma-pa disables the device-manager module to prevent module conflicts and in the process breaks functionality the Phonon KCM, isn't that the bug that needs solving? Having two KCMs that use different PulseAudio modules that conflict with one another such that we can have either automatic source switching, or a fully-functional Phonon KCM--but not both--seems like a bug to me. Nate ---- On Wed, 21 Mar 2018 09:16:14 -0700 David Edmundson<k...@davidedmundson.co.uk> wrote ---- > You're not going to get a different answer here to the comments David and I > have already left on bugzilla. > > > > > I don't understand what you think the problem is. > > > > >...But both modules can't be loaded at once. > > Not technically true, but they would interfere with each other. > > > > But in any case plasma-pa disables device-manager when we enable switch on > connect. > > > > >So plasma-pa's "Automatically switch all running streams when a new output > >becomes available" checkbox does not work in many circumstances. > > > > That's not what any of your links are about, also it doesn't make sense as > described because we disable device-manager when we enable > switch-on-connect. See ModuleManager::setSwitchOnConnect. > > > > > David > > > > > > > > > >
