Pavel,
thanks for checking. I'm afraid there's no generic way to fix this in the rules then :/
You can fix it locally by creating a file /etc/udev/rules.d/95-keyboard.rules with
--------------------- 8< ------------------ ACTION=="remove", GOTO="force_release_end" SUBSYSTEM!="serio", GOTO="force_release_end" KERNEL!="serio*", GOTO="force_release_end" DRIVER!="atkbd", GOTO="force_release_end" ENV{DMI_VENDOR}="$attr{[dmi/id]sys_vendor}" ENV{DMI_VENDOR}=="TOSHIBA", RUN+="keyboard-force-release.sh $devpath common-volume-keys" --------------------- 8< ------------------
Pavel,
thanks for checking. I'm afraid there's no generic way to fix this in the rules then :/
You can fix it locally by creating a file /etc/udev/ rules.d/ 95-keyboard. rules with
------- ------- ------- 8< ------------------ release_ end" release_ end" release_ end" release_ end" VENDOR} ="$attr{ [dmi/id] sys_vendor} " VENDOR} =="TOSHIBA" , RUN+="keyboard- force-release. sh $devpath common-volume-keys" ------- ------- 8< ------------------
ACTION=="remove", GOTO="force_
SUBSYSTEM!="serio", GOTO="force_
KERNEL!="serio*", GOTO="force_
DRIVER!="atkbd", GOTO="force_
ENV{DMI_
ENV{DMI_
-------