[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 |

[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

[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 |

[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

[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 --

[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

[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

[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|

[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