Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Some background:
System76 Machine, made a script work-around for the brightness.
Runs the script brightness.sh up or down to increase, decrease the brightness.
The question:
Right now, I have it mapped to Alt+F8 and Alt+F9 to decrease/increase brightness.
I want to map it to Fn+F8 and Fn+F9, but the Keyboard Shortcuts Window doesn't recognize it when I press those (it just still waits for a key-combo).
EDIT 1: The following was fixed, and isn't an issue anymore:
Quote:
Fn+F8 and Fn+F9 still send the brightness change signal to the OS, so I see a window showing the brightness raised/lowered, but since that didn't work for me (System76 was clueless of the problem, I tried grub, whatever), it's useless and doesn't have any effect.
How do I get Keyboard Shortcuts to recognize Fn+F8 and Fn+F9? Or how do I setup an alternate method of keyboard shortcutting?
Again, don't respond if you are going to argue with my methods of getting brightness to work. Try to stay focused on the question at hand.
Sigh...yes...I've tried that. As I stated in the question, I'd ask you to not argue/dispute the method of brightness change.
System76 is very different from Asus.
I've tried modifying Grub many times, none of it has ever worked.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
I'm afraid I don't think you can do what you want. On my system (ASUS laptop) those key combinations aren't seen by xev at all -- the other fn+<key> ones are though making me think that what you want to do isn't going to be possible.
The keys work as they ought on my system, by the way, just letting you know for completeness.
What if I told you xev does pick up my Fn+F8 and Fn+F9 keys? They pick something up, this is the output xev when pressing Fn then F8 (brightness down) and then Fn then F9 (brightness up).
Quote:
FN+F8
MappingNotify event, serial 37, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
FocusOut event, serial 37, synthetic NO, window 0x4400001,
mode NotifyGrab, detail NotifyAncestor
FocusOut event, serial 38, synthetic NO, window 0x4400001,
mode NotifyUngrab, detail NotifyPointer
FocusIn event, serial 38, synthetic NO, window 0x4400001,
mode NotifyUngrab, detail NotifyAncestor
MappingNotify event, serial 40, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
Any way to map this combo to a script? It might not be through the default keyboard shortcuts, but that's fine.
Also, see my edits to the question. I managed (through Grub, believe it or not) to remove the brightness window that shows up when pressing the brightness up down fn keys.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
I'm not convinced that that is picking up the key combination as anything meaningful -- I may well be wrong but I read that as noticing that the screen-brightness window had been created and given focus etc. and perhaps that some system key had been used.
Contrast what you see with a real key press event:
Code:
KeyPress event, serial 39, synthetic NO, window 0x1400001,
root 0xdd, subw 0x1400002, time 1721533, (19,56), root:(613,371),
state 0x0, keycode 42 (keysym 0x67, g), same_screen YES,
XLookupString gives 1 bytes: (67) "g"
XmbLookupString gives 1 bytes: (67) "g"
XFilterEvent returns: False
KeyRelease event, serial 39, synthetic NO, window 0x1400001,
root 0xdd, subw 0x1400002, time 1721644, (19,56), root:(613,371),
state 0x0, keycode 42 (keysym 0x67, g), same_screen YES,
XLookupString gives 1 bytes: (67) "g"
XFilterEvent returns: False
True, I did see that it didn't pick any keys up. I'm going to leave this thread open a while to see if anyone else has insights about the problem. I might start-up another thread to try to get the brightness keys to work like they should instead of using a script. Right now I'm stuck using xbacklight, and I've tried a few grub changes, but they didn't help.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Sorry to have put a downer on things. Could you map it to some other combination in the mean time? For example my C and V keys have what looks like a slideshow (no idea really) and a camera button on them which didn't do anything (I now use the S button for opening a terminal in XFCE.
Yes, I have the keys currently set to Alt+F8 and Alt+F9, so it's not a humongous desperate issue, I'd just like to have the Fn combo since I use that for everything else.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.