SUMMARY If you have 100% volume and still try to increase it with either hotkey or by scrolling on volume icon in systray, it will not increase volume but it will still give visual feedback so you can see in the middleof your screen that the sound is already 100%. But this does not happen when you scroll on battery icon and already having 100% brightness (or 0%). visual feedback is only given if brightness level changed, but i think (and i hope you agree) it is better to always give visual feedback so user can see that he has 100% brightness already. By the way this does not happen when using hotkeys, `brightness up` button always gives visual feedback even on 100%, so i guess this is `battery and brightness` widget bug STEPS TO REPRODUCE 0. have a laptop, battery and brightness icon in systray, visual feedback for changing brightness enabled 1. scroll your mouse wheel up on battery and brightness icon untill you have 100% brightness 2. wait untill that visual feedback brightness level in the center of the screen disappears 3. scroll up again OBSERVED RESULT no visual feedback appear, user has to guess that he has 100% brightness already EXPECTED RESULT visual feedback appears and tells that brightness is 100% already SOFTWARE/OS VERSIONS Linux/KDE Plasma: gentoo 2.9 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.5
This is working for me with current git master on Wayland. Please re-open if you find it's not working for you on Plasma 5.27 once it's released in about a month, or if you compile it now.
Can confirm. At least on X11, scrolling down when it's on minimum, or up when it's already on maximum, gives no OSD feedback for brightness change. For Volume it always works though (both source and OSD appear).
(In reply to Nate Graham from comment #1) > This is working for me with current git master on Wayland. Please re-open if > you find it's not working for you on Plasma 5.27 once it's released in about > a month, or if you compile it now. I just downloaded kde neon, it says it has plasma 5.28.80 and x11 session. The bug is still here. I can not run wayland on my gentoo installation and it seems like there is no way to run wayland session on kde neon live usb so i'm sorry but i can not test if it is x11-only bug or something else is wrong.
Interesting, maybe it's already fixed on Wayland?
Adding the x11-only keyword