[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=399487 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=396799 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 --- Comment #6 from David Rosca --- > Upstream says we shouldn't be using gconf in the first place: gconf is not to blame here, ubuntu is. Alternative to pulseaudio gconf module, as suggested, is to effectively reimplement what it is doing (eg. manually track loaded modules and load/unload what we want on each pulseaudio startup). It may be necessary in future, but right now we can still use gconf. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 --- Comment #5 from David Edmundson --- Two lines later > but no such API exists at the moment (apart from GConf) We're limited into using things that exist. If pulseuadio add an alternative, I'd happily do the port -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 --- Comment #4 from Nate Graham --- Upstream says we shouldn't be using gconf in the first place: https://bugs.freedesktop.org/show_bug.cgi?id=95104#c11 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 --- Comment #3 from David Rosca --- Also this is an issue that comes from distribution-specific patch, it should be fixed there. module-switch-on-connect is not enabled by default upstream for a reason. If it ever becomes enabled by default, then I assume it will be either only for non-KDE session or module-device-manager won't be loaded in KDE session anymore. Certainly not the way it was done by Ubuntu patch. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 David Edmundson changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Edmundson --- I rechecked the code, we don't load the module directly. We update gconf, which we know pulseaudio has a module to follow, which in turn loads the module. I don't think there's any way we can avoid the double load at our level. Sorry -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- >Likely for this reason, plasma-pa has the checkbox unchecked by default That isn't the reason. I know because I wrote the switch on connect UI. It is not a better setting, merely a different one.. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=392103 -- You are receiving this mail because: You are watching all bug changes.
