On 07/11/10 11:19 AM, Luca Niccoli wrote: > On 7 November 2010 15:35, Ben Armstrong <[email protected]> wrote: > >> Testing it today I found a bashism: >> >> LINUX_FULL_VER=`uname -r` >> LINUX_MINOR_REV=${LINUX_FULL_VER:4:5} > > I'll fix it right away.
THanks. >> Furthermore, when using LXDE, there are some keys I would expect would >> be handled by eeepc-acpi-scripts, as LXDE itself doesn't handle them. >> Are these handled by GNOME & KDE? For example, hotkey 00000037 >> (touchpad) is ignored. > > This is not intentional. > I don't see where the problem is; the event regex > event=hotkey ASUS010:00 (0000001[0123456abcd]|0000003[012789]) > should catch it; hotkey.sh has not been changed in the way it manages > it; touchpad.sh has not been changed either and > eeepc-acpi-scripts.default is set to handle_touchpad_toggle. > Are you sure the problem is due to the scripts and not to synclient? > There has been a message on this mailing list about it some days ago... Yes, I am certain. Manually typing these commands works: synclient TouchpadOff=1 synclient TouchpadOff=0 also, manually executing the two lines from lib/hotkey.sh to toggle the touchpad works fine too: STATE="$(synclient -l 2>/dev/null | sed -e '/TouchpadOff/! d; s/[^0-9]\+//g')" synclient TouchpadOff=$((1-STATE)) 2>/dev/null || return 2 with set -x in hotkey.sh and acpid -d -l I get: + code=00000037 ++ test xhotkey = x- ++ echo 0x00000037 + value=0x00000037 ++ uname -r + LINUX_FULL_VER=2.6.32-5-amd64 + LINUX_MINOR_REV=32-5- + acpi= + acpiwrite= + ACPITEST=/lib/init/rw/eeepc-acpi-scripts.acpi-ignore + case "$code" in + test -f /lib/init/rw/eeepc-acpi-scripts.acpi-ignore + read acpi + test hotkey = hotkey + exit 0 END HANDLER MESSAGES acpid: action exited with status 0 acpid: 4 total rules matched acpid: completed netlink event "hotkey ASUS010:00 00000037 00000008" Ben _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
