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
Hi,
Great software!
I found an issue with a Lenovo laptop keyboard, which may be worth documenting in the readme, or maybe fixing if possible.
I wanted to set the XF86Audio* hotkeys (Fn + F1 for mute, Fn + F2 to volume down, Fn + F3 for volume up). However in every case it selected XF86WakeUp. I did a search and it seems to be related to Lenovo keyboards, Fn key is mapped to this. I looked at ~/.config/pnmixer/config and searched for the numeric representation of these XF86* keys. The first link I found was here: https://askubuntu.com/questions/1048771/how-to-remap-swap-function-and-control-keys . Based on this I could manually configure the proper XF86Audio* hotkeys ~/.config/pnmixer/config and it works fine. Maybe these could be the default settings.
VolMuteKey=121
VolUpKey=123
VolDownKey=122
Maybe it would be possible that until some hotkey is kept pressed it does not immediately accepts that, but only when it is released. Maybe it is already so... I am not sure if it would fix this problem.
The text was updated successfully, but these errors were encountered:
Hi,
Great software!
I found an issue with a Lenovo laptop keyboard, which may be worth documenting in the readme, or maybe fixing if possible.
I wanted to set the XF86Audio* hotkeys (Fn + F1 for mute, Fn + F2 to volume down, Fn + F3 for volume up). However in every case it selected XF86WakeUp. I did a search and it seems to be related to Lenovo keyboards, Fn key is mapped to this. I looked at ~/.config/pnmixer/config and searched for the numeric representation of these XF86* keys. The first link I found was here: https://askubuntu.com/questions/1048771/how-to-remap-swap-function-and-control-keys . Based on this I could manually configure the proper XF86Audio* hotkeys ~/.config/pnmixer/config and it works fine. Maybe these could be the default settings.
Maybe it would be possible that until some hotkey is kept pressed it does not immediately accepts that, but only when it is released. Maybe it is already so... I am not sure if it would fix this problem.
The text was updated successfully, but these errors were encountered: