You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've used KDE and Gnome for a while before switching to Budgie and both desktop environments had Fn key hotkeys implemented properly. Fn+F1 mutes audio, Fn+F2 lowers volume, Fn+F3 raises volume, Fn+F5 lowers screen brightness and so on. xev shows these actions as XF86MonBrightnessDown, XF86AudioMute, etc. There was also an overlay window that shows when you perform those actions.
On Budgie this is completely missing. I also tried binding these in the control center but there's no entry for changing screen brightness, and the Fn key itself is recognized rather than the full combination so I wasn't able to.
I also took a quick look and this also seems to mean I have no way to change screen brightness from the DE. If it's not in power settings, where is it?
Proposal
No response
References
No response
The text was updated successfully, but these errors were encountered:
serebit
transferred this issue from BuddiesOfBudgie/budgie-desktop
Oct 15, 2023
Budgie version
10.8.1
Use-cases
I've used KDE and Gnome for a while before switching to Budgie and both desktop environments had Fn key hotkeys implemented properly. Fn+F1 mutes audio, Fn+F2 lowers volume, Fn+F3 raises volume, Fn+F5 lowers screen brightness and so on.
xev
shows these actions as XF86MonBrightnessDown, XF86AudioMute, etc. There was also an overlay window that shows when you perform those actions.On Budgie this is completely missing. I also tried binding these in the control center but there's no entry for changing screen brightness, and the Fn key itself is recognized rather than the full combination so I wasn't able to.
I also took a quick look and this also seems to mean I have no way to change screen brightness from the DE. If it's not in power settings, where is it?
Proposal
No response
References
No response
The text was updated successfully, but these errors were encountered: