This bug was fixed in the package acpi-support - 0.132
---------------
acpi-support (0.132) lucid; urgency=low
* lib/state-funcs, start.d/60-asus-wireless-led.sh, asus-wireless.sh:
eliminate setLEDAsusWireless altogether; this needs to be handled
directly by the kernel when the kill switch is toggled, not in a racy
and inconsistently-applied manner by acpi-support; and in at least some
cases we know this already *does* happen because of reports that
/sys/devices/platform/asus-laptop/wlan, used for toggling "the LED" with
the current kernel module, is actually an interface for toggling *the
antenna* that happens to also toggle the LED. Likewise, we should not
be responsible for bringing up the antenna at boot, so get rid of the
file in the start.d directory. LP: #293943, #204378, #334368.
* Now that the last script is gone from start.d, kill off the directory
and the init script handling too.
* Remove the asus-wireless-2 event handler, which is completely redundant
with the pre-existing asus-wireless-{off,on} handlers. LP: #207871.
[ Erik Andrén ]
* Add support for ATKD 00000037 to events/asus-touchpad.
This makes the disable touchpad buttons (!) on the EeePc 1005HA work as
intended. LP: #502720.
-- Steve Langasek <steve.langa...@ubuntu.com> Mon, 04 Jan 2010 15:52:56 -0800
** Changed in: acpi-support (Ubuntu)
Status: Fix Committed => Fix Released
--
Add touchpad disable hotkey event for Asus EeePc 1005HA
https://bugs.launchpad.net/bugs/502720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
