Welcome to awesome bug tracking system.

FS#715 - awesome overrides xbindkeys keybinds

Attached to Project: awesome
Opened by Dieter Plaetinck (Dieter_be) - Saturday, 02 January 2010, 14:04 GMT
Task Type Bug Report
Category Core
Status Unconfirmed
Assigned To No-one
Operating System All
Severity Medium
Priority Normal
Reported Version 3.4.2
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No


awesome overrides/undoes xbindkeys keybindings.

I use xbindkeys for bindings which have nothing to do with the WM (starting apps, changing alsa volume, etc)
I use awesome's own keybinding system for WM-related bindings.
I start xbindkeys in ~/.xinitrc before I start awesome, so the xbindkeys process is running as long as X is running.(using xbindkeys 1.8.3)

this allows me to test different WM's without needing to redefine most keybinds (and I test a lot of different WM's).
With qtile from git or wmii 3.6 this gives no problems, the xbindkeys bindings just work.
With awesome 3.4.2 the xbindkeys bindings have no effect. I need to start a new xbindkey process after launching awesome.
Also, when I restart awesome (using the "restart" menu option) I manually need to restart xbindkeys also, because each restart overrides the xbindkeys bindings again.
This task depends upon

Comment by Dieter Plaetinck (Dieter_be) - Friday, 08 January 2010, 18:55 GMT
hmm.. it seems like keybindings for xbindkeys do work, but only on empty tags. if i have a tag with urxvt, claws-mail or firefox, i cannot execute any xbindkeys bind.
if i switch to a tag that has no apps, they work :/ (but after starting somethere it doesn't work anymore)

also, i'm getting a lot of these on my tty1:
X: awesome: xerror:316: X error: request=GrabKey, error=BadAccess
Comment by Uli Schlachter (psychon) - Saturday, 09 January 2010, 14:21 GMT
I started xbindkeys -v -f /tmp/t before awesome in an Xeyphr. Only kebinding used was ctrl+shift+w for strarting urxvt. I were able to start multiple urxvt this way (-> it worked on an empty and a non-empty tag). I used the current default awesome config. There was no single X error reported.

What did I do "wrong" to not see this bug?
Comment by Dieter Plaetinck (Dieter_be) - Sunday, 10 January 2010, 10:36 GMT
Hmm.. You did not do anything 'wrong', maybe the behavior under xephyr is different?
Anyway, i have the following bindings in xbindkeys:

"notify-send 'xbindkeys_show' && xbindkeys_show"
control+shift + q
"notify-send 'new term' && urxvt"
Mod1 + Return
"notify-send 'dmenu_run' && dmenu_run"
Mod1 + x

(the notify-send are just to doublecheck things)

mod1+return works always
the others only work on empty tags (i tried a tag with many programs in it: urxvt, firefox, abiword, claws-mail)

also, i have the following binding in my rc.lua:
awful.key({ modkey, }, "q", awesome.quit

this binding stops working at some point, but i'm not sure yet what triggers it.

also, the Xerrors I mentioned, i see them as soon as awesome starts, without even hitting any key.
I'll see if i can do some more research
Comment by Igor S. (ciphr) - Saturday, 31 July 2010, 13:26 GMT
awesome 3.4.6, launched xlock from xbindkeys (Mod4+F12), everything is fine. It doesn't matter whether tag is empty or not. Xbindkeys works for me.
Comment by Vivien Mallet (vivien) - Saturday, 16 October 2010, 06:57 GMT
I have just updated to Ubuntu to 10.10, and I experience the same problem now. At the same time, I updated from awesome 3.4.6 to awesome 3.4.8.

"control + mod4 + w" now works only on empty tags. In non-empty tags, "control + mod4 + w" is sent to the selected client. I do not know if it matters, but I have a French keyboard.

I have other bindings prefixed with "control + mod4" but they seem to be working fine.

I also confirm that the problem disappears when xbindkeys is launched after awesome.
Comment by Dariusz Dwornikowski (tdi) - Friday, 15 June 2012, 17:00 GMT
I confirm the same problem on Arch awesome 3.4.12. xbindkeys started after awesome does work.
Comment by Aron Kimig (arki) - Saturday, 25 August 2012, 10:11 GMT
Same problem on Arch / awesome 3.4.13.
Comment by Radek Fér (Collodi) - Wednesday, 23 January 2013, 18:10 GMT
I have similar problem here (Arch/awesome 3.4.13) - sometimes, after resume from sleep, my keyboard settings (set with "setxkbmap cz_qwerty; xmodmap .Xmodmap") are gone.
After I manually run these commands again, "my" keyboard is back.