Bug 428757

Summary: Microphone tray applet's mute toggle function doesn't always mute the selected microphones; consider making it mute ALL microphones
Product: [Plasma] plasmashell Reporter: Daniel <daniel-other+kdebug>
Component: Microphone Indicator widgetAssignee: Kai Uwe Broulik <kde>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: andrea.ippo, nate, oded, plasma-bugs, postix, supgesu, voidpointertonull+bugskdeorg
Priority: NOR    
Version First Reported In: 5.20.2   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=435142
https://bugs.kde.org/show_bug.cgi?id=428778
https://bugs.kde.org/show_bug.cgi?id=465301
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: wrong device volume is updated
wrong device volume is updated (now h264 video)

Description Daniel 2020-11-06 14:03:54 UTC
SUMMARY
In certain circumstances, the microphone tray applet isn't toggling the selected device.

STEPS TO REPRODUCE
1. Plugin in a headset with a microphone, have a application requesting the mic running
2. Select the device which was already there before as the sound source.
3. Middle click on the microphone tray applet to toggle mute.

OBSERVED RESULT
The new device's sound is toggled, despite the other one beeing selected as the sound source. See the video for demonstration.

EXPECTED RESULT
The currently selected microphone device should be toggled.
Comment 1 Daniel 2020-11-06 14:06:16 UTC
Created attachment 133085 [details]
wrong device volume is updated
Comment 2 Nate Graham 2020-11-06 18:08:51 UTC
I have had this happen a few times. I think it might be better to just have the mute action mute everything, not just the selected device.
Comment 3 Nate Graham 2021-03-31 21:03:41 UTC

*** This bug has been marked as a duplicate of bug 435142 ***
Comment 4 Daniel 2021-03-31 21:26:40 UTC
Created attachment 137214 [details]
wrong device volume is updated (now h264 video)

I've noticed the video was encoded with h265, which browser sadly don't support yet, so i've uploaded it with h264.

Also, I just reconfirmed the bug with Plasma 5.21.3

Also, I want to point out, that it is not exactly a duplicate, since #435142 is about changing the default mic only, while this bug is about the issue that (under certain circumstances) the current default mic is **not** toggled. However, both would be resolved if the toggle-option would just toggle all mics, wether they are the default or not, that's why you marked them as duplicate, @Nate isn't it?
Comment 5 Nate Graham 2021-04-01 17:37:35 UTC
Oh, you're right. So sorry!
Comment 6 Oded Arbel 2021-12-12 19:54:26 UTC
I can't reproduce with current neon unstable - with 3 microphones connected, left clicking or middle clicking the microphone icon in the system tray setting will mute/unmute all microphones.
Comment 7 Andrea Ippolito 2024-06-06 09:19:29 UTC
Hello,

I managed to reproduce this issue when connecting a pair of Bluetooth earbuds.

https://youtu.be/SWWRHmtfQLI

The mic is probably still muted (to be confirmed), but the applet is not reflecting this.

The applet is in sync with the actual volume value only when the main output and input devices are available, as soon as I connect the earbuds somethings gets messed up.

As you can see from the video, the "Audio Devices" widget correctly shows the mute/unmute state. But the mic widget does not.

In my video I'm toggling mic off/on with Meta+volume mute (which is Fn + F3 on my keyboard)
Comment 8 Andrea Ippolito 2024-06-06 09:21:26 UTC
(In reply to Andrea Ippolito from comment #7)
 
> As you can see from the video, the "Audio Devices" widget correctly shows
> the mute/unmute state. But the mic widget does not.

although it does show a slight decrease in volume, for whatever reason...

It's very confusing and makes me not use this feature at all because I'm always worried that my mic might not be actually muted.
Comment 9 Pedro V 2024-09-29 15:40:07 UTC
(In reply to Andrea Ippolito from comment #7)
> I managed to reproduce this issue when connecting a pair of Bluetooth
> earbuds.
> 
> https://youtu.be/SWWRHmtfQLI

Aside from hitting bug 489083 , it's really odd to see the issue happening with a single audio source which may not be even the originally described bug.

(In reply to Andrea Ippolito from comment #7)
> In my video I'm toggling mic off/on with Meta+volume mute (which is Fn + F3
> on my keyboard)

Beware, that's covered by bug 435142 , the shortcut and the applet work differently!


(In reply to Andrea Ippolito from comment #8)
> It's very confusing and makes me not use this feature at all because I'm
> always worried that my mic might not be actually muted.

It's definitely a concern, especially as I've seen the tray icon no longer following changes after high system load, even though the popup still confirmed toggles. It's been a while though since I've seen that, not sure if it can still happen.

But even though I'd also like to use it as a kind of security feature, it really isn't one:
- Monitoring just the default audio source inherently makes the indication vulnerable to changes. No need for malicious intentions, EasyEffects source becoming the default audio source already defeats the whole idea of using the indicator to figure if programs can record the microphone.
- Completely outside of its scope, but apparently muting isn't really guaranteed to work. Used EasyEffects a bit, but effectively couldn't mute it, even though pactl also confirmed the mute status being set properly. That was quite a killer combination with the indicator only focusing on the default device which was the mute immune EasyEffects source.
- Programs can unmute the microphone. Sure, well-behaved programs are not expected to do so, but for example some multiplayer games are well-known to like to fiddle with microphone settings, and them also happening to be fullscreen most of the time can perfectly hide status changes.
Comment 10 Nate Graham 2025-08-04 14:28:47 UTC
Bug 435142 is being fixed soon, and this will be effectively fixed as well by the approach taken there. Marking it as a duplicate.

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