Arch Linux

Description:
I am using xbindkeys to send a doubleclick on "middle click" with the mouse.
It took me quite a while to find out while it seems to work unreliable. It works fine when using the default keyboard (ch) but when I switch to a different layout (e.g. dk) it stops working. You can see below that it triggers a different button.state and while the one for "ch" triggers the keybinding, the button.state for "dk" does not.

Additional info:
* xbindkeys 1.8.6-3 in combination with xautomation 1.09-3
* Layout CH - running "xbindkeys -n -v" and pressing the button 2:
"/usr/bin/xte 'mouseclick 1' 'mouseclick 1' &"
Release + m:0x0 + b:2 (mouse)
starting loop...
Button press !
e.xbutton.button=2
e.xbutton.state=0
Button release !
e.xbutton.button=2
e.xbutton.state=512
"/usr/bin/xte 'mouseclick 1' 'mouseclick 1' &"
Release + m:0x0 + b:2 (mouse)

* Layout DK - running "xbindkeys -n -v" and pressing the button 2:
"/usr/bin/xte 'mouseclick 1' 'mouseclick 1' &"
Release + m:0x0 + b:2 (mouse)
starting loop...
Button press !
e.xbutton.button=2
e.xbutton.state=0
Button release !
e.xbutton.button=2
e.xbutton.state=8704

* The test below was done first with "ch" (first 4 lines) and then with "dk" (last 4 lines).
$ xev |grep -i button
ButtonPress event, serial 34, synthetic NO, window 0x3e00001,
state 0x0, button 2, same_screen YES
ButtonRelease event, serial 34, synthetic NO, window 0x3e00001,
state 0x200, button 2, same_screen YES
ButtonPress event, serial 34, synthetic NO, window 0x3e00001,
state 0x0, button 2, same_screen YES
ButtonRelease event, serial 34, synthetic NO, window 0x3e00001,
state 0x2200, button 2, same_screen YES

* It looks like this bug is known and a patch available - see the reply from Manuel here: https://askubuntu.com/questions/689410/xbindkeys-does-not-trigger-some-keys-when-keyboard-layout-changes.