https://bugs.kde.org/show_bug.cgi?id=465301
--- Comment #12 from Prajna Sariputra <putr...@gmail.com> --- Okay, it looks like KMix itself didn't have anything to do with it, the issue actually came back later on after a reboot or two and stayed, so I guess my fiddling with KMix and the issue fixing itself earlier today is just coincidence. I happen to have a second user account that is mostly untouched that I use for testing purposes, and so far the indicator has worked there after 6 cycles of rebooting, logging straight in to that account, starting Audacity and then using the record function (3 with KMix and 3 without). So, the only other thing that's different audio wise between the two accounts (that I can think of) other than KMix being on by default in the testing account is that I have EasyEffects set up on my main account, so I disabled its autostart function and did 3 cycles of what I did with the other account (rebooting, logging straight in to that account, starting Audacity and then using the record function) and in all 3 the issue was gone. Then, I reenabled EasyEffects' autostart and ended up going through the testing cycle like 8x, and infuriatingly the issue disappeared somehow in 2 of those cycles, and in the others the indicator was inconsistent as it usually is. Also, so far killing EasyEffects with `pkill easyeffects` appears to fix the indicator, and starting it again does not make the issue disappear. The most infuriating part of all this however is that my Fedora install also has EasyEffects running on startup, so idk what's going on anymore (some race condition on boot???). TL;DR: Try killing EasyEffects if you have it running? -- You are receiving this mail because: You are watching all bug changes.
