[Bug 42820] Re: wireless.sh should use device/rf_kill instead of power/state

Nicolò Chieffo 84yelo3 at gmail.com
Fri Mar 23 22:43:52 UTC 2007


Does this mean that we won't have a working hotkey in Feisty? or just
that we need to wait?

I've had a look at the patch.  Great! But I've noticed that the
wireless status is not saved for halt/reboot too (only for suspend or
hibernate/resume). Are you going to add the file also in start.d and
stop.d?

And don't forget to correct another wireless.sh bug (that closes my
report #38354 but don't look at the bug description because it is very
messy):
wireless.sh prints something every time it finds a wireless interface
(you do a echo in the for). in my opinion you shuold do the for
without any echo, and then call
if isAnyWirelessPoweredOn; then
   echo 1
else
   echo 0
fi
using this you actually print the correct status (it is possible that
something fails in changing the status (well, it is sure if the card
does not support rf_kill, because the power/state method is broken),
and currently you don't perform any check!)

another proposal is to use networkmanager to completely disable
wireless so that the applet does not try to automatically connect
after we disabled wireless:

dbus-send --system --type=method_call
--dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
org.freedesktop.NetworkManager.setWirelessEnabled boolean:false

boolean:true to enable it. This can be put in wireless.sh and in
resume.d if nm forgets its options after the suspend (and in start.d
it you accept to add it)

Thank you!

PS: since you're active now, please have a look at this (very simple)
acpi-support bug:
https://launchpad.net/bugs/76593

-- 
wireless.sh should use device/rf_kill instead of power/state
https://launchpad.net/bugs/42820




More information about the kernel-bugs mailing list