I have this UDEV rule, which gets activated when I plug in my keyboard:
ACTION=="add", DEVPATH=="/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:046A:0011.00??/input/input??/event[0-9][0-9]*", ATTRS{name}=="HID 046a:0011", ATTRS{phys}=="usb-0000:00:14.0-1/input0", RUN+="/home/*user*/.udev_rule_scripts/cherry_keyboard.sh", SYMLINK+="cherrysymlink"
It should
- create a symlink
/dev/cherrysymlink, which it does, and
- execute a shell script, which it doesn’t.
Here’s the debugging output of udevadm test /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:046A:0011.0003/input/input18/event17:
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
.INPUT_CLASS=kbd
ACTION=add
DEVLINKS=/dev/input/by-id/usb-046a_0011-event-kbd /dev/cherrysymlink /dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-kbd
DEVNAME=/dev/input/event17
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:046A:0011.0003/input/input18/event17
ID_BUS=usb
ID_INPUT=1
ID_INPUT_KEY=1
ID_INPUT_KEYBOARD=1
ID_MODEL=0011
ID_MODEL_ENC=0011
ID_MODEL_ID=0011
ID_PATH=pci-0000:00:14.0-usb-0:1:1.0
ID_PATH_TAG=pci-0000_00_14_0-usb-0_1_1_0
ID_REVISION=0100
ID_SERIAL=046a_0011
ID_TYPE=hid
ID_USB_DRIVER=usbhid
ID_USB_INTERFACES=:030101:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=046a
ID_VENDOR_ENC=046a
ID_VENDOR_ID=046a
LIBINPUT_DEVICE_GROUP=3/46a/11/111:usb-0000:00:14.0-1
MAJOR=13
MINOR=81
SUBSYSTEM=input
USEC_INITIALIZED=31155231
run: '/usr/local/bin/cherry.sh'
When the keyboard is plugged in, /dev/cherrysymlink is created. Also the debugging output says in the last line that the script /usr/local/bin/cherry.sh did indeed run.
The problem is, the script doesn’t get actually executed.
cherry_keyboard.sh:
#!/bin/bash
xset r rate 150 60
It should change the autorepeat of the keyboard keys but it stays the same.
I’ve also tried:
#!/bin/bash
slock
Nothing happens. When I execute the scripts manually in the shell they both work. What am I doing wrong?
EDIT:
After modifying my script like this I am able to pipe the echo output into dzen2 so it pops up on the screen:
#!/bin/bash
export DISPLAY=:0
export XAUTHORITY=/home/*user*/.Xauthority
echo 'test' > /home/*user*/.udev_rule_scripts/test
echo 'test' | dzen2 -p 4
xset r rate 150 60
slock
So far, the first two echo-lines work. The xset and slock commands still don’t work.
EDIT2:
After some reading I am pretty certain it has something to do with DBUS and the environment variable “DBUS_SESSION_BUS_ADDRESS”. Also, when I run printenv as user, there is DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus set. When I run printenv as root this variable is not set.
Therefore I made another modification to my script:
#!/bin/bash
export DISPLAY=:0
export XAUTHORITY=/home/*user*/.Xauthority
export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
echo 'test' > /home/*user*/.udev_rule_scripts/test
echo 'test' | dzen2 -p 4
xset r rate 150 60
slock
Unfortunately, it still doesn’t work.
EDIT3:
After Gilles’ suggestion I added a line to the script:
#!/bin/bash
exec >>/home/*user*/.udev_rule_scripts/test.log 2>&1; echo; date
export DISPLAY=:0
export XAUTHORITY=/home/*user*/.Xauthority
echo 'test' | dzen2 -p 4
xset r rate 150 60
slock
which produces the following error message in test.log
Tue Feb 23 10:14:17 UTC 2016
/home/*user*/.udev_rule_scripts/cherry_keyboard: line 11: 858 Segmentation fault (core dumped) slock
which (kind of) explains why slock fails to execute.
Sadly, there’s nothing about xset.
EDIT4:
This time, I combined Gilles’ and ojs’ suggestions. Now the error messages are more interesting:
cherry_keyboard.sh:
#!/bin/bash
exec >>/home/*user*/.udev_rule_scripts/test.log 2>&1; echo; date
export DISPLAY=:0
export XAUTHORITY=/home/*user*/.Xauthority
echo 'test' | dzen2 -p 4
su *user* -c "DISPLAY=:0 xset r rate 150 60"
su *user* -c "DISPLAY=:0 slock"
test.log:
Tue Feb 23 10:37:22 UTC 2016
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 43 requests (37 known processed) with 0 events remaining.
Tue Feb 23 10:38:37 UTC 2016
dzen: cannot open display
xset: unable to open display ":0"
slock: cannot open display
Tue Feb 23 10:40:54 UTC 2016
Now here’s the thing: When I plugin my keyboard, dzen2 pops up on the screen, then the screen goes black. But not because of slock, it kind of crashes and when I type on the keyboard the screen stays black (which it shouldn’t when slock was behind it). Other applications like moc are still running.
And now the strange part:
When I press the power button on my laptop to restart the system (which is the only option in this situation I think), before shutdown, the black screen disappears for half a second and instead a red screen appears (the red screen of slock when you type in a wrong password). So slock IS actually running. But why does the error message state that both dzen and slock “cannot open display”, while they’re in fact both running? And why does the screen crash? And in which way does xset‘s error message differ?
An alternative cherry_keyboard.sh:
#!/bin/bash
exec >>/home/*user*/.udev_rule_scripts/test.log 2>&1; echo; date
export DISPLAY=:0
export XAUTHORITY=/home/*user*/.Xauthority
echo 'test' | dzen2 -p 4
su *user* -c "DISPLAY=:0 xset r rate 150 60"
#su *user* -c "DISPLAY=:0 slock"
test.log:
Tue Feb 23 10:43:36 UTC 2016
So this time there are no error messages at all.
But, in both versions xset does not modify the autorepeat…
