FS#78693 - [xbindkeys] stops working after kill -HUP

Attached to Project: Arch Linux
Opened by Yuri Kanivetsky (x-yuri) - Saturday, 03 June 2023, 01:29 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 05 July 2023, 00:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Konstantin Gizdov (kgizdov)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

This is probably an upstream issue, but it doesn't look like it's maintained anymore:

https://lists.nongnu.org/archive/html/xbindkeys-devel/

There's a fork, but I'm not sure if they want to go on, and that might be kind of a spin-off:

https://github.com/sharmanr/xbindkeys

Steps to reproduce:

/usr/local/bin/xbindkeys.sh:

#!/bin/sh -eu
stdbuf -o0 xbindkeys -n -v > /tmp/xbindkeys.log 2>&1

$ pkill -HUP xbindkeys

then try to press any keybindings.

$ cat /tmp/xbindkeys.log

displayName = :0
rc file = /home/yuri/.xbindkeysrc
rc guile file = /home/yuri/.xbindkeysrc.scm
getting rc guile file /home/yuri/.xbindkeysrc.scm.
WARNING : /home/yuri/.xbindkeysrc.scm not found or reading not allowed.
6 keys in /home/yuri/.xbindkeysrc

min_keycode=8 max_keycode=255 (ie: know keycodes)
"urxvt"
Control+Mod4 + x
"emacs"
Control+Mod4 + e
"chromium"
Control+Mod4 + c
"MOZ_USE_XINPUT2=1 firefox"
Control+Mod4 + f
"nautilus"
Control+Mod4 + a
"pavucontrol"
Control+Mod4 + p
starting loop...
Key press !
e.xkey.keycode=53
e.xkey.state=68
"urxvt"
Control+Mod4 + x
got screen 0 for window 55a
Start program with fork+exec call
Key release !
e.xkey.keycode=53
e.xkey.state=68
Reload RC file
getting rc guile file /home/yuri/.xbindkeysrc.scm.
WARNING : /home/yuri/.xbindkeysrc.scm not found or reading not allowed.
6 keys in /home/yuri/.xbindkeysrc

min_keycode=8 max_keycode=255 (ie: know keycodes)
"urxvt"
Control+Mod4 + x

I launched urxvt, sent HUP, after which the keybindings stopped working.

I'm running awesome + lightdm.
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 05 July 2023, 00:45 GMT
Reason for closing:  Upstream
Additional comments about closing:  Please report upstream as requested.
Comment by Yuri Kanivetsky (x-yuri) - Saturday, 03 June 2023, 01:49 GMT
xbindkeys is executed from ~/.xinitrc.
Comment by Toolybird (Toolybird) - Saturday, 03 June 2023, 02:47 GMT
Did you move the mouse as per the man page[1]?

[1] https://man.archlinux.org/man/xbindkeys.1#NOTE
Comment by Yuri Kanivetsky (x-yuri) - Saturday, 03 June 2023, 03:21 GMT
I don't have a mouse. If moving the mouse pointer with a touchpad counts, then I did.
Comment by Toolybird (Toolybird) - Saturday, 03 June 2023, 03:44 GMT
Ok, then like you say, it seems like an upstream issue. It doesn't matter that upstream appears inactive, it still needs to be reported upstream [1]. Arch is just a packager of this software, not the developer, and it's not a packaging bug. In fact, it was dropped to the AUR a few years ago but then resurrected.

[1] https://savannah.nongnu.org/bugs/?group=xbindkeys

Loading...