Bug 376009

Summary: Taskbar shows sound icons for all Chrome windows
Product: [Plasma] plasmashell Reporter: Christian Muehlhaeuser <muesli>
Component: Task Manager and Icons-Only Task Manager widgetsAssignee: Eike Hein <hein>
Status: RESOLVED NOT A BUG    
Severity: normal CC: fcheslack, kde, nate, plasma-bugs, qwad1000
Priority: NOR    
Version: 5.9.0   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christian Muehlhaeuser 2017-02-04 16:36:46 UTC
Taskbar shows sound icons for all Chrome windows even though there's no sound playing.
Comment 1 Kai Uwe Broulik 2017-02-04 16:51:28 UTC
Are you sure? Could it have been a brief notification sound in some messenger website perhaps? Chrome tends to keep audio streams open for way longer than they actually played.
Comment 2 fcheslack 2017-07-06 13:53:53 UTC
I also see this behaviour. Taskbar for Chrome intermittently shows audio being played when there is none. This happens for 8 seconds every minute (at the same second). There is only one Chrome window open, with one tab I know is not playing sound (a local file I control which chrome also doesn't consider to be playing sound based on it's similar tab audio icons).

This could be chrome opening audio to test that it has that capability, or playing inaudible sounds as google uses for things like chromecast pairing?
Comment 3 fcheslack 2017-07-06 13:56:14 UTC
In my case this turned out to be an extension (Signal Private Messenger) triggering it. I can trigger it (with no audible sound) by toggling the extension on and off.
Comment 4 Nate Graham 2017-12-13 20:58:26 UTC
So is there anything we can do here? If not, we should unfortunately mark it as RESOLVED UPSTREAM; no sense in keeping an unfixable bug open forever. :/
Comment 5 Nate Graham 2017-12-13 21:01:31 UTC
Oops, that comment went to this bug by accident. Either way, it sounds like this is caused by misbehaving Chrome extensions; not much we can do there. You should report the issue to those extensions' developers.
Comment 6 Nate Graham 2017-12-13 21:18:30 UTC
*** Bug 377787 has been marked as a duplicate of this bug. ***