You are not logged in.
Pages: 1
This is my .xbindkeysrc
"amixer sset Master 2+ &"
m:0x0 + c:123
XF86AudioRaiseVolume
"amixer sset Master 2- &"
m0x0 + c:122
XF86AudioLowerVolume
"amixer sset Master toggle &"
m0x0 + c:121
XF86AudioMute
"xbacklight +10"
m:0x0 + c:233
XF86MonBrightnessUp
"xbacklight -10"
m0x0 + c:232
XF86MonBrightnessDown
And while xbacklight does raise and lower the screen brightness, and the fn keys are returning the above values, this still doesn't work.
I've made sure xbindkeys is running. I've gone over everything for possible typos. I've searched around for a solution. And I've concluded that I'm completely baffled.
Any help is greatly appreciated.
Offline
One thing I don't understand why do you have 3 lines for each command, I think that the default is two. (at least, that's what 'xbindkeys -d' says). The other thing I wanted to say is that you can run 'xbindkeys -n', that way it won't go to the background and it will print what's happening.
Offline
This is my .xbindkeysrc
"amixer sset Master 2+ &" m:0x0 + c:123 XF86AudioRaiseVolume "amixer sset Master 2- &" m0x0 + c:122 XF86AudioLowerVolume "amixer sset Master toggle &" m0x0 + c:121 XF86AudioMute "xbacklight +10" m:0x0 + c:233 XF86MonBrightnessUp "xbacklight -10" m0x0 + c:232 XF86MonBrightnessDown
And while xbacklight does raise and lower the screen brightness, and the fn keys are returning the above values, this still doesn't work.
I've made sure xbindkeys is running. I've gone over everything for possible typos. I've searched around for a solution. And I've concluded that I'm completely baffled.
Any help is greatly appreciated.
Are you have xbindkeys command in your .xinitrc?
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
Are you using KDE4?
If you do, then you may have a problem with some settings. I use xbindkeys and there are a number of occasions where KDE has a short-cut defined and it seems to take precedence.
I also noticed that some of my MM keys fail and KDE suggests that the key was not found or something while in the CLI I can see the command is correct.
R.
Offline
Hi guys, thanks for the quick replies! I was at work the whole day hence the delayed response.
To answer you questions in no particular order. Yes I have the xbindkeys command in my .xinitrc and it is starting when X does. No I am not using KDE4, I am using the awesome wm.
And lastly, when I run xbindkeys -n I receive the following message: Warning: unkown key in RC file : /home/[username]/.xbindkeysrc
At this point I am going to recheck all the keys and make sure once more that I have no typos. I am also going to try with just the key name (eg. XF86MonBrightnessDown), and then with just the key code (eg. m0x0 + c:232).
I will post to this thread again if the problem persists.
Offline
Sorry for the quick double post, but I've had a bit of a break.
For testing purposes I reduced the uncommented portion of my .xbindkeysrc to just
"xbacklight -10"
m0x0 + c:232
I made sure that I was using the key code exactly as it had been returned by xbindkeys -k. So this should've worked.
Running xbindkeys -n still gave me the warning I mentioned, but now there was also a second line which said: Error in alocation of keys
A quick google search then led me to the xbindkeys source code which simply states
790 if (keys == NULL)
791 {
792 fprintf (stderr, "Error in alocation of keys\n");
793 return (-1);
794 }
And now I am doubly confused, because after all, it was xbindkeys itself that gave me the key code to use.
Last edited by bdjnk (2009-09-02 15:09:01)
Offline
Pages: 1