Arch Linux

CarolusRex

Member

Registered: 2020-03-31

Posts: 6

Awesome WM keyboard shortcuts issue (XKB 865)

Hi everyone!

I am trying to set up Awesome WM configuration and faced a problem related to keyboard shortcuts.
It's fully explained by this old piece of bug - https://bugs.freedesktop.org/show_bug.cgi?id=865
So, the problem which I've faced is the following - it seems that awesome starts handling of a shortcut on press
and I want to make it count every key until the release.

As always I set up aur/xorg-server-bug865, but it didn't help me unlike my common configuration with XFCE(DE+WM).

Some information which I could provide:

/etc/X11/xorg.conf.d/00-keyboard.conf

Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option  "XkbLayout"  "us,ru(winkeys)"
        Option "XkbModel" "pc105"
        Option "XkbVariant" "cyrillic"
        Option  "XkbOptions" "grp:ctrl_shift_toggle,grp_led:num,grp:switch,terminate:ctrl_alt_bksp"
EndSection

~/.xinitrc

setxkbmap -layout us,ru -variant -option grp:ctrl_shift_toggle,terminate:ctrl_alt_bksp &
urxvtd -q -f -o &
exec awesome

Example of key binding which I use in awesome config

    awful.key({"Shift"}, "Control_L", function () require("keyboard_layout").kbdcfg.switch_next() end),
    awful.key({"Control"}, "Shift_L", function () require("keyboard_layout").kbdcfg.switch_next() end)

Note: keyboard_layout is got from https://github.com/echuraev/keyboard_layout

Thank you in advance!

Last edited by CarolusRex (2020-04-01 11:55:00)

CarolusRex

Member

Registered: 2020-03-31

Posts: 6

Re: Awesome WM keyboard shortcuts issue (XKB 865)

One more thing - while doing some investigations on the bug, I've tried to add following lines to my config:

awful.key({"Shift"}, "Control_L", function() print("pressed1") end, function() print("released1") end),
awful.key({"Control"}, "Shift_L", function() print("pressed2") end, function() print("released2") end)

But the only prints in the output are pressed1/pressed2.
Am I right that it could be a solution? Should I change this lines somehow or maybe use awful.keygrabber?

UPDATE:
OK, I found a related bug in awesome bugtracker - https://github.com/awesomeWM/awesome/issues/169
It seems that I should do something else to resolve my issue.

Last edited by CarolusRex (2020-04-02 01:02:05)