bluetooth doesn't remember on/off state after boot

[Felipe Figueiredo]

Binary package hint: gnome-bluetooth

Everytime I boot, I have to turn the bluetooth off in the indicator applet to conserve power.

I'd like it to remember my last choice, so that I only turned it on when I want to use it.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-bluetooth 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Oct 5 23:09:09 2010
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=pt_BR.utf8
 SHELL=/bin/bash
SourcePackage: gnome-bluetooth

[Sebastien Bacher (seb128)]

thank you for your bug report, seems it should be a system behaviour, nothing to do with the indicator applet in any case there

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Tristan Hill (stan)]

Per http://ubuntuforums.org/showpost.php?p=10167074&postcount=7 this can be worked around by adding

rfkill block bluetooth

to startup applications.

Since both the gnome applet and rfkill use /dev/rfkill the applet should pick up the disabled state still.

[Chris Giltnane (chris-giltnane)]

I think the bug is that for a non-command line user, the system should remember the state of bluetooth. There are multiple ways of working around this problem but these do not address the core issue that unless you want to get into command line stuff then there is no way to stop bluetooth starting on the next boot. Actually this is one of the most irritating bugs around.

[Stéphane Guillou (stephane-guillou)]

Also affects me in 11.10.

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 446657, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.