Created attachment 147409 [details] A picture of the media widget popup listing "microsoft teams notification" SUMMARY I *believe* this is for the right product, but it's just called "media player" in the menus, so I'm not sure. My issue is with the main media player interface (the application and the widget). Whenever I get a call via Microsoft Teams, it lists the call sound in Media Player. Now, obviously, this is the fault of incompetent Teams development, but I would love the ability to blacklist the application, so it doesn't show up. This issue affects my media keys, since when I press them, it affects whatever application has most recently played "media", which Teams apparently thinks includes it. STEPS TO REPRODUCE 1. Install the Teams aur package 2. Receive a call on Teams 3. Look at the Media Player application or widget OBSERVED RESULT Teams is listed in the widget/application. EXPECTED RESULT Teams is not listed in said widget/app, or there is an option to blacklist it (obviously the latter makes more sense from a development standpoint). SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (x11) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2
Making this configurable would certainly solve the issue, but I wonder if there's a generic way to filter out inappropriate entries like this one.
(In reply to Nate Graham from comment #1) > Making this configurable would certainly solve the issue, but I wonder if > there's a generic way to filter out inappropriate entries like this one. Maybe through length, like we do in task manager for short sounds? Calls would probably take longer, but maybe the Teams MPRIS stream has some metadata we can use to detect that. I don't use Teams, but if someone does, can they open QDBusViewer, go to the mpris interface opened by Teams, then go to org > mpris > MediaPlayer2 > org.mpris.MediaPlayer2.Player > Property Metadata, and post the output? Also possible duplicate https://bugs.kde.org/show_bug.cgi?id=429542
Yeah, let's track it as a bug report rather than a new blacklist feature. *** This bug has been marked as a duplicate of bug 429542 ***