ThinkPad wifi+bluetooth Fn+F5 toggling broken

i think this problem is part of Bug #24680
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/24680

this bug was in Dapper, Edgy, Feisty etc.
In mine a case the combination does not work in general.

Fn+ZOOM doesn't work too.

i don't know how the zoom functionality should be implemented now. This is another problem and you should add another bug. Once beryl is here we can find it a use.

The problem with the wireless functionality is related to the way wireless.sh script is implemented.

It uses

/sys/class/net/eth1/device/power/state

instead of

/sys/class/net/eth1/device/rf_kill

using /sys/bus/pci/drivers/ipw2200/*/rf_kill is not appropriate as it is dependent of the driver

my /etc/acpi/ibm-wireless.sh

#!/bin/bash
# Find and enable/disable wireless devices

state=`. /etc/acpi/wireless.sh`

if [ "$state" = "0" ]; then
    if [ -f /proc/acpi/ibm/bluetooth ]; then
        echo disable >/proc/acpi/ibm/bluetooth;
    fi
else
    if [ -f /proc/acpi/ibm/bluetooth ]; then
        echo enable >/proc/acpi/ibm/bluetooth;
    fi
fi

Script original (not edited)
No words about wifi

The Fn+Spacebar ("Zoom") issue is a separate one. Currently within 'thinkpad-keys' in the 'hotkey-setup' package, this is detected and passed through as a key-press; However there's currently nothing to assign it to (changing the screen mode is what is currently done under windows).

Please can you open a new bug report for the Zoom issue and I'll try to find the 'xrandr'-using script I did for this.

AleksysP: You said that 'Fn-F5' wasn't working on edgy/dapper? This should have worked fine---the issue has come up because the upstream kernel developers removed access to the 'power/state' interface.

confirmed

confirmed here on T40p. Can not turn on Bluetooth by pressing Fn+F5 at all!
Have a madwifi minipci - WLAN card and can turn on bluetooth manually by:

echo "enable" > /proc/acpi/ibm/bluetooth

On my T410 Fn+F5 toggles on/off only bluetooth. This was working fine on Feisty where it cycled through

both off
bluetooth on, wifi off
bluetooth on, wifi on
bluetooth off, wifi on

and so on...