[Bluetooth] starts automatically on start-up. No option in Settings to disable upon start-up and Bluetooth not listed in Start-up applications.

Bug #952036 reported by mwilkes512 on 2012-03-11
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Bluetooth Menu
indicator-bluetooth (Ubuntu)

Bug Description

Bluetooth starts automatically on start-up. No option in Settings to disable upon start-up and Bluetooth not listed in Start-up applications. Easy to disable but kind of a pain to have to do it at every start-up. Other than that Bluetooth works properly.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/952036/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Robert Roth (evfool) on 2012-03-12
affects: ubuntu → gnome-control-center (Ubuntu)
affects: gnome-control-center (Ubuntu) → bluez (Ubuntu)

Well, there is an easy way to disable bluetooth's daemon: you can disable the upstart job like any other via .override files for the job.

For lack of a better link, here's how that can be done: https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverviewUpstart#Override_files

Also, rfkill state should be carried over between restarts via the rfkill-store/rfkill-restore upstart jobs. Is it the rfkill state that you are interested in?

Changed in bluez (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired

So can this bug be re-activated? Imo this is not user friendly. Just allow users to disable Bluetooth in the top menu bar in the system preferences. That is what those are for actually and it is like an adult operating system should operate. Hope this gets added to ubuntu system preferences.

If Ubuntu wants bigger user adaption then make it user friendly. Simple as that.

Foss-4 (foss-4) wrote :

still an issue with 13.10. Very unprofessional. We need an easy nice UI option in the system preferences.

Changed in bluez (Ubuntu):
status: Expired → New
affects: bluez (Ubuntu) → ubuntu-ux
Daniela Ferrai (dferrai) on 2014-06-24
Changed in ubuntu-ux:
assignee: nobody → Matthew Paul Thomas (mpt)
summary: - Bluetooth starts automatically on start-up. No option in Settings to
+ [Bluetooth] starts automatically on start-up. No option in Settings to
disable upon start-up and Bluetooth not listed in Start-up applications.
Changed in ubuntu-ux:
status: New → Fix Released
status: Fix Released → Triaged
Michał Sawicz (saviq) on 2014-07-15
affects: unity8 → ubuntu-system-settings
John Lea (johnlea) on 2014-07-21
Changed in ubuntu-ux:
status: Triaged → New
importance: Undecided → Medium
John Lea (johnlea) on 2014-07-21
Changed in ubuntu-ux:
status: New → Triaged
Foss-4 (foss-4) wrote :

Isn't this already in 14.04? If so, why is it on "NEW" and not FIXED? Maybe I'm missing something?

ramgorur (code-icted) wrote :

This problem still exists in 14.04, on lenovo S431.

If I do "rfkill block bluetooth" or "echo disable > /proc/acpi/ibm/bluetooth" in rc.local the indicator app gets disappeared after startup.

Any work-around ?

Foss-4 (foss-4) wrote :

Well this WORKSFORME. And I still assume it's fixed.

I'd rather suggest that is you still have device specific problems with Bluetooth, to file a new bug for that specific problem. Because in 14.04 Bluetooth settings I turn off Bluetooth, restart machine, revisit Bluetooth settings and it's still off.

Also we finally have an UI option to remove bluetooth from the menubar.

Matthew Paul Thomas (mpt) wrote :

This is not a design bug: the Bluetooth on/off setting should persist across sessions, but the same is true for every setting in the OS, it doesn't require any extra specification.

no longer affects: ubuntu-ux
Foss-4 (foss-4) wrote :

Matthew: Can you translate this?

While what you write is true, it also is, what I experience under Ubuntu 14.04. So maybe it would be good to specify exactly what is not working as expected yet to let people understand why this bug is still on "NEW" and not "FIXED".

Matthew Paul Thomas (mpt) wrote :

Foss-4, I don't know whether this bug is currently reproducible. "New" is Launchpadese for "Unconfirmed", and nobody has yet described steps to reproduce the problem. Perhaps it occurs with some Bluetooth drivers and not others. My point was simply that regardless of whether it is still a problem, it is not a bug that requires any design changes. A setting for toggling Bluetooth on/off already exists, and that setting should be obeyed at startup just as much as at any other time.

Christian Dywan (kalikiana) wrote :

For me it's clearly still happening both on desktop and phone, so I don't think this is merely "some drivers".

no longer affects: ubuntu-system-settings
Jos van Houtem (jos-vh67) wrote :

For me it still happens randomly. Sometimes after a restart , bluetooth apperars to be "on".
But I can not find a way to reproduce it. Not a big problem for me though.

Launchpad Janitor (janitor) wrote :

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

Changed in indicator-bluetooth (Ubuntu):
status: New → Confirmed
Borim (borim) wrote :

I wonder when this bug will be fixed.

As the settings for network (WLAN and LAN) the settings for bluetooth should be persistent. When bluetooth is disabled, it should stay disabled until enabled again. Of course also over multiple sessions.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers