| Summary: | Muting one Electron app via the sound icon on an app's icon will mute multiple others | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Alexander Sanderson <1gsiqkbz> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | nate, qydwhotmail, sitter |
| Priority: | NOR | ||
| Version: | 6.2.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=489243 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screencap demonstration of the bug on the icons-only task manager | ||
Sounds like these apps may not set suitable hints for us to differentiate them. May well need fixing in the apps. |
Created attachment 176966 [details] Screencap demonstration of the bug on the icons-only task manager SUMMARY If you use the task manager to mute an Electron application, its audio settings seem to be shared between other electron apps, because it will mute others. It doesn't apply to all Electron apps, for instance, Discord is unaffected. But apps like FreeTube, Signal, and Chromium itself are affected. STEPS TO REPRODUCE 1. Open Chromium, FreeTube, and/or Signal, IntelliJ, etc. 2. Play sound in one of these apps 3. Mute an app that isn't playing sound OBSERVED RESULT The app that was playing sound is now muted EXPECTED RESULT The app that was playing sound should not be muted because you muted a different app SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20241226 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 Kernel Version: 6.12.6-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Iris® Xe Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A4 ADDITIONAL INFORMATION It seems this is much less likely to happen if the applications aren't Flatpaks. Interestingly though, if you have a Chromium Flatpak and an Electron-based NON-Flatpak app (e.g. a portable binary or an Appimage) open together, the issue still occurs, although other Electron Flatpaks seem unaffected when this is done.