https://bugs.kde.org/show_bug.cgi?id=375943
--- Comment #10 from Dragan <d.milivoje...@gmail.com> --- (In reply to Nate Graham from comment #9) > Actually perhaps not. As Kai said: > > "All sound playback "belongs" to the main Chrome process. PulseAudio in > theory supports applications adding a Window ID to the audio stream but in > practise I've never seen anybody actually use this." > > If Firefox does the same thing, then they would both just be broken in the > same way. I remember that this issue started to show up after a kde update. It's unlikely that both firefox and chrome were updated at the same time. I will try and dig up some older fedora kde live image and test it there with the latest firefox. -- You are receiving this mail because: You are watching all bug changes.
