Bug 500556 - Audio indicators show up despite being disabled on Task Manager Settings
Summary: Audio indicators show up despite being disabled on Task Manager Settings
Status: RESOLVED DUPLICATE of bug 499891
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (show other bugs)
Version: 6.3.1
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-21 23:38 UTC by Roguefort
Modified: 2025-02-22 06:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Icon-Only Task Manager Settings (68.91 KB, image/png)
2025-02-21 23:38 UTC, Roguefort 		Details
Audio Indicadors (18.61 KB, image/png)
2025-02-21 23:38 UTC, Roguefort 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Roguefort 2025-02-21 23:38:16 UTC 
Created attachment 178716 [details]
Icon-Only Task Manager Settings

SUMMARY
Whenever I'm running an application (being rpm. flatpak, appimage, etc.) that plays audio, the audio indicator shows up, despite having that setting disabled.

When clicking on the indicator it doesn't mute the sound coming from it.

STEPS TO REPRODUCE
1. Disable "Use audio indicators to mute tasks" setting on the icon's only task manager settings
2. Open an application that can play audio
3. Play audio

OBSERVED RESULT
The audio indicator shows up. Clicking on the application won't mute it.

EXPECTED RESULT
The audio indicator doesn't show up.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.12.15-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Comment 1 Roguefort 2025-02-21 23:38:36 UTC 
Created attachment 178717 [details]
Audio Indicadors
Comment 2 Roguefort 2025-02-21 23:41:20 UTC 
Also happens on Icons-and-Text Task Manager.
Comment 3 Antonio Rojas 2025-02-22 06:37:33 UTC 

*** This bug has been marked as a duplicate of bug 499891 ***