Bug 570073

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.

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 ...

(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.

(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.

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.

(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.

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

Flipping version to Fedora 13.

Same in F15!

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

The same issue in F16 on Sony Vaio VPCEB3B4R

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

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

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

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.

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?

Still the case in F18 beta.

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.

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.

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.

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

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.

You might want to refer to this upstream bug:

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

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.

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.

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.

Still present on F20, and annoying hackers everywhere :)

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.

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.

Same here on F19 on T530.

Systemctl workaround:

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

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.

(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.

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

Same on lenovo w530 centos 6

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

Argghhh...

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

(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)

Updating version based on comment 38.

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

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

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.

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

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

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...

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.

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

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

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.

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.

Same for F23

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.

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

I still experience this behaviour on Fedora 24.

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

/etc/rc.d/rc.local

rfkill block bluetooth

It also still happens on Fedora 25 for me.

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

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

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