SUMMARY I checked "Raise maximum volume" in System Settings. Since a recent update, it doesn't work anymore to increase the volume to above 100% (and keep it there). STEPS TO REPRODUCE 1. Press Fn key to raise volume (5% increment). 2. Volume is raised to 95%, 100%, 105%. 3. On next Fn key press, it goes back to 100% and not to 110%. Also: 1. Hover mouse over sound icon in System Tray and scroll to adjust volume. Audio similarly goes 100%, 105%, 100%, 105%, 100%, ... 2. Open Audio Volume in System Tray and click on high volume, e.g., 140%. Volume stays at set volume. Press any volume Fn key (increase/decrease) -> volume goes to 100%. OBSERVED RESULT Cannot consistently increase volume to something between 100% and 150%. EXPECTED RESULT Audio volume should continue to increase in 5% steps even above 100% if "Raise maximum volume" is checked. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.10-arch1-1 (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION
I'm not able to reproduce this on Plasma built from git-master, or on Fedora 42 with Plasma 6.4.5 Pressing the Fn volume key allows me to raise volume to 95%, 100%, 105%, 110%, etc up to 150%. Similarly, I can raise volume to 150% via middle mouse scroll over the audio widget, or by opening the audio widget and using the slider. The only thing different in versions between Fedora 42 and your system is the kernel. Fedora has 6.16.9-200 Are you able to reproduce this with a brand new user?
Yes, I can reproduce this with another, new user. I created a new standard user via System Settings and I experience the same issue.
Well, that's odd. Thanks for confirming. I'll leave this open so others can try to reproduce.
Cannot reproduce either.
Me neither. Have you by any chance changed any PulseAudio or Pipewire settings? Maybe you used EasyEffects to change your audio stuff and added a limiter or other filter?
Not sure anymore. Could be that I changed some pulseaudio/pipewire settings few years ago, but this bug just appeared recently. Anyway, if you all cannot reproduce, I maybe just messed up my local packages/settings somehow. Feel free to close.