Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends

[pablomme]

Binary package hint: gnome-bluetooth

Gnome's bluetooth applet should get a bluetooth device's on/off status through dbus from SetProperty setting sent by bluetoothd. This information was given in http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a setting controlling this feature: RememberPowered=true in /etc/bluetooth/main.conf

Questions:
Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't do anything for it? Does bluez's SetProperty actually find the last (if even saved) bluetooth status?

ProblemType: Bug
Architecture: i386
Date: Thu Oct 8 20:54:15 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: gnome-bluetooth 2.28.1-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
SourcePackage: gnome-bluetooth
Uname: Linux 2.6.31-12-generic i686

[papukaija (papukaija)]

True, the on/off setting should not be lost on restart.

[Omer Akram (om26er)]

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue , in the default Ubuntu 9.10 install , that affects many people and is quick and easy to fix. So this bug can't be addressed as part of the project.

its rather more like a feature request

For further info about papercuts criteria , pls read > https://wiki.ubuntu.com/PaperCut

Don't worry though, This bug has been marked as "invalid" ONLY in the papercuts project.

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[papukaija (papukaija)]

This bug is now sent to upstream (at https://bugzilla.gnome.org/show_bug.cgi?id=607334 ).

[Charlie Kravetz (cjkgeek)]

Set to triaged; status low as this is a nice to implement feature.

[papukaija (papukaija)]

According to https://bugzilla.gnome.org/show_bug.cgi?id=598140#c2 this feature isn't gnome-bluetooth's job, but bluetoothd's (part of bluez). So do I change it here too?

[Lightbreeze (nedhoy-gmail)]

@papukaiji: For the Ubuntu task press "Also affects distribution" then change the package name in the box that appears.

[papukaija (papukaija)]

Where is the upstream bug reporting system for bluez?

[Vish (vish)]

@papukaija: http://wiki.bluez.org/report/1 seems to be the place to report the issue

[papukaija (papukaija)]

Vish: I found that, but there is no login/signup page to submit bugs.

[Vish (vish)]

@papukaija: Yes , the filing of bugs seems a bit weird. :(
However i had a quick look , Try getting some info from these links>
http://wiki.bluez.org/wiki/TracReports
http://wiki.bluez.org/wiki/TracGuide
http://trac.edgewall.org/wiki/TracFaq

If all else fails , try contacting the devs directly > http://www.bluez.org/contact/
I didnt have time to dig deeper. thanks for looking into this.

[papukaija (papukaija)]

OK, you can follow the discussion at
http://permalink.gmane.org/gmane.linux.bluez.kernel/4287

[papukaija (papukaija)]

Sorry, the correct link is:
http://comments.gmane.org/gmane.linux.bluez.kernel/4287

And it seems that this feature is already implemented, but for some reason not working in Ubuntu.

[papukaija (papukaija)]

I'm going to edit this bug's title and description since this feature request is implemented,but for some reason not working in Ubuntu.

[papukaija (papukaija)]

For some reason I can't change this bug's title to "Doesn't get the bluetooth's on/off status from the SetProperty D-Bus method that bluetoothd sends"

[Սահակ (petrosyan)]

this bug has been fixed in Ubuntu 10.04

[Vish (vish)]

Սահակ , I'm using Ubuntu 10.04 and its _not_ fixed for here.

[Baptiste Mille-Mathias (bmillemathias)]

Not a gnome-bluetooth problem

[Baptiste Mille-Mathias (bmillemathias)]

Rather on bluez

[Baptiste Mille-Mathias (bmillemathias)]

Honnestly this bug is a mess, the title is "Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends" but th epeople complains about non-remembering the power status after computer reboot, which is *totally* different.

[pablomme (pablomme)]

@Baptiste: please read the full bug history. This bug was initially reported against gnome-bluetooth, forwarded upstream, rejected, then moved against bluez, forwarded upstream, and confirmed non-existent there. This turns out to be an Ubuntu-specific problem that prevents bluez from using its existing feature of loading the previously recorded on/off state, which is caused by a dbus communication issue or, most likely, inaction on the dbus communication between gnome-bluetooth and bluetoothd.

The bug title is correct and the comments are on-topic. The only messiness stems from the fact that this bug has required reporting to two different upstreams to discover the nature of the problem, but that's just the way things have panned out.

Please reconsider whether you really wish to move the bug against bluez again.

[papukaija (papukaija)]

@Baptiste: Please read http://permalink.gmane.org/gmane.linux.bluez.kernel/4302

@All: I'm going to re-assign this bug for gnome-bluetooth and to remove the bug watcher since it was created for the feature request. Should this bug be opened for dbus too?

[papukaija (papukaija)]

It's of course possible that the dbus message in question is not sent by bluetoothd's (part of bluez).

I'm setting the external tracker to invalid since this bug seems to be an Ubuntu specific problem (see comment 22 and http://permalink.gmane.org/gmane.linux.bluez.kernel/4291 ).

[papukaija (papukaija)]

Is there a way to debug this bug?

[Vish (vish)]

@Baptiste Mille-Mathias : How do we proceed with this bug? bluez says its not their bug . And everyone else says its a bluez bug.

I had filed a similar bug [ Bug #503286 ] regarding the hardware switch not remembering the bluetooth state.
And kernel upstream also mentioned that the bug needs fixing in bluez

Attaching my /etc/bluetooth/main.conf
upstream bluez mentions it works with the git version. is this an ubuntu bug?

[sassmann (sassmann-redhat-bugs)]

Description of problem:
On my lenovo t500 bluetooth is always enabled after reboot, regardless if it was turned off before the reboot or not. Not sure why this happens but someway during initrd run I see the bluetooth LED turning on.

Version-Release number of selected component (if applicable):
gnome-bluetooth-2.28.6-2.fc12.x86_64

How reproducible:
always

Steps to Reproduce:
1. turn off bluetooth in gnome-bluetooth applet
2. reboot
3.

Actual results:
bluetooth is always turned on

Expected results:
bluetooth setting is the same as before the reboot

Additional info:

[papukaija (papukaija)]

In main.conf, there is:

# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true

If you set this to false, the bluetooth-applet will show bt as disabled regardless of your bt status at logout. This means that gnome-bluetooth doesn't get the SetProperty dbus message sent by bluetoothd.

So should this bug be opened for dbus and/or for bluez?

[Vish (vish)]

Even if set :
InitiallyPowered = false

I find the hardware bluetooth light always on for every boot.

[Alexander Sack (asac)]

this would require us to change main.conf to:

# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true

# Remember the previously stored Powered state when initializing adapters
RememberPowered = true

however, this causes problems for some users so we shouldn't change this that late this cycle. lets try it next cycle.

[papukaija (papukaija)]

Wait wait. Those are the default values. So, we're back in finding out why gnome-bluetooth doesn't get the SetProperty dbus message sent by bluetoothd. How to debug dbus?

[Gleb Kozyrev (gkozyrev)]

In my case (on lucid) dbus seems to be working just fine: the applet is able to switch bluetooth on/off and is correctly notified when switched via rfkill.
Still bluetooth is always on at startup regardless of the applet and InitiallyPowered/RememberPowered settings. Should this be filed as a separate bug? It might get bounced between upstreams the same way :(
BTW, where is Powered state supposed to be stored when RememberPowered = true? Looking for modified files with find / ~/ -newermt '2 min ago' gives me nothing but log files.

[pablomme (pablomme)]

I was about to add that this bug seems fixed in lucid, but clearly Gleb's comment indicates otherwise. Mine is a clean 32-bit install from beta 2 - Gleb, how does your installation differ from mine?

[Vish (vish)]

Doesnt work for me either in Lucid.
Every boot i have to turn the bluetooth LED off using the kill switch.

[Gleb Kozyrev (gkozyrev)]

Mine is 64-bit. I've installed a fresh ubuntu-10.04-beta2-desktop-amd64 today and bluetooth is always on after boot.

[papukaija (papukaija)]

Gleb (about your comment 31): The only bug reported in this bug report is that bluetooth on/off status isn't remembered on boot.

All: How to debug bluez to see if the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't do anything for it? Or to see if bluez's SetProperty actually finds the last (if even saved) bluetooth status?

[papukaija (papukaija)]

Please remove the wishlist importance since this is a real bug.

[papukaija (papukaija)]

Has anyone tried to reproduce this bug in Maverick?

[Vish (vish)]

@papukaija : In Lucid , I'v tested with mainline Kernel .34 and .35 , both of which remember the killswitch state of the previous session. Bug might have been in the kernel?
Could you try the mainline kernels too? https://wiki.ubuntu.com/KernelMainlineBuilds

[papukaija (papukaija)]

@Vish: That would explain why bluez.org can't confirm this bug. I'll test with 2.6.34-lucid and 2.6.35-rc1-lucid soon. Is your attached main.conf a file with default settings because I'm not sure if my file has the defaults, especially about the "RememberPowered" setting?

[Vish (vish)]

@papukaija : InitiallyPowered and RememberPowered are both true by default.

[papukaija (papukaija)]

@Vish: I tested both 2.6.34-lucid and 2.6.35-rc1 without success (with InitiallyPowered and RememberPowered as true). I noticed from upstream kernel bug report (linked to this bug's dupplicate) that this shouldn't be a bug in Kernel. Maybe this is still a bug in bluetooth-applet which would not get the SetProperty dbus message sent by bluez's bluetoothd. I'll try if running bluetooth-applet from terminal shows anything special.

[papukaija (papukaija)]

I manually started bluetooth-applet from the terminal (in Lucid on Ubuntu's 2.6.32 Kernel) and it didn't show any error messages. I attach the debug messages if someone wants to look at them. Is it possible that the applet doesn't actually save the last bt-status or that it just doesn't get the dbus message?

[jpazdziora (jpazdziora-redhat-bugs)]

The same problem on Fedora 13 with gnome-bluetooth-2.30.0-1.fc13.i686 on T61. Bastien, please, let us know if some other package might be causing this and you'd need more detailed version info, or if it is configurable somewhere.

I am pretty sure that on Fedora 11 my bluetooth was off after reboot (and I had the option to turn it on with the applet on my panel). That's why I'd consider this a regression.

[jpazdziora (jpazdziora-redhat-bugs)]

Funny thing: if I change in /etc/bluetooth/main.conf InitiallyPowered = true to false, and reboot, the applet will show that white x in red on its icon, to say that bluetooth is off. However, the bluetooth LED is still on, so in that case the applet shows incorrect information.

So maybe this is a bug in bluez (which owns that /etc/bluetooth/main.conf), that it does not honor the setting (and provides bad info to the applet as well)? But I don't see a component bluez in bugzilla to report it ...

[jpazdziora (jpazdziora-redhat-bugs)]

(In reply to comment #2)
> Funny thing: if I change in /etc/bluetooth/main.conf InitiallyPowered = true to
> false, and reboot, the applet will show that white x in red on its icon, to say
> that bluetooth is off. However, the bluetooth LED is still on, so in that case
> the applet shows incorrect information.

Another finding: even if the icon of the applet shows that bluetooth is off, when I click it, the status is shown as On, and I have the option to "Turn Off Bluetooth". When I turn if off, the LED goes off as well. When I then turn in on again, the LED goes on, but the icon on the panel still shows that red/white "off" sign.

[pablomme (pablomme)]

As I mentioned in an earlier comment, I suspect this bug has some hardware-dependent component to it. I used to have this on a Dell Mini 9 with Jaunty and Karmic, but my Eee PC 1201N with Lucid works correctly.

[papukaija (papukaija)]

I have Samsung NC10 netbook with Ubuntu Lucid 10.04 UNE. The intenrnal bluetooth device is a BCM2046 Bluetooth Device.

So this is a bug in the kernel (supposing that the bt drivers are part of it) ?

[bnocera (bnocera-redhat-bugs)]

(In reply to comment #1)
> The same problem on Fedora 13 with gnome-bluetooth-2.30.0-1.fc13.i686 on T61.
> Bastien, please, let us know if some other package might be causing this and
> you'd need more detailed version info, or if it is configurable somewhere.
>
> I am pretty sure that on Fedora 11 my bluetooth was off after reboot (and I had
> the option to turn it on with the applet on my panel). That's why I'd consider
> this a regression.

Definitely not a regression, if anything, it's a kernel one. The ibm-laptop (or whatever the kernel module is called for Thinkpads) module changed behaviour.

(In reply to comment #2)
> Funny thing: if I change in /etc/bluetooth/main.conf InitiallyPowered = true to
> false, and reboot, the applet will show that white x in red on its icon, to say
> that bluetooth is off. However, the bluetooth LED is still on, so in that case
> the applet shows incorrect information.

Nope. Check the output of "hciconfig hci0", you'll see that the device is enabled, just not powered. The hardware has no ways to know that...

> So maybe this is a bug in bluez (which owns that /etc/bluetooth/main.conf),
> that it does not honor the setting (and provides bad info to the applet as
> well)? But I don't see a component bluez in bugzilla to report it ...

This is a BIOS bug. gnome-bluetooth doesn't hold *any* information as to the state of Bluetooth, and bluetoothd (somewhat) remembers the state of the device. The problem is that when it's hard-blocked, eg. disabled in hardware, bluetoothd has no Bluetooth devices to remember the setting of.

With a good BIOS, the BIOS should remember the previous state, and use that.

[sassmann (sassmann-redhat-bugs)]

Actually when I observe the bluetooth LED on the Thinkpad it is off during BIOS init and just turns on sometime while executing the initrd. So I guess some module in the initrd is actually activating bluetooth.
Maybe it's thinkpad_acpi but not sure.

[jpazdziora (jpazdziora-redhat-bugs)]

(In reply to comment #4)
> > this a regression.
>
> Definitely not a regression, if anything, it's a kernel one. The ibm-laptop (or
> whatever the kernel module is called for Thinkpads) module changed behaviour.

I am not qualified to pinpoint the component which caused the change in behaviour -- I've just pointed out that something which used to work in Fedora 11 now behaves in a less desirable way.

> With a good BIOS, the BIOS should remember the previous state, and use that.

The BIOS hasn't been updated/changed since I used Fedora 11 on this machine. So it has to be something between F11 and F13 (well, F12 and F13, even though I am not 100 % sure what the behaviour on F12 was) that changed in an undesirable way. And I'd like to find the cause and bring back the pre-F13 behaviour.

[papukaija (papukaija)]

This bug is affecting more people than LP says: http://brainstorm.ubuntu.com/idea/25499/

[papukaija (papukaija)]

@members of bug-control team: Please change this bug's importance from wishlist to something else as this is a real bug (but seems to be hw-specific). I suggest low or even medium importance, given that this bus isn't the end of world but affect more than just those 7 people reported by LP as there are 3 duplicate bugs and in total 140 votes in the brainstorm idea linked in comment 45. Thanks in advance!

[triage (triage-redhat-bugs)]

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[jpazdziora (jpazdziora-redhat-bugs)]

Flipping version to Fedora 13.

[Kent Asplund (hoglet)]

This problem affects me too on Natty.
U nfortunately for me the saved state of bluetooth is off. This means that I have no bluetooth on startup nor after resume. As I am using a bluetooth mouse it has been very irritating.

Setting "RememberPowered = false" in /etc/bluetooth/main.conf is the workaround for me, and others, while waiting.

[marbolangos (marbolangos-redhat-bugs)]

Same in F15!

[jpazdziora (jpazdziora-redhat-bugs)]

Flipping the version to Fedora 15 so that this bug does not get autoclosed.

[Peter Hedlund (peter-peterandlinda)]

The problem remains in Oneiric. Bluetooth is always on after a reboot. MacBook Air 3,2.

[papukaija (papukaija)]

I just linked six duplicate bugs to this report. Please remove the wishlist importance. Thanks in advance.

[Colin Ian King (colin-king)]

Problem also in Precise.

[ndMHcGFzqhcfQEAdTKmfxZqTbujWUyxE (ndmhcgfzqhcfqeadtkmfxzqtbujwuyxe-deactivatedaccount)]

as far as i'm concerned, this is a security issue. having open avenues for attack reopen every boot is not to be overlooked. even us-cert has a bulletin on bluetooth security and the first item under 'how can you protect yourself' is to disable it when you're not using it.

http://www.us-cert.gov/cas/tips/ST05-015.html

[papukaija (papukaija)]

Interesting. Gnome rejected this bug at https://bugzilla.gnome.org/show_bug.cgi?id=598140#c2 but know Bastien Nocera [gnome-bluetooth developer] thinks at https://bugzilla.gnome.org/show_bug.cgi?id=638117#c9 that this is a bug in Gnome and bluez.

[papukaija (papukaija)]

*now

[boris.nadezhdin (boris.nadezhdin-redhat-bugs)]

The same issue in F16 on Sony Vaio VPCEB3B4R

[Mathieu Trudel-Lapierre (cyphermox)]

We're covering this through an upstart job (rfkill-store, rfkill-restore) that should save and restore all killswitch states; so I'm unassigning this since the rest of the work in gnome-bluetooth and bluez should come from upstreams.

[daniel (daniel-redhat-bugs-1)]

I'm also having the same issue on a Sony Vaio VPCSA3.

[dbraunwarth (dbraunwarth-redhat-bugs)]

Same here on 3.3.0-4.fc16.x86_64

But systemctl status bluetooth.service returns:

bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled)
   Active: inactive (dead)
   CGroup: name=systemd:/system/bluetooth.service

[Stéphane Guillou (stephane-guillou)]

This is still affecting Ubuntu 12.04 LTS.
It is still seen as an obvious defect by most users, and it would be sad not to see it fixed in this LTS, even more because it has been around for a while.
A lot of people never use bluetooth on their device and want to save battery life. Switching it from on to off every time the computer boots basically extends the time necessary for people to start using their device, and makes them see Ubuntu as "user-unfriendly".

[Elias K Gardner (zorkerz)]

Get me if I'm wrong by in 12.04 my bluetooth seems to remember its turned
off state across restarts at least judging by the indicator remaining
grayed out (I don't know if this means it is really turned off).

On Mon, Apr 2, 2012 at 6:39 PM, Stéphane Guillou
<email address hidden>wrote:

> This is still affecting Ubuntu 12.04 LTS.
> It is still seen as an obvious defect by most users, and it would be sad
> not to see it fixed in this LTS, even more because it has been around for a
> while.
> A lot of people never use bluetooth on their device and want to save
> battery life. Switching it from on to off every time the computer boots
> basically extends the time necessary for people to start using their
> device, and makes them see Ubuntu as "user-unfriendly".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/446657
>
> Title:
> Bluetooth's on/off status doesn't update from the SetProperty D-Bus
> method that bluetoothd sends
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions
>

[Chris Giltnane (chris-giltnane)]

yep since a few days ago this seems to be working fine. At least on my Lenovo T61 with 12.04 updates.

[papukaija (papukaija)]

There has indeed been some improvements to this bug in Precise but the indicator menu is still confused by the bluetooth status, I tested this a while ago with my mobille phone and the BT status wasn't working correctly (and the initial status in the indicator menu was misleading). I also had some issues to even enable BT before restarting the BT service in the system.

The improvement was from this upload:

bluez (4.98-2ubuntu4) precise; urgency=low
[...]
  * Eliminate the /etc/default/bluetooth conffile as it's not the Upstart
    way. Transition the BLUETOOTH_ENABLED variable to an Upstart override
    variable if it's been changed.

I will test again since there has been many updated packages after my testing.

[Stéphane Guillou (stephane-guillou)]

The issue is definitely still here on my Samsung N310, with everything updated today.

I either deactivate the bluetooth from the indicator dropdown menu, or inside the settings window, the result is the same: it is back on when I reboot my computer.

[Sam_ (and-sam)]

Nothing changed (indicator is confused since four years due to confused responsibilities).
Cold boot: bluetooth is off (g-c-c), indicator states it's on and it can be turned off.
Reboot: bluetooth is off (g-c-c), indicator states it's off and it can be turned on.
Enable it on indicator, open settings - it's still off in g-c-c.

bluez:
  Installed: 4.98-2ubuntu7
  Candidate: 4.98-2ubuntu7
  Version table:
 *** 4.98-2ubuntu7 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

[Ing. Radomír Polách (exander77)]

Seems to work fine Precise.

[bcotton (bcotton-redhat-bugs)]

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[jpazdziora (jpazdziora-redhat-bugs)]

Reopening as I feel the problem is still present in Fedora 17.

On the other hand, I am not completely sure that gnome-bluetooth is the right component as I can see the same behaviour on XFCE desktop.

[jamilo (jamilo-redhat-bugs)]

I am also having the same issue on Fedora 17 (64bit Gnome). I am surprised this bug has been there for so long. Is this applicable to only very specific systems?

[Stéphane Guillou (stephane-guillou)]

This is still a problem in Quantal up to date.
At restart, I have to turn the bluetooth off every time.

[papukaija (papukaija)]

The upstream is working on a fix for this bug.

[mattdm (mattdm-redhat-bugs)]

Still the case in F18 beta.

[Kyle Fazzari (kyrofa)]

Sounds like it might be the issue outlined here, which includes a fix: https://bugs.launchpad.net/bugs/1073669 .

[papukaija (papukaija)]

That bug is indeed the same bug but I haven't tried if the fix works.

[draeath (draeath-redhat-bugs)]

This happens for me on an eeepc 1000 (Fedora 17, XFCE).

For this device, the adapter is attached to the USB bus internally.

From lsusb:
Bus 005 Device 002: ID 0b05:b700 ASUSTek Computer, Inc. Broadcom Bluetooth 2.1

I don't have a hardware indicator to tell me if it's actually on or not, but regardless of whether I tell it to turn off or not, it's back up on the next boot.

[tommy (tommy-redhat-bugs)]

I have same problem, after disable bluetooth using command

systemctl disable bluetooth.service

bluetooth still shown after restart. I've to kill blueman-applet every time I boot my system.

I'm using Fedora 18 XFCE.

[grawert (grawert-redhat-bugs)]

I had the same issue on a Lenovo X1. The problem seems not to be gnome-bluetooth or any bluetooth daemon. For Lenovo laptops there is the thinkpad-acpi kernel module. That module is activating bluetooth. I did the following:

# modprobe -r thinkpad_acpi
# modprobe -v thinkpad_acpi
insmod /lib/modules/3.7.6-201.fc18.x86_64/kernel/drivers/platform/x86/thinkpad_acpi.ko fan_control=1

Bluetooth is actived now! There is a module parameter bluetooth=0, but it is not recognized as of thinkpad_acpi module version 0.24. The documentation is also mentioning that many paramters are deprecated, and rfkill shall be used. When examining with rfkill, the following blocked states are set after module loading:

# rfkill list bluetooth
3: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: no
 Hard blocked: no
4: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

As soon as I turn on "soft blocking" for bluetooth, it gets disabled:

# rfkill block bluetooth
# rfkill list bluetooth
3: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: yes
 Hard blocked: no

Bluetooth is deactivated now.

I added "rfkill block bluetooth" to /etc/rc.d/rc.local. During boot the bluetooth LED is active when the thinkpad_acpi module is loaded, but turns off, as soon as rc-local.service unit has been reached.

[Florian Stoll (flostoll)]

In Ubuntu 12.04 and 12.10 it worked fine on my Lenovo T500 but in 13.04 there seems to be a regression because it does not remember the last state of bluetooth device.

[beland (beland-redhat-bugs)]

*** Bug 911093 has been marked as a duplicate of this bug. ***

[Florian Stoll (flostoll)]

Since some time ago the last state is remembered after restart in 13.04 on my Lenovo T500. The icon in indicator menu is only visible if bluetooth is enabled...

[papukaija (papukaija)]

I can also confirm that the bluetooth status is remembered between reboots in Raring. Could the original reporter or someone else please confirrm this?

[Martin Albisetti (beuno)]

It doesn't seem to be remembered for me. I turn it off, reboot, and it's back on.

[pablomme (pablomme)]

Original reporter here. I've not had this problem for a long time (I've changed laptops since I reported it), and after the switch to indicator-bluetooth in raring things continue to work fine.

[Elias K Gardner (zorkerz)]

this has resurfaced for me in raring

On Sunday, April 14, 2013, pablomme wrote:

> Original reporter here. I've not had this problem for a long time (I've
> changed laptops since I reported it), and after the switch to indicator-
> bluetooth in raring things continue to work fine.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/446657
>
> Title:
> Bluetooth's on/off status doesn't update from the SetProperty D-Bus
> method that bluetoothd sends
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions
>

[papukaija (papukaija)]

I think it's better to keep this bug open. I've been using Raring for few weeks now and the bluetooth is sometimes (possibly after installing an updated kernel) enabled on boot after I've disabled it before shutting down.

[Daniel Aleksandersen (da2x)]

I have this problem with my Lenovo X1 running raring. I turn off Bluetooth, restart the machine, and voilà: it is back on and draining battery power. This happens every time. Sometimes I also see it being re-enabled after awakening from hibernation.

[mwp.junk (mwp.junk-redhat-bugs)]

I have two laptops running F18 and F19, complete installs, and both exhibit the same issue. The F18 laptop is a Dell XPS 17 (LX720x) with a 3.9.6 kernel and the F19 is a Dell Latitude D830 with 3.9.8 kernel.

Interacting with the top-bar bluetooth applet doesn't have any affect on the bluetooth led.

'sudo systemctl stop bluetooth.service' && 'sudo systemctl disable bluetooth.service' won't turn it off either despite 'sudo systemctl status bluetooth.service' saying it's dead (inactive) and the systemd journal showing bluetoothhd was stopped.

'sudo chkconfig --list | grep bluetooth' doesn't show it running and 'chkconfig bluetooth off' just forwards to systemctl disable bluetooth.service.

[hub+rhbz (hub+rhbz-redhat-bugs)]

You might want to refer to this upstream bug:

https://bugzilla.gnome.org/show_bug.cgi?id=638117

[bcotton (bcotton-redhat-bugs)]

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

[jpazdziora (jpazdziora-redhat-bugs)]

I currently have

#!/bin/bash
echo disable > /proc/acpi/ibm/bluetooth

in my /etc/rc.d/rc.local so I will no longer attempt to keep this bugzilla open for proper resolution. Someone else who still cares might want to pick up the flag.

[bcotton (bcotton-redhat-bugs)]

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

[jshubin (jshubin-redhat-bugs)]

Still present on F20, and annoying hackers everywhere :)

[mskinner (mskinner-redhat-bugs)]

I have a T530 - even though I have bluetooth disabled in the KDE settings, the /proc/acpi/ibm/bluetooth had it enabled.

I am running the latest BIOS as well.

[mskinner (mskinner-redhat-bugs)]

I have a T530 - even though I have bluetooth disabled in the KDE settings, the /proc/acpi/ibm/bluetooth had it enabled.

I'm running F20.

I am running the latest BIOS as well.

[sbonazzo (sbonazzo-redhat-bugs)]

Same here on F19 on T530.

[Jesse Michael (jesse.michael)]

It's kind of depressing that this bug is still not fixed four and a half years later in trusty.

[eminguez (eminguez-redhat-bugs)]

Systemctl workaround:

echo "w /proc/acpi/ibm/bluetooth - - - - disable" >> /etc/tmpfiles.d/disable-bluetooth.conf

[bnocera (bnocera-redhat-bugs)]

systemd is supposed to remember and restore rfkill status. If that doesn't work, it could be a problem with systemd's implementation, or with the kernel implementation of the device specific rfkill (the thinkpad_acpi module is known to be problematic).

Punting to systemd.

[Elijah Lynn (elijah-lynn)]

Yes, very depressing. This is why people use Macs.

But there is no way I am going to use a Mac's OS and this is free and open software so I would like to get to the bottom of this. I just read through this entire issue and https://bugzilla.gnome.org/show_bug.cgi?id=638117#c9 and it appears this is now a true upstream with gnome-bluetooth. It also appears to be related to those with an actual hardware wireless radio or bluetooth kill switch. This may explain why it works for certain people.

This is present in Ubuntu 14.04 with bluez 4.101-0ubuntu13 and gnome-bluetooth 3.8.2.1-0ubuntu4 and not sure it matters but I also have indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2.

I got this with a dpkg-query -l "*blue*" in case anyone else is wondering what
versions they are running.

ps. Possible duplicate here -> https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/280811

[htl10 (htl10-redhat-bugs)]

(In reply to Bastien Nocera from comment #32)
> systemd is supposed to remember and restore rfkill status. If that doesn't
> work, it could be a problem with systemd's implementation, or with the
> kernel implementation of the device specific rfkill (the thinkpad_acpi
> module is known to be problematic).
>
> Punting to systemd.

It is certainly not being remembered. FWIW, I have toshiba_bluetooth module; and I keep having to turn it off at the user-settings; it seems to be forgotten whenever reboot/logout.

[pspacek (pspacek-redhat-bugs)]

I confirm the same issue on T540 running latest Fedora 21.

[zeus (zeus-tunalkan)]

I'm on Ubuntu 14.04, a Toshiba Portégé Z830 with Atheros bluetooth, gnome-bluetooth v 3.8.2.1. I can confirrm I'm still experiencing this issue for the past two or three years. Never seen it solved. Bluetooth state always on after reboot. Indeed having to switch it off every time makes Ubuntu less user-friendly. If it's useful for someone, when I use KDE I don't have this problem. Only with Gnome (same Ubuntu and Mint),

[papukaija (papukaija)]

This bug should be fixed in Ubuntu 15.04, as it currently has systemd 215. The fix is in systemd 209, source: https://bugzilla.gnome.org/show_bug.cgi?id=638117#c50

[wgqiwt (wgqiwt-redhat-bugs)]

Same on lenovo w530 centos 6

[jshubin (jshubin-redhat-bugs)]

On Fedora 21.
Bluetooth is off.
Turn wifi switch off, then on.
Bluetooth turns itself on again!

Argghhh...

[beland (beland-redhat-bugs)]

According to https://bugzilla.gnome.org/show_bug.cgi?id=638117 systemd 209 fixes this for at least some hardware.

I can confirm this fix on Fedora 21 with my Macbook Air running systemd-216-24.fc21.x86_64; Bluetooth stays off after reboot if set that way. Also according to that external bug, there may be additional bugs in the hardware-specific kernel bluetooth drivers.

It sounds like if we want this fixed, then, we should report new hardware-specific bugs against the kernel. On my MacBook, "lsmod | grep rfkill" reports:

rfkill 21980 5 cfg80211,bluetooth

I also have a Lenovo ThinkPad running Fedora 19, and it lists users of rfkill as cfg80211,thinkpad_acpi,bluetooth. For those that are running Fedora 21 and seeing this problem still, what modules do you see there?

The upstream bug also mentions this as a manual workaround:

/etc/modprobe.d/rfkill.conf:

options rfkill master_switch_mode=0

[ledufff (ledufff-redhat-bugs)]

(In reply to James (purpleidea) from comment #36)
> On Fedora 21.
> Bluetooth is off.
> Turn wifi switch off, then on.
> Bluetooth turns itself on again!
>
> Argghhh...

I can reply this too in Fedora 22 (Cinnamon)

[jpazdziora (jpazdziora-redhat-bugs)]

Updating version based on comment 38.

[leigh123linux (leigh123linux-redhat-bugs)]

*** Bug 1240476 has been marked as a duplicate of this bug. ***

[jsynacek (jsynacek-redhat-bugs)]

*** Bug 1231423 has been marked as a duplicate of this bug. ***

[josephpfidler (josephpfidler-redhat-bugs)]

Just noticed this bug with Fedora 23 - Gnome 3.18.2.

Set Bluetooth to off in the Gnome Settings Bluetooth dialogue - reboot and that setting is forgotten and Bluetooth is turned on again. Same is true for the Bluetooth setting in the power settings dialog.

For me this creates an necessary power drain by having Bluetooth enabled when its not needed, and more importantly a potential security problem. Hardware is an Asus UX305LA laptop.

Cheers, Joe.

[mbrancaleoni (mbrancaleoni-redhat-bugs)]

same on fedora 24, branched release (updated as now).

calling it an Enhancement is a bit.... meh, but well.

[josephpfidler (josephpfidler-redhat-bugs)]

Yep - Not honoring a very noticeable user setting seems like a straight forward bug to me. And its now six year old.

I am happy to test fixes for this if it helps...

[mbrancaleoni (mbrancaleoni-redhat-bugs)]

right now issue bypassed with tlp and by setting

DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"

in /etc/default/tlp

not elegant, but 99.999% of time bluetooth is not really needed here.

[josephpfidler (josephpfidler-redhat-bugs)]

Its more elegant the the "rfkill block bluetooth" command I currently have in a startup script.
Thanks Matteo for your help.

[jsynacek (jsynacek-redhat-bugs)]

On Fedora 24, I can't reproduce this anymore.

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: no
 Hard blocked: no
2: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

After turning off bluetooth from the gnome menu:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: yes
 Hard blocked: no
2: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

After rebooting the machine, bluetooth is still soft blocked and appears as Off in the menu and bluetooth settings.

$ rpm -q gnome-shell bluez kernel
gnome-shell-3.20.0-1.fc24.x86_64
bluez-5.37-3.fc24.x86_64
kernel-4.5.0-301.fc24.x86_64

[josephpfidler (josephpfidler-redhat-bugs)]

Just re-tested this bug against my current setup - Fedora 23 with current updates. I do not see the issue as originally described - my Blutooth is staying off after a power-off. I am still working to see if I applied any of the work arounds, so that I can confirm if this is a valid result. I do see the issue after a suspend-resume event, but do know if that is relevant to this bug.

To re-create using suspend-resume I ...

1] Turn-off Blu-tooth using the Gnome menu (if its not already off). rfkill list shows:

1: asus-wlan: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: asus-bluetooth: Bluetooth
 Soft blocked: yes
 Hard blocked: no
3: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

2] suspend the machine - sudo systemctl suspend

3] Resume. Gnome indicator shows Blutooth enabled and I can see the laptop's blutooth from other devices. Rfkill list still shows:

1: asus-wlan: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: asus-bluetooth: Bluetooth
 Soft blocked: yes
 Hard blocked: no
3: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
4: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

rpm -q gnome-shell bluez kernel
gnome-shell-3.18.4-1.fc23.x86_64
bluez-5.36-1.fc23.x86_64
kernel-4.4.4-301.fc23.x86_64
kernel-4.4.5-300.fc23.x86_64
kernel-4.4.6-300.fc23.x86_64

So after the resume Blutooth has activated itself despite being configured not too. I noticed the second Blutooth device (hci0) that has appeared in the list and wonder if this is part the cause of the problem. I am out of the office next week - will try to load the F24 Alpha then and re-test against that.

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.

[bcotton (bcotton-redhat-bugs)]

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

[bugzilla (bugzilla-redhat-bugs)]

Same for F23

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/446657

[bcotton (bcotton-redhat-bugs)]

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

[hub+rhbz (hub+rhbz-redhat-bugs)]

Good news.
I haven't seen the problem is F24 and F25. Possibly fixed upstream.

[woiling (woiling-redhat-bugs)]

I still experience this behaviour on Fedora 24.

[htl10 (htl10-redhat-bugs)]

Argh, in my rc.local, I had it blocked by default:

/etc/rc.d/rc.local

rfkill block bluetooth

[woiling (woiling-redhat-bugs)]

It also still happens on Fedora 25 for me.

[josephpfidler (josephpfidler-redhat-bugs)]

Yep its still there. Just retested under F25 with current updates.

Turn off Bluetooth in the Gnome settings panel. Either a suspend-resume or power-off power-on will result in Bluetooth active.

I did see an error related to communication with my Bluetooth device (hci0) but have no idea if this is related to this error:

sudo dmesg | grep hci0
[ 3.692511] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 3.694466] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 3.830043] Bluetooth: hci0 sending frame failed (-19)
[ 5.865638] Bluetooth: hci0 command 0xfc8e tx timeout
[ 14.313764] Bluetooth: hci0 sending Intel patch command (0xfc8e) failed (-110)
[ 14.313889] Bluetooth: hci0 sending frame failed (-19)
[ 16.361767] Bluetooth: hci0 command 0xfc11 tx timeout
[ 16.361772] Bluetooth: hci0: Exiting manufacturer mode failed (-110)
[ 23.495554] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 23.495766] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 23.804611] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated

[spike speigel (frail-knight)]

For anyone who might find their way here while using newer versions of Ubuntu such as 16.04 LTS, 16.10, 17.04...

This might be the solution. Worked for me:

https://github.com/blueman-project/blueman/issues/682

[devidd05 (devidd05-redhat-bugs)]

I am experiencing the same thing again in Fedora 31 in Dell XPS 13 9350.

[updates (updates-redhat-bugs)]

FEDORA-2022-f38f479b8f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f38f479b8f