I tried looking at the /etc/acpi/ibm-wireless.sh script to find the cause of the issue and noticed the the wireless status cannot be affected by that script: The script relies on isAnyWirelessPoweredOn and toggleAllWirelessStates to control the wireless, which are in /usr/share/acpi-support/state-funcs. But those functions don't have any effect as /sys/class/net/wlan0/device/power/state does not even exist (there is /sys/class/net/wlan0/operstate which provides the information). Nevertheless, wireless does get affected when pressing the button, and the only thing the script does is toggle bluetooth. Now I wonder, is FN+F5 first "interpreted" at a level below ACPI (or possibly even below the kernel?) which toggles the state of the wireless and then acpi enters and toggles bluetooth, or is there another acpi script that gets executed when pressing that key combination? What I also noticed is that the /etc/acpi/ibm-wireless.sh and /usr/share/acpi-support/state-funcs files are actually identical between jaunty and karmic, therefore I assume there must be at least a third element somewhere which made it work in jaunty. Any hints?
-- [IBM ACPI] FN+F7 only allows to enable/disable WLAN and BT simultaneously https://bugs.launchpad.net/bugs/396541 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
