SUMMARY When microphone is muted there's no notification when starting to record, like KRecorder or any other program using the microphone STEPS TO REPRODUCE 1. Connect headset or headphone 2. Launch Krecorder 3. Hit Record OBSERVED RESULT No notification warning about mic being muted EXPECTED RESULT Notification warning about mic being muted like advertised in Plasma 6.4 announcement SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Unstable branch KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18 Qt Version: 6.9.2 ADDITIONAL INFORMATION Tried other distros, like KDE Neon, Ubuntu Studio, same problem since Plasma 6.4.0
Note: the relevent MR that implemented this is https://invent.kde.org/plasma/plasma-pa/-/merge_requests/319
I tried again with Audacity and i see a OSD notification that quickly disappears, but another shows on top with the name of the device and battery left. It shows up when i start or stop recording only.
On git-master, I do see an OSD notification when starting to record in Audacity and the mic is muted. On KDE Neon Testing, I checked with KRecorder and I also saw the notification. It sounds like you are actually seeing the muted mic notification, but that it's being overlapped by another one. Can you send a screen recording, showing the bug happening?
I tried KDE neon unstable with Plasma 6.5 and it works fine too, but i tried with Manjaro KDE with Plasma 6.4.5 and it doesn't. Weird because it works fine too with KDE Neon User and Plasma 6.4.5. Don't know if it happens on Arch too.
(In reply to machaquiro from comment #4) > I tried KDE neon unstable with Plasma 6.5 and it works fine too, but i tried > with Manjaro KDE with Plasma 6.4.5 and it doesn't. > Weird because it works fine too with KDE Neon User and Plasma 6.4.5. Don't > know if it happens on Arch too. Thanks for the additional troubleshooting, that's helpful. If it's bugged in 6.4.5 but working properly in 6.5, it sounds like the bug has been fixed in 6.5. With Neon User and 6.4.5, it may be that the Neon folks have a patch applied. Lets call this fixed for now. If you can reproduce this in 6.5.0 or later, feel free to reopen this report. Thanks!