Bug 512963

Summary: Muting the microphone via hardware also mutes via software
Product: [Plasma] plasmashell Reporter: NeKoconut <fogdace>
Component: Audio Volume widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: isma.af, kde, nate
Priority: NOR    
Version First Reported In: 6.5.3   
Target Milestone: 1.0   
Platform: CachyOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description NeKoconut 2025-12-05 01:34:03 UTC
SUMMARY
From a fresh boot, upon pressing the physical mute button on my microphone, followed by pressing the button again to unmute the device, the microphone on the software end remains muted, but on the hardware end, it is unmuted.  This can be manually resolved by clicking on the unmute button from the system settings.  The issue does not happen for the remainder of the time the computer is on, only the first time.  

STEPS TO REPRODUCE
1. Log into computer after it previously being shut down.
2. Press the physical mute button on microphone.
3. Press the button once more to unmute the microphone.

OBSERVED RESULT
The Microphone's muted status in the system settings is de-synced from the hardware's muted status.  Repeating the instructions a 2nd time or more does not appear to cause the same issue.

EXPECTED RESULT
The Microphone's muted status in the system settings should remain the same as the hardware's muted status.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
- CachyOS x86_64
- Linux 6.17.9-2-cachyos
KDE Plasma Version: KDE Plasma 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
Operating System: CachyOS Linux 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.9-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X3D 8-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3090
Microphone: Elgato Wave 3
Comment 1 Nate Graham 2025-12-09 04:08:51 UTC
This is sort of the inverse of Bug 511276, but it's got the same root cause.

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