How can I deactivate Bluetooth on system startup?
How can I deactivate Bluetooth on system startup?
startup bluetooth services
|
show 10 more comments
How can I deactivate Bluetooth on system startup?
startup bluetooth services
I don't think that "should be the natural default configuration", people are bound to want to use Bluetooth on their computers without having to turn it on (you don't seem to have a Bluetooth mouse or keyboard, if those were your primary input devices you'd want Bluetooth on from boot). However I do agree that a way to choose how you want Bluetooth to be on boot would be useful to have.
– roadmr
May 4 '12 at 20:25
57
The normal and natural thing is to let you choose, in the bluetooth settings, whether you want it on or off when it boots. It is not natural to have people turning it off or on every time they turn on their computer. We are talking about making Linux the best desktop system, not the worst, aren't we?
– Robert
May 4 '12 at 20:30
We agree that letting people choose is the best option. See here for some possible ways of doing this. answers.launchpad.net/ubuntu/+source/bluez/+question/51440
– roadmr
May 4 '12 at 20:31
1
This is bug #1073669.
– colan
Jul 14 '15 at 20:44
3
It's kind of unbelievable that, on the 14th edition, we are still "teaching" Ubuntu developers things like "the option to have bluetooth on or off on boot should be available to normal users, and not just to those fond of searching in interminable lines of public forums".
– Rodrigo
Aug 28 '15 at 12:08
|
show 10 more comments
How can I deactivate Bluetooth on system startup?
startup bluetooth services
How can I deactivate Bluetooth on system startup?
startup bluetooth services
startup bluetooth services
edited Feb 1 '13 at 8:18
Flimm
21.7k1563122
21.7k1563122
asked Oct 16 '11 at 21:02
FloqqiFloqqi
1,5223103
1,5223103
I don't think that "should be the natural default configuration", people are bound to want to use Bluetooth on their computers without having to turn it on (you don't seem to have a Bluetooth mouse or keyboard, if those were your primary input devices you'd want Bluetooth on from boot). However I do agree that a way to choose how you want Bluetooth to be on boot would be useful to have.
– roadmr
May 4 '12 at 20:25
57
The normal and natural thing is to let you choose, in the bluetooth settings, whether you want it on or off when it boots. It is not natural to have people turning it off or on every time they turn on their computer. We are talking about making Linux the best desktop system, not the worst, aren't we?
– Robert
May 4 '12 at 20:30
We agree that letting people choose is the best option. See here for some possible ways of doing this. answers.launchpad.net/ubuntu/+source/bluez/+question/51440
– roadmr
May 4 '12 at 20:31
1
This is bug #1073669.
– colan
Jul 14 '15 at 20:44
3
It's kind of unbelievable that, on the 14th edition, we are still "teaching" Ubuntu developers things like "the option to have bluetooth on or off on boot should be available to normal users, and not just to those fond of searching in interminable lines of public forums".
– Rodrigo
Aug 28 '15 at 12:08
|
show 10 more comments
I don't think that "should be the natural default configuration", people are bound to want to use Bluetooth on their computers without having to turn it on (you don't seem to have a Bluetooth mouse or keyboard, if those were your primary input devices you'd want Bluetooth on from boot). However I do agree that a way to choose how you want Bluetooth to be on boot would be useful to have.
– roadmr
May 4 '12 at 20:25
57
The normal and natural thing is to let you choose, in the bluetooth settings, whether you want it on or off when it boots. It is not natural to have people turning it off or on every time they turn on their computer. We are talking about making Linux the best desktop system, not the worst, aren't we?
– Robert
May 4 '12 at 20:30
We agree that letting people choose is the best option. See here for some possible ways of doing this. answers.launchpad.net/ubuntu/+source/bluez/+question/51440
– roadmr
May 4 '12 at 20:31
1
This is bug #1073669.
– colan
Jul 14 '15 at 20:44
3
It's kind of unbelievable that, on the 14th edition, we are still "teaching" Ubuntu developers things like "the option to have bluetooth on or off on boot should be available to normal users, and not just to those fond of searching in interminable lines of public forums".
– Rodrigo
Aug 28 '15 at 12:08
I don't think that "should be the natural default configuration", people are bound to want to use Bluetooth on their computers without having to turn it on (you don't seem to have a Bluetooth mouse or keyboard, if those were your primary input devices you'd want Bluetooth on from boot). However I do agree that a way to choose how you want Bluetooth to be on boot would be useful to have.
– roadmr
May 4 '12 at 20:25
I don't think that "should be the natural default configuration", people are bound to want to use Bluetooth on their computers without having to turn it on (you don't seem to have a Bluetooth mouse or keyboard, if those were your primary input devices you'd want Bluetooth on from boot). However I do agree that a way to choose how you want Bluetooth to be on boot would be useful to have.
– roadmr
May 4 '12 at 20:25
57
57
The normal and natural thing is to let you choose, in the bluetooth settings, whether you want it on or off when it boots. It is not natural to have people turning it off or on every time they turn on their computer. We are talking about making Linux the best desktop system, not the worst, aren't we?
– Robert
May 4 '12 at 20:30
The normal and natural thing is to let you choose, in the bluetooth settings, whether you want it on or off when it boots. It is not natural to have people turning it off or on every time they turn on their computer. We are talking about making Linux the best desktop system, not the worst, aren't we?
– Robert
May 4 '12 at 20:30
We agree that letting people choose is the best option. See here for some possible ways of doing this. answers.launchpad.net/ubuntu/+source/bluez/+question/51440
– roadmr
May 4 '12 at 20:31
We agree that letting people choose is the best option. See here for some possible ways of doing this. answers.launchpad.net/ubuntu/+source/bluez/+question/51440
– roadmr
May 4 '12 at 20:31
1
1
This is bug #1073669.
– colan
Jul 14 '15 at 20:44
This is bug #1073669.
– colan
Jul 14 '15 at 20:44
3
3
It's kind of unbelievable that, on the 14th edition, we are still "teaching" Ubuntu developers things like "the option to have bluetooth on or off on boot should be available to normal users, and not just to those fond of searching in interminable lines of public forums".
– Rodrigo
Aug 28 '15 at 12:08
It's kind of unbelievable that, on the 14th edition, we are still "teaching" Ubuntu developers things like "the option to have bluetooth on or off on boot should be available to normal users, and not just to those fond of searching in interminable lines of public forums".
– Rodrigo
Aug 28 '15 at 12:08
|
show 10 more comments
30 Answers
30
active
oldest
votes
18.04+ users who don't naturally have a /etc/rc.local, you'll need to create one and make it executable. To make things slightly easier, you can just paste the following command into a terminal:
sudo install -b -m 755 /dev/stdin /etc/rc.local << EOF
#!/bin/sh
rfkill block bluetooth
exit 0
EOF
Run sudoedit /etc/rc.local
and add this before line with exit 0
:
rfkill block bluetooth
You should still be able to enable Bluetooth through the top bar applet.
This should work for most systems but it looks like there are a few bugs lurking in the kernel's ACPI for Thinkpads. If you're on a Thinkpad, add the following to /etc/rc.local
:
echo disable > /proc/acpi/ibm/bluetooth
Or check out ibm-acpi - IBM ThinkPad ACPI Extras Driver -- some reports suggest that ibm-acpi includes bluetooth control (amongst other nice things). But I don't have the hardware so I'm completely unable to verify these claims. Good luck.
6
For Thinkpads (and only Thinkpads) this works:echo disable > /proc/acpi/ibm/bluetooth
in /etc/rc.local
– Marius Gedminas
Nov 2 '11 at 19:51
4
rfkill block bluetooth
worked for Thinkpad T430u
– bmaupin
Nov 15 '13 at 16:47
5
Neither worked for me (ThinkPad x201) when I placed them one at a time in/etc/rc.local
. Therfkill block bluetooth
command does work, but not on startup. The -x flag is set on/etc/rc.local
. I'm running Xubuntu 13.10.
– Kyle Falconer
Dec 20 '13 at 7:34
4
On Ubuntu 15.10 with systemd you need some more to reenable the use of theetc/rc.local
file: askubuntu.com/a/696226/34298
– rubo77
Nov 10 '15 at 12:36
5
if our rc.local is just an empty file,where should we add 'rfkill block bluetooth'?
– Sss
Nov 25 '17 at 10:57
|
show 20 more comments
I found a how-to with a clean "workaround" here (archive link for posterity)
Actually changing /etc/bluetooth/main.conf
was enough for me.
From the article:
Search for the entry:
InitiallyPowered = true
and change the value to:
InitiallyPowered = false
It was enough for me, although the article describes some other steps that may or may not be necessary.
On Ubuntu 17.10 and Ubuntu 18.04 the option InitiallyPowered
has been replaced with AutoEnable
2
doesn't work for samsung laptop 530u3b, bluetooth is always on after reboot and wake up
– Maxim Kim
Aug 27 '12 at 18:51
3
This would only work if I also used Saeed Zarinfam's answer of putting/etc/init.d/bluetooth stop
in rc.local. It seems that when the service starts up, it also brings the power on for bluetooth. I needed both to get this to work. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:57
2
Didn't work for me on thinkpad t420
– UpTheCreek
May 10 '15 at 9:40
4
"Search for the entry" is of precisely no use to those of us whosemain.conf
does not contain this parameter or any comment indicating its default location. So, under which[Heading]
should we put it?
– underscore_d
Oct 30 '15 at 23:00
9
On my case it was AutoEnable=false, but anyways +1 for right solution from right place.
– Arman Petrosyan
Apr 20 '17 at 5:50
|
show 12 more comments
To disable the bluetooth driver from loading on startup:
sudo $EDITOR /etc/modprobe.d/blacklist.conf
add:
blacklist btusb
Enabling it later should just be:
sudo modprobe btusb
1
Thanks for that, that does seem to work but I was trying to avoid command line stuff as per my original question. You would think this would be as simple as ticking a box so that it remembered that I don't want BT to start automatically but it looks like its way more complicated than that. With Ubuntu's drive for quicker boot times and the general focus on power consumption in laptops and netbooks I am suprised that this has never been addressed. I appreciate the help though.
– Chris Giltnane
Aug 19 '10 at 9:52
9
"Run gedit as root and edit /etc/modprobe.d/blacklist.conf" <-- ok, is that less command line for ya?
– maco
Aug 19 '10 at 13:35
1
Works fine on Samsung Q35 with Ubuntu 13.10, while the 'rfkill block bluetooth' approach does not. Thanks!
– user27164
Jan 6 '14 at 8:29
DELL E6410 works for me. Good that can run again on the go without reset.
– Ruslan Gerasimov
Jun 13 '14 at 10:24
Don't bother trying to "avoid command line stuff" when you are configuring the operating system. Is Ctrl+Alt+T and a couple of ctrl-shift-V (to paste) too much to ask?
– doug65536
Aug 8 '16 at 0:15
|
show 1 more comment
Step 1: Go to the terminal and type in the following command to edit system's /etc/rc.local
file:
gksudo gedit /etc/rc.local
Step 2: Add the following line before the exit 0
line:
rfkill block bluetooth
1
This is set soft block to bluetooth, I think it same as turn off its service and works well.
– Smile.Hunter
Aug 17 '12 at 13:45
@Robert:$ man rfkill
: "Disable the device corresponding to the given index." Despite the name, it is only disabling BT; just try the commandrfkill block bluetooth
on the terminal, you should see the icon go gray.
– Daniel
Jun 13 '15 at 17:54
add a comment |
From ubuntu 16.04 onwards systemd manages startup services like bluetooth ... to view current status issue following in a terminal
sudo systemctl status bluetooth.service
to deactivate bluetooth on startup issue this
sudo systemctl disable bluetooth.service
then on next reboot bluetooth will not be active ... to enable bluetooth issue
sudo systemctl enable bluetooth.service
2
This works for me, but as a side effect, blueman-applet stoppped to work too. It starts, but doesn't appear in the indicator area, so there is no fast way to enable bluetooth, only in terminal.
– Yuri Gor
Sep 2 '17 at 21:02
In Xubuntu, at least, if you click on Blueman, it has the option of "Turn Bluetooth Off". I think this is what the OP would like automated. Your solution removes Blueman altogether, making it harder to re-enable Bluetooth if desired.
– Adrian Keister
Jan 30 '18 at 14:08
1
Put sudo systemctl disable bluetooth.service && sudo systemctl stop bluetooth.service into a Disable script, and chmod 755 on it. Do the same for sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service in an Enable script.
– Adrian Keister
Jan 30 '18 at 14:33
FINALLY! Ubuntu 18.10, the only thing that worked for me. Nothing else worked.
– Tyler
Feb 18 at 13:02
add a comment |
Type the following into a terminal:
sudo gedit /etc/modprobe.d/blacklist.conf
At the bottom of the file, add the line:
blacklist bluetooth
Save the file and restart - Bluetooth should now be disabled.
This won't work on my pc...
– Floqqi
Oct 16 '11 at 21:47
@Floqqi: Can you please try it again? I've updated my answer.
– Nathan Osman
Oct 16 '11 at 23:42
2
Tried about 20 things on my ubuntu 12 thinkpad, this is the only one that did the trick.
– OlivierBlanvillain
Sep 12 '13 at 16:57
add a comment |
You can change the services started at boot with the help of BUM.
Install it: sudo apt-get install bum
Run: sudo bum
Uncheck the box and click Apply.
Thank you, desgua, I was thinking about this kind of tools. I have used some in the past but they become obsolete and the new ubuntu, with their minimalistic obsession, comes with nothing of the kind. Is this the only yo know or the best yo know?
– Robert
May 5 '12 at 0:15
1
Maybe works but at first it has disappointed me because it started showing the bluetooth as not activated at boot time, why? and as not running when rfkill, the applet and hciconfig show it running. I turn off and on but bum continues showing the service as off. I activated the service at boot-up but the status of the service continues to be wrong.
– Robert
May 5 '12 at 1:26
sorry doesn't work on elementaryOS Freya
– Hoang Tran
Jul 9 '16 at 13:31
I get lots of "use of uninitialized value" warnings when it runs. Sorry, can't trust that.
– doug65536
Aug 8 '16 at 0:21
Now, the package is not available. It say, Bum is virtual.
– Satya Prakash
Jul 26 '17 at 19:27
|
show 2 more comments
1. block bluetooth in rc.local
Add this line at the end of the file /etc/rc.local
right before the line exit 0
:
rfkill block bluetooth
This will do the trick, but only in older Ubuntu versions using upstart.
2. reenable rc.local on systemd
On Ubuntu 15.10 with systemd as startup manager the /etc/rc.local
file is not used by default any more, so call this on a terminal:
sudo systemctl edit --full rc-local
Which opens an editor. At the end of the file i added:
[Install]
WantedBy=multi-user.target
Those changes are activated by
sudo systemctl reenable rc-local
Now the file /etc/rc.local
is used as you know it.
3. disable blueman-applet on start
sudo sed -i 's/NoDisplay=true/NoDisplay=false/g' /etc/xdg/autostart/blueman.desktop
gnome-session-properties
Now blueman-applet is visible and you can disable it from startup programs
4. Reboot to see the effect
3
For me on Ubuntu 17.04 with blueman:gsettings set org.blueman.plugins.powermanager auto-power-on false
worked, from wiki.archlinux.org/index.php/Blueman. Although I ended up doingsudo apt remove blueman
then manage bluetooth through system settings and check "Show Bluetooth status in the menu bar". Blueman starting and turning on bluetooth was the issue.
– Michael Jackson
Sep 28 '17 at 14:29
add a comment |
I think that the best way is to disable the service from being started in the first place. There is a general method for disabling services which works perfectly:
sudo sh -c "echo 'manual' > /etc/init/bluetooth.override"
That works for Ubuntu 13.10 and probably for earlier versions as well.
how to turn on bluetooth, while using provided settings later on? say I want to use it just for 5 min. every 10 boots..
– b1r3k
Oct 10 '15 at 14:51
add a comment |
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
This removed the bluetooth tray icon but left my bluetooth indicator light on (indicating power was still being sent to the radio). Edit: this in conjunction with Stepbaer's answer (InitiallyPowered = false
) worked for me. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:59
this did not work on my 64-bit Ubuntu 14.04 dell inspiron. Only rfkill worked for me.
– faizal
Jun 17 '14 at 7:19
add a comment |
You can edit your update-rc.d
settings. I used something similar to:
sudo update-rc.d bluetooth remove
In Debian Wheezy. Check out man update-rc.d
for more info on how to use it.
add a comment |
Maybe you can turn it off in the Startup Applications.
But these applications are hidden by default.
Unhide the hidden Startup Applications in 12.04: Open the terminal and run these two commands:
cd /etc/xdg/autostart/
sudo sed --in-place 's/NoDisplay=true/NoDisplay=false/g' *.desktop
Now you can uncheck bluetooth. (Don't remove!)
Bluetooth is not listed among these applications, sadly.
– pfctdayelise
Jul 10 '15 at 12:11
add a comment |
No. It is not always in the startup applcations list. I think that the best solution is to add the rfkill command in rc.local script or to set the InitiallyPowered
parameter in /etc/bluetooth/main.conf
.
1
InitiallyPowered seems to be ignored for me.
– UpTheCreek
May 10 '15 at 9:42
add a comment |
1) Install the package smbios-utils and add it to Startup Applications with:
sudo smbios-wireless-ctl --bt 0
2) In terminal type:
sudo visudo
and add to the end of opened file /etc/sudoers
the line:
<your username> ALL = NOPASSWD: /usr/sbin/smbios-wireless-ctl
3) To switch bluetooth on during session, run in terminal:
sudo smbios-wireless-ctl --bt 1
This works for me on my Dell D630 with Ubuntu 13.10
Do you think thatsudo smbios-wireless-ctl --boot --bt 0
would work? Also, I'm not sure, but this may be Dell-specific.
– Hitechcomputergeek
May 2 '15 at 18:48
Actually, the package smbios-utils performs bios commands, so it switches on and off physical devices related to bios, so you may also use it to switch on and off wifi etc. I'm not sure if it works with any bios or not. At least, it works well with Dell. By the way, the last installations of Ubuntu 14.04 do same things with bluetooth and wifi applets, so I don't need any more in that package.
– victor
May 3 '15 at 19:22
I knew that. But if you dosmbios-wireless-ctl --help
, part of it has--boot Set BIOS boot-time setting.
I didn't know they fixed the Bluetooth, though; thanks for telling me.
– Hitechcomputergeek
May 4 '15 at 21:29
add a comment |
On Ubuntu 16.04, I simply disabled the service from starting up using systemctl.
To do this, open up a terminal window and type the following:
sudo systemctl disable bluetooth
You can either reboot since now bluetooth will be disabled from starting up, or if you do not want to reboot and want to stop bluetooth right away, you can type:
sudo service bluetooth stop
add a comment |
We can disable bluetooth auto start this way:
sudo gedit /etc/bluetooth/main.conf
(gedit
is my fav editor, you can replace this with xed
or whatever that's installed on your system.)
At the very bottom of this file, there's this line:
#AutoEnable=false
Un-comment it, like this:
AutoEnable=false
doesn't work in ubuntu budgie 18.04
– Argento
Sep 3 '18 at 13:27
add a comment |
If you're using the Bluetooth applet in the top panel (blueman-applet), it has its own setting that will automatically turn Bluetooth on even if you've disabled it in other places (like /etc/bluetooth/main.conf or /etc/default/tlp).
To prevent Bluetooth from turning on at startup using the command line:
gsettings set org.blueman.plugins.powermanager auto-power-on false
Or through the GUI:
- Click the Bluetooth applet > Plugins > PowerManager > Configuration
- Uncheck Auto power-on
Next time you reboot, the Bluetooth applet will still be visible but Bluetooth will be off. To turn it on:
Click the Bluetooth applet > Turn Bluetooth On
In Ubuntu 18.04 this is the only solution I have found. Even if you change in /etc/bluetooth/main.conf, at the bottom, the option from AutoEnable=true to AutoEnable=false you cannot turn off the Bluetooth. In fact this option is for discovering new devices not for powering Bluetooth on or off.
– Alessandro D'lncal
Aug 19 '18 at 12:26
add a comment |
I using Sputnik Kernel, which fixed this on my Dell Inspiron 14R N4110.
add a comment |
I think you should edit
/etc/default/bluetooth
and set
BLUETOOTH_ENABLED=0
to disable the bluetooth service at boot
1
did not work on Ubuntu 14.04
– b1r3k
Sep 27 '15 at 17:28
add a comment |
For those of you where inserting the line rfkill block bluetooth
(or any other) in /etc/rc.local
doesn't work, try to include the same line in the end of ~/.bashrc
In my set up (Ubuntu 14.04, Thinkpad W540), no option worked inserting it in /etc/rc.local
but the former did work in bashrc. Note this will work just for the current user, not globally for all users.
add a comment |
On Ubuntu Studio 16.04 you can disable Bluetooth Applet in Startup in:
Session and Startup > Application Autostart > Bluetooth Applet
Here you can click in the field to disable it.
This is a perfectly good solution on my Xubuntu 17.10 machine, except for one thing: if the user wants to start using bluetooth again on the fly, he needs to execute sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service. But your solution definitely solves the bootup problem.
– Adrian Keister
Jan 30 '18 at 14:52
add a comment |
Since Ubuntu 18.04 (with GNOME) you need to
Edit /etc/bluetooth/main.conf and find
AutoEnable = true
and change the value to:
AutoEnable = false
So this device is not powered on startup.
Edit /etc/default/tlp and find:
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit this line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
So this device is disabled on startup.
Then open Dash and search for "Startup Applications". Uncheck any items related to Bluetooth in the list. Click [Close] to save.
Point 4: Go to Settings -> Bluetooth -> Disable (at top right window).
– Omar Tariq
Jan 27 at 6:43
add a comment |
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
add a comment |
Solution for my notebook
"BIOS - USB Configuration - EHCI2 : Disabled"
EHCI1 is for usb ports (actually My notebook has 2 usb 2.0 ports)
add a comment |
Edit /etc/default/grub
:
sudo nano /etc/default/grub
and change the following line:
GRUB_CMDLINE_LINUX=""
to say this instead:
GRUB_CMDLINE_LINUX="bluetooth.blacklist=yes"
Then, update grub and reboot:
sudo update-grub
add a comment |
This should disable bluetooth from starting on Debian based systems:
sudo chkconfig bluetooth off
or on RedHat based systems
systemctl disable bluetooth.service
add a comment |
I found another answer using tlp that works great for me with Ubuntu 18.04. Probably first tlp must be installed with
sudo apt install tlp
Then the file
/etc/default/tlp
contains some settings about devices like wifi and bluetooth. There is the key
RESTORE_DEVICE_STATE_ON_STARTUP
which is by default set to 0. After I switched it to 1 my last setting is remembered on the next boot. That means when I disable bluetooth in the top panel it stays disabled and when I enable bluetooth it stays enabled. Also there is the key
DEVICES_TO_DISABLE_ON_STARTUP
which can be set to
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
Now bluetooth will be disabled on each boot. After changing this configuration bluetooth will can be enabled and disabled through menu and panel item. I think it's better than removing it from kernel modules.
TLP is not installed by default in Ubuntu. You should update your post accordingly.
– linrunner
Feb 11 at 17:07
@linrunner Ok, didn't know what that. I tested on a fresh Ubuntu Budgie from Tuxedo. There it worked. I fixed my answer.
– Thomas Sablik
Feb 11 at 18:07
add a comment |
I had to use a brute-force method to stop bluetoothd from being automatically started at boot. I renamed the executable so it couldn't be found.
It's faster starting things in parallel. At least that's the idea.
– Douglas Leeder
Sep 28 '12 at 13:48
add a comment |
You can also use this Graphic application that also does this bluetooth manager
add a comment |
You need to disable it from the Start Up Applications list in System Settings.
Click on the cog in the top right hand side of the menu bar and then select System Settings.
Click on Start Up Applications then scroll down until you find the bluetooth setting, take the tick from the box and you all done.
2
I can't find bluetooth in the Start Up Applications..
– Floqqi
Oct 16 '11 at 21:40
5
That doesn't actually stop the Bluetooth subsystems and hardware from running (and importantly: consuming battery). It just stops the applet running.
– Oli♦
Oct 16 '11 at 23:59
@Oli - thanks for the heads up, I never actually knew that ! I assumed if you disabled it in the start up applications it did not start the process at all.
– Mark Rooney
Oct 17 '11 at 9:44
1
Sadly, it's not in the startup applications in 11.10.
– Amanda
Jan 28 '12 at 1:24
add a comment |
protected by Community♦ Oct 15 '14 at 14:26
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
30 Answers
30
active
oldest
votes
30 Answers
30
active
oldest
votes
active
oldest
votes
active
oldest
votes
18.04+ users who don't naturally have a /etc/rc.local, you'll need to create one and make it executable. To make things slightly easier, you can just paste the following command into a terminal:
sudo install -b -m 755 /dev/stdin /etc/rc.local << EOF
#!/bin/sh
rfkill block bluetooth
exit 0
EOF
Run sudoedit /etc/rc.local
and add this before line with exit 0
:
rfkill block bluetooth
You should still be able to enable Bluetooth through the top bar applet.
This should work for most systems but it looks like there are a few bugs lurking in the kernel's ACPI for Thinkpads. If you're on a Thinkpad, add the following to /etc/rc.local
:
echo disable > /proc/acpi/ibm/bluetooth
Or check out ibm-acpi - IBM ThinkPad ACPI Extras Driver -- some reports suggest that ibm-acpi includes bluetooth control (amongst other nice things). But I don't have the hardware so I'm completely unable to verify these claims. Good luck.
6
For Thinkpads (and only Thinkpads) this works:echo disable > /proc/acpi/ibm/bluetooth
in /etc/rc.local
– Marius Gedminas
Nov 2 '11 at 19:51
4
rfkill block bluetooth
worked for Thinkpad T430u
– bmaupin
Nov 15 '13 at 16:47
5
Neither worked for me (ThinkPad x201) when I placed them one at a time in/etc/rc.local
. Therfkill block bluetooth
command does work, but not on startup. The -x flag is set on/etc/rc.local
. I'm running Xubuntu 13.10.
– Kyle Falconer
Dec 20 '13 at 7:34
4
On Ubuntu 15.10 with systemd you need some more to reenable the use of theetc/rc.local
file: askubuntu.com/a/696226/34298
– rubo77
Nov 10 '15 at 12:36
5
if our rc.local is just an empty file,where should we add 'rfkill block bluetooth'?
– Sss
Nov 25 '17 at 10:57
|
show 20 more comments
18.04+ users who don't naturally have a /etc/rc.local, you'll need to create one and make it executable. To make things slightly easier, you can just paste the following command into a terminal:
sudo install -b -m 755 /dev/stdin /etc/rc.local << EOF
#!/bin/sh
rfkill block bluetooth
exit 0
EOF
Run sudoedit /etc/rc.local
and add this before line with exit 0
:
rfkill block bluetooth
You should still be able to enable Bluetooth through the top bar applet.
This should work for most systems but it looks like there are a few bugs lurking in the kernel's ACPI for Thinkpads. If you're on a Thinkpad, add the following to /etc/rc.local
:
echo disable > /proc/acpi/ibm/bluetooth
Or check out ibm-acpi - IBM ThinkPad ACPI Extras Driver -- some reports suggest that ibm-acpi includes bluetooth control (amongst other nice things). But I don't have the hardware so I'm completely unable to verify these claims. Good luck.
6
For Thinkpads (and only Thinkpads) this works:echo disable > /proc/acpi/ibm/bluetooth
in /etc/rc.local
– Marius Gedminas
Nov 2 '11 at 19:51
4
rfkill block bluetooth
worked for Thinkpad T430u
– bmaupin
Nov 15 '13 at 16:47
5
Neither worked for me (ThinkPad x201) when I placed them one at a time in/etc/rc.local
. Therfkill block bluetooth
command does work, but not on startup. The -x flag is set on/etc/rc.local
. I'm running Xubuntu 13.10.
– Kyle Falconer
Dec 20 '13 at 7:34
4
On Ubuntu 15.10 with systemd you need some more to reenable the use of theetc/rc.local
file: askubuntu.com/a/696226/34298
– rubo77
Nov 10 '15 at 12:36
5
if our rc.local is just an empty file,where should we add 'rfkill block bluetooth'?
– Sss
Nov 25 '17 at 10:57
|
show 20 more comments
18.04+ users who don't naturally have a /etc/rc.local, you'll need to create one and make it executable. To make things slightly easier, you can just paste the following command into a terminal:
sudo install -b -m 755 /dev/stdin /etc/rc.local << EOF
#!/bin/sh
rfkill block bluetooth
exit 0
EOF
Run sudoedit /etc/rc.local
and add this before line with exit 0
:
rfkill block bluetooth
You should still be able to enable Bluetooth through the top bar applet.
This should work for most systems but it looks like there are a few bugs lurking in the kernel's ACPI for Thinkpads. If you're on a Thinkpad, add the following to /etc/rc.local
:
echo disable > /proc/acpi/ibm/bluetooth
Or check out ibm-acpi - IBM ThinkPad ACPI Extras Driver -- some reports suggest that ibm-acpi includes bluetooth control (amongst other nice things). But I don't have the hardware so I'm completely unable to verify these claims. Good luck.
18.04+ users who don't naturally have a /etc/rc.local, you'll need to create one and make it executable. To make things slightly easier, you can just paste the following command into a terminal:
sudo install -b -m 755 /dev/stdin /etc/rc.local << EOF
#!/bin/sh
rfkill block bluetooth
exit 0
EOF
Run sudoedit /etc/rc.local
and add this before line with exit 0
:
rfkill block bluetooth
You should still be able to enable Bluetooth through the top bar applet.
This should work for most systems but it looks like there are a few bugs lurking in the kernel's ACPI for Thinkpads. If you're on a Thinkpad, add the following to /etc/rc.local
:
echo disable > /proc/acpi/ibm/bluetooth
Or check out ibm-acpi - IBM ThinkPad ACPI Extras Driver -- some reports suggest that ibm-acpi includes bluetooth control (amongst other nice things). But I don't have the hardware so I'm completely unable to verify these claims. Good luck.
edited Aug 7 '18 at 9:26
answered Aug 18 '10 at 9:00
Oli♦Oli
223k89565765
223k89565765
6
For Thinkpads (and only Thinkpads) this works:echo disable > /proc/acpi/ibm/bluetooth
in /etc/rc.local
– Marius Gedminas
Nov 2 '11 at 19:51
4
rfkill block bluetooth
worked for Thinkpad T430u
– bmaupin
Nov 15 '13 at 16:47
5
Neither worked for me (ThinkPad x201) when I placed them one at a time in/etc/rc.local
. Therfkill block bluetooth
command does work, but not on startup. The -x flag is set on/etc/rc.local
. I'm running Xubuntu 13.10.
– Kyle Falconer
Dec 20 '13 at 7:34
4
On Ubuntu 15.10 with systemd you need some more to reenable the use of theetc/rc.local
file: askubuntu.com/a/696226/34298
– rubo77
Nov 10 '15 at 12:36
5
if our rc.local is just an empty file,where should we add 'rfkill block bluetooth'?
– Sss
Nov 25 '17 at 10:57
|
show 20 more comments
6
For Thinkpads (and only Thinkpads) this works:echo disable > /proc/acpi/ibm/bluetooth
in /etc/rc.local
– Marius Gedminas
Nov 2 '11 at 19:51
4
rfkill block bluetooth
worked for Thinkpad T430u
– bmaupin
Nov 15 '13 at 16:47
5
Neither worked for me (ThinkPad x201) when I placed them one at a time in/etc/rc.local
. Therfkill block bluetooth
command does work, but not on startup. The -x flag is set on/etc/rc.local
. I'm running Xubuntu 13.10.
– Kyle Falconer
Dec 20 '13 at 7:34
4
On Ubuntu 15.10 with systemd you need some more to reenable the use of theetc/rc.local
file: askubuntu.com/a/696226/34298
– rubo77
Nov 10 '15 at 12:36
5
if our rc.local is just an empty file,where should we add 'rfkill block bluetooth'?
– Sss
Nov 25 '17 at 10:57
6
6
For Thinkpads (and only Thinkpads) this works:
echo disable > /proc/acpi/ibm/bluetooth
in /etc/rc.local– Marius Gedminas
Nov 2 '11 at 19:51
For Thinkpads (and only Thinkpads) this works:
echo disable > /proc/acpi/ibm/bluetooth
in /etc/rc.local– Marius Gedminas
Nov 2 '11 at 19:51
4
4
rfkill block bluetooth
worked for Thinkpad T430u– bmaupin
Nov 15 '13 at 16:47
rfkill block bluetooth
worked for Thinkpad T430u– bmaupin
Nov 15 '13 at 16:47
5
5
Neither worked for me (ThinkPad x201) when I placed them one at a time in
/etc/rc.local
. The rfkill block bluetooth
command does work, but not on startup. The -x flag is set on /etc/rc.local
. I'm running Xubuntu 13.10.– Kyle Falconer
Dec 20 '13 at 7:34
Neither worked for me (ThinkPad x201) when I placed them one at a time in
/etc/rc.local
. The rfkill block bluetooth
command does work, but not on startup. The -x flag is set on /etc/rc.local
. I'm running Xubuntu 13.10.– Kyle Falconer
Dec 20 '13 at 7:34
4
4
On Ubuntu 15.10 with systemd you need some more to reenable the use of the
etc/rc.local
file: askubuntu.com/a/696226/34298– rubo77
Nov 10 '15 at 12:36
On Ubuntu 15.10 with systemd you need some more to reenable the use of the
etc/rc.local
file: askubuntu.com/a/696226/34298– rubo77
Nov 10 '15 at 12:36
5
5
if our rc.local is just an empty file,where should we add 'rfkill block bluetooth'?
– Sss
Nov 25 '17 at 10:57
if our rc.local is just an empty file,where should we add 'rfkill block bluetooth'?
– Sss
Nov 25 '17 at 10:57
|
show 20 more comments
I found a how-to with a clean "workaround" here (archive link for posterity)
Actually changing /etc/bluetooth/main.conf
was enough for me.
From the article:
Search for the entry:
InitiallyPowered = true
and change the value to:
InitiallyPowered = false
It was enough for me, although the article describes some other steps that may or may not be necessary.
On Ubuntu 17.10 and Ubuntu 18.04 the option InitiallyPowered
has been replaced with AutoEnable
2
doesn't work for samsung laptop 530u3b, bluetooth is always on after reboot and wake up
– Maxim Kim
Aug 27 '12 at 18:51
3
This would only work if I also used Saeed Zarinfam's answer of putting/etc/init.d/bluetooth stop
in rc.local. It seems that when the service starts up, it also brings the power on for bluetooth. I needed both to get this to work. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:57
2
Didn't work for me on thinkpad t420
– UpTheCreek
May 10 '15 at 9:40
4
"Search for the entry" is of precisely no use to those of us whosemain.conf
does not contain this parameter or any comment indicating its default location. So, under which[Heading]
should we put it?
– underscore_d
Oct 30 '15 at 23:00
9
On my case it was AutoEnable=false, but anyways +1 for right solution from right place.
– Arman Petrosyan
Apr 20 '17 at 5:50
|
show 12 more comments
I found a how-to with a clean "workaround" here (archive link for posterity)
Actually changing /etc/bluetooth/main.conf
was enough for me.
From the article:
Search for the entry:
InitiallyPowered = true
and change the value to:
InitiallyPowered = false
It was enough for me, although the article describes some other steps that may or may not be necessary.
On Ubuntu 17.10 and Ubuntu 18.04 the option InitiallyPowered
has been replaced with AutoEnable
2
doesn't work for samsung laptop 530u3b, bluetooth is always on after reboot and wake up
– Maxim Kim
Aug 27 '12 at 18:51
3
This would only work if I also used Saeed Zarinfam's answer of putting/etc/init.d/bluetooth stop
in rc.local. It seems that when the service starts up, it also brings the power on for bluetooth. I needed both to get this to work. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:57
2
Didn't work for me on thinkpad t420
– UpTheCreek
May 10 '15 at 9:40
4
"Search for the entry" is of precisely no use to those of us whosemain.conf
does not contain this parameter or any comment indicating its default location. So, under which[Heading]
should we put it?
– underscore_d
Oct 30 '15 at 23:00
9
On my case it was AutoEnable=false, but anyways +1 for right solution from right place.
– Arman Petrosyan
Apr 20 '17 at 5:50
|
show 12 more comments
I found a how-to with a clean "workaround" here (archive link for posterity)
Actually changing /etc/bluetooth/main.conf
was enough for me.
From the article:
Search for the entry:
InitiallyPowered = true
and change the value to:
InitiallyPowered = false
It was enough for me, although the article describes some other steps that may or may not be necessary.
On Ubuntu 17.10 and Ubuntu 18.04 the option InitiallyPowered
has been replaced with AutoEnable
I found a how-to with a clean "workaround" here (archive link for posterity)
Actually changing /etc/bluetooth/main.conf
was enough for me.
From the article:
Search for the entry:
InitiallyPowered = true
and change the value to:
InitiallyPowered = false
It was enough for me, although the article describes some other steps that may or may not be necessary.
On Ubuntu 17.10 and Ubuntu 18.04 the option InitiallyPowered
has been replaced with AutoEnable
edited Jun 9 '18 at 15:01
Mehrad Mahmoudian
255415
255415
answered Jun 25 '12 at 18:00
StepbaerStepbaer
98762
98762
2
doesn't work for samsung laptop 530u3b, bluetooth is always on after reboot and wake up
– Maxim Kim
Aug 27 '12 at 18:51
3
This would only work if I also used Saeed Zarinfam's answer of putting/etc/init.d/bluetooth stop
in rc.local. It seems that when the service starts up, it also brings the power on for bluetooth. I needed both to get this to work. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:57
2
Didn't work for me on thinkpad t420
– UpTheCreek
May 10 '15 at 9:40
4
"Search for the entry" is of precisely no use to those of us whosemain.conf
does not contain this parameter or any comment indicating its default location. So, under which[Heading]
should we put it?
– underscore_d
Oct 30 '15 at 23:00
9
On my case it was AutoEnable=false, but anyways +1 for right solution from right place.
– Arman Petrosyan
Apr 20 '17 at 5:50
|
show 12 more comments
2
doesn't work for samsung laptop 530u3b, bluetooth is always on after reboot and wake up
– Maxim Kim
Aug 27 '12 at 18:51
3
This would only work if I also used Saeed Zarinfam's answer of putting/etc/init.d/bluetooth stop
in rc.local. It seems that when the service starts up, it also brings the power on for bluetooth. I needed both to get this to work. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:57
2
Didn't work for me on thinkpad t420
– UpTheCreek
May 10 '15 at 9:40
4
"Search for the entry" is of precisely no use to those of us whosemain.conf
does not contain this parameter or any comment indicating its default location. So, under which[Heading]
should we put it?
– underscore_d
Oct 30 '15 at 23:00
9
On my case it was AutoEnable=false, but anyways +1 for right solution from right place.
– Arman Petrosyan
Apr 20 '17 at 5:50
2
2
doesn't work for samsung laptop 530u3b, bluetooth is always on after reboot and wake up
– Maxim Kim
Aug 27 '12 at 18:51
doesn't work for samsung laptop 530u3b, bluetooth is always on after reboot and wake up
– Maxim Kim
Aug 27 '12 at 18:51
3
3
This would only work if I also used Saeed Zarinfam's answer of putting
/etc/init.d/bluetooth stop
in rc.local. It seems that when the service starts up, it also brings the power on for bluetooth. I needed both to get this to work. (ThinkPad x201, Xubuntu 13.10)– Kyle Falconer
Dec 20 '13 at 7:57
This would only work if I also used Saeed Zarinfam's answer of putting
/etc/init.d/bluetooth stop
in rc.local. It seems that when the service starts up, it also brings the power on for bluetooth. I needed both to get this to work. (ThinkPad x201, Xubuntu 13.10)– Kyle Falconer
Dec 20 '13 at 7:57
2
2
Didn't work for me on thinkpad t420
– UpTheCreek
May 10 '15 at 9:40
Didn't work for me on thinkpad t420
– UpTheCreek
May 10 '15 at 9:40
4
4
"Search for the entry" is of precisely no use to those of us whose
main.conf
does not contain this parameter or any comment indicating its default location. So, under which [Heading]
should we put it?– underscore_d
Oct 30 '15 at 23:00
"Search for the entry" is of precisely no use to those of us whose
main.conf
does not contain this parameter or any comment indicating its default location. So, under which [Heading]
should we put it?– underscore_d
Oct 30 '15 at 23:00
9
9
On my case it was AutoEnable=false, but anyways +1 for right solution from right place.
– Arman Petrosyan
Apr 20 '17 at 5:50
On my case it was AutoEnable=false, but anyways +1 for right solution from right place.
– Arman Petrosyan
Apr 20 '17 at 5:50
|
show 12 more comments
To disable the bluetooth driver from loading on startup:
sudo $EDITOR /etc/modprobe.d/blacklist.conf
add:
blacklist btusb
Enabling it later should just be:
sudo modprobe btusb
1
Thanks for that, that does seem to work but I was trying to avoid command line stuff as per my original question. You would think this would be as simple as ticking a box so that it remembered that I don't want BT to start automatically but it looks like its way more complicated than that. With Ubuntu's drive for quicker boot times and the general focus on power consumption in laptops and netbooks I am suprised that this has never been addressed. I appreciate the help though.
– Chris Giltnane
Aug 19 '10 at 9:52
9
"Run gedit as root and edit /etc/modprobe.d/blacklist.conf" <-- ok, is that less command line for ya?
– maco
Aug 19 '10 at 13:35
1
Works fine on Samsung Q35 with Ubuntu 13.10, while the 'rfkill block bluetooth' approach does not. Thanks!
– user27164
Jan 6 '14 at 8:29
DELL E6410 works for me. Good that can run again on the go without reset.
– Ruslan Gerasimov
Jun 13 '14 at 10:24
Don't bother trying to "avoid command line stuff" when you are configuring the operating system. Is Ctrl+Alt+T and a couple of ctrl-shift-V (to paste) too much to ask?
– doug65536
Aug 8 '16 at 0:15
|
show 1 more comment
To disable the bluetooth driver from loading on startup:
sudo $EDITOR /etc/modprobe.d/blacklist.conf
add:
blacklist btusb
Enabling it later should just be:
sudo modprobe btusb
1
Thanks for that, that does seem to work but I was trying to avoid command line stuff as per my original question. You would think this would be as simple as ticking a box so that it remembered that I don't want BT to start automatically but it looks like its way more complicated than that. With Ubuntu's drive for quicker boot times and the general focus on power consumption in laptops and netbooks I am suprised that this has never been addressed. I appreciate the help though.
– Chris Giltnane
Aug 19 '10 at 9:52
9
"Run gedit as root and edit /etc/modprobe.d/blacklist.conf" <-- ok, is that less command line for ya?
– maco
Aug 19 '10 at 13:35
1
Works fine on Samsung Q35 with Ubuntu 13.10, while the 'rfkill block bluetooth' approach does not. Thanks!
– user27164
Jan 6 '14 at 8:29
DELL E6410 works for me. Good that can run again on the go without reset.
– Ruslan Gerasimov
Jun 13 '14 at 10:24
Don't bother trying to "avoid command line stuff" when you are configuring the operating system. Is Ctrl+Alt+T and a couple of ctrl-shift-V (to paste) too much to ask?
– doug65536
Aug 8 '16 at 0:15
|
show 1 more comment
To disable the bluetooth driver from loading on startup:
sudo $EDITOR /etc/modprobe.d/blacklist.conf
add:
blacklist btusb
Enabling it later should just be:
sudo modprobe btusb
To disable the bluetooth driver from loading on startup:
sudo $EDITOR /etc/modprobe.d/blacklist.conf
add:
blacklist btusb
Enabling it later should just be:
sudo modprobe btusb
answered Aug 18 '10 at 16:59
macomaco
12.7k32434
12.7k32434
1
Thanks for that, that does seem to work but I was trying to avoid command line stuff as per my original question. You would think this would be as simple as ticking a box so that it remembered that I don't want BT to start automatically but it looks like its way more complicated than that. With Ubuntu's drive for quicker boot times and the general focus on power consumption in laptops and netbooks I am suprised that this has never been addressed. I appreciate the help though.
– Chris Giltnane
Aug 19 '10 at 9:52
9
"Run gedit as root and edit /etc/modprobe.d/blacklist.conf" <-- ok, is that less command line for ya?
– maco
Aug 19 '10 at 13:35
1
Works fine on Samsung Q35 with Ubuntu 13.10, while the 'rfkill block bluetooth' approach does not. Thanks!
– user27164
Jan 6 '14 at 8:29
DELL E6410 works for me. Good that can run again on the go without reset.
– Ruslan Gerasimov
Jun 13 '14 at 10:24
Don't bother trying to "avoid command line stuff" when you are configuring the operating system. Is Ctrl+Alt+T and a couple of ctrl-shift-V (to paste) too much to ask?
– doug65536
Aug 8 '16 at 0:15
|
show 1 more comment
1
Thanks for that, that does seem to work but I was trying to avoid command line stuff as per my original question. You would think this would be as simple as ticking a box so that it remembered that I don't want BT to start automatically but it looks like its way more complicated than that. With Ubuntu's drive for quicker boot times and the general focus on power consumption in laptops and netbooks I am suprised that this has never been addressed. I appreciate the help though.
– Chris Giltnane
Aug 19 '10 at 9:52
9
"Run gedit as root and edit /etc/modprobe.d/blacklist.conf" <-- ok, is that less command line for ya?
– maco
Aug 19 '10 at 13:35
1
Works fine on Samsung Q35 with Ubuntu 13.10, while the 'rfkill block bluetooth' approach does not. Thanks!
– user27164
Jan 6 '14 at 8:29
DELL E6410 works for me. Good that can run again on the go without reset.
– Ruslan Gerasimov
Jun 13 '14 at 10:24
Don't bother trying to "avoid command line stuff" when you are configuring the operating system. Is Ctrl+Alt+T and a couple of ctrl-shift-V (to paste) too much to ask?
– doug65536
Aug 8 '16 at 0:15
1
1
Thanks for that, that does seem to work but I was trying to avoid command line stuff as per my original question. You would think this would be as simple as ticking a box so that it remembered that I don't want BT to start automatically but it looks like its way more complicated than that. With Ubuntu's drive for quicker boot times and the general focus on power consumption in laptops and netbooks I am suprised that this has never been addressed. I appreciate the help though.
– Chris Giltnane
Aug 19 '10 at 9:52
Thanks for that, that does seem to work but I was trying to avoid command line stuff as per my original question. You would think this would be as simple as ticking a box so that it remembered that I don't want BT to start automatically but it looks like its way more complicated than that. With Ubuntu's drive for quicker boot times and the general focus on power consumption in laptops and netbooks I am suprised that this has never been addressed. I appreciate the help though.
– Chris Giltnane
Aug 19 '10 at 9:52
9
9
"Run gedit as root and edit /etc/modprobe.d/blacklist.conf" <-- ok, is that less command line for ya?
– maco
Aug 19 '10 at 13:35
"Run gedit as root and edit /etc/modprobe.d/blacklist.conf" <-- ok, is that less command line for ya?
– maco
Aug 19 '10 at 13:35
1
1
Works fine on Samsung Q35 with Ubuntu 13.10, while the 'rfkill block bluetooth' approach does not. Thanks!
– user27164
Jan 6 '14 at 8:29
Works fine on Samsung Q35 with Ubuntu 13.10, while the 'rfkill block bluetooth' approach does not. Thanks!
– user27164
Jan 6 '14 at 8:29
DELL E6410 works for me. Good that can run again on the go without reset.
– Ruslan Gerasimov
Jun 13 '14 at 10:24
DELL E6410 works for me. Good that can run again on the go without reset.
– Ruslan Gerasimov
Jun 13 '14 at 10:24
Don't bother trying to "avoid command line stuff" when you are configuring the operating system. Is Ctrl+Alt+T and a couple of ctrl-shift-V (to paste) too much to ask?
– doug65536
Aug 8 '16 at 0:15
Don't bother trying to "avoid command line stuff" when you are configuring the operating system. Is Ctrl+Alt+T and a couple of ctrl-shift-V (to paste) too much to ask?
– doug65536
Aug 8 '16 at 0:15
|
show 1 more comment
Step 1: Go to the terminal and type in the following command to edit system's /etc/rc.local
file:
gksudo gedit /etc/rc.local
Step 2: Add the following line before the exit 0
line:
rfkill block bluetooth
1
This is set soft block to bluetooth, I think it same as turn off its service and works well.
– Smile.Hunter
Aug 17 '12 at 13:45
@Robert:$ man rfkill
: "Disable the device corresponding to the given index." Despite the name, it is only disabling BT; just try the commandrfkill block bluetooth
on the terminal, you should see the icon go gray.
– Daniel
Jun 13 '15 at 17:54
add a comment |
Step 1: Go to the terminal and type in the following command to edit system's /etc/rc.local
file:
gksudo gedit /etc/rc.local
Step 2: Add the following line before the exit 0
line:
rfkill block bluetooth
1
This is set soft block to bluetooth, I think it same as turn off its service and works well.
– Smile.Hunter
Aug 17 '12 at 13:45
@Robert:$ man rfkill
: "Disable the device corresponding to the given index." Despite the name, it is only disabling BT; just try the commandrfkill block bluetooth
on the terminal, you should see the icon go gray.
– Daniel
Jun 13 '15 at 17:54
add a comment |
Step 1: Go to the terminal and type in the following command to edit system's /etc/rc.local
file:
gksudo gedit /etc/rc.local
Step 2: Add the following line before the exit 0
line:
rfkill block bluetooth
Step 1: Go to the terminal and type in the following command to edit system's /etc/rc.local
file:
gksudo gedit /etc/rc.local
Step 2: Add the following line before the exit 0
line:
rfkill block bluetooth
edited Nov 28 '13 at 1:39
behnam
22119
22119
answered May 4 '12 at 20:44
VarunVarun
32436
32436
1
This is set soft block to bluetooth, I think it same as turn off its service and works well.
– Smile.Hunter
Aug 17 '12 at 13:45
@Robert:$ man rfkill
: "Disable the device corresponding to the given index." Despite the name, it is only disabling BT; just try the commandrfkill block bluetooth
on the terminal, you should see the icon go gray.
– Daniel
Jun 13 '15 at 17:54
add a comment |
1
This is set soft block to bluetooth, I think it same as turn off its service and works well.
– Smile.Hunter
Aug 17 '12 at 13:45
@Robert:$ man rfkill
: "Disable the device corresponding to the given index." Despite the name, it is only disabling BT; just try the commandrfkill block bluetooth
on the terminal, you should see the icon go gray.
– Daniel
Jun 13 '15 at 17:54
1
1
This is set soft block to bluetooth, I think it same as turn off its service and works well.
– Smile.Hunter
Aug 17 '12 at 13:45
This is set soft block to bluetooth, I think it same as turn off its service and works well.
– Smile.Hunter
Aug 17 '12 at 13:45
@Robert:
$ man rfkill
: "Disable the device corresponding to the given index." Despite the name, it is only disabling BT; just try the command rfkill block bluetooth
on the terminal, you should see the icon go gray.– Daniel
Jun 13 '15 at 17:54
@Robert:
$ man rfkill
: "Disable the device corresponding to the given index." Despite the name, it is only disabling BT; just try the command rfkill block bluetooth
on the terminal, you should see the icon go gray.– Daniel
Jun 13 '15 at 17:54
add a comment |
From ubuntu 16.04 onwards systemd manages startup services like bluetooth ... to view current status issue following in a terminal
sudo systemctl status bluetooth.service
to deactivate bluetooth on startup issue this
sudo systemctl disable bluetooth.service
then on next reboot bluetooth will not be active ... to enable bluetooth issue
sudo systemctl enable bluetooth.service
2
This works for me, but as a side effect, blueman-applet stoppped to work too. It starts, but doesn't appear in the indicator area, so there is no fast way to enable bluetooth, only in terminal.
– Yuri Gor
Sep 2 '17 at 21:02
In Xubuntu, at least, if you click on Blueman, it has the option of "Turn Bluetooth Off". I think this is what the OP would like automated. Your solution removes Blueman altogether, making it harder to re-enable Bluetooth if desired.
– Adrian Keister
Jan 30 '18 at 14:08
1
Put sudo systemctl disable bluetooth.service && sudo systemctl stop bluetooth.service into a Disable script, and chmod 755 on it. Do the same for sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service in an Enable script.
– Adrian Keister
Jan 30 '18 at 14:33
FINALLY! Ubuntu 18.10, the only thing that worked for me. Nothing else worked.
– Tyler
Feb 18 at 13:02
add a comment |
From ubuntu 16.04 onwards systemd manages startup services like bluetooth ... to view current status issue following in a terminal
sudo systemctl status bluetooth.service
to deactivate bluetooth on startup issue this
sudo systemctl disable bluetooth.service
then on next reboot bluetooth will not be active ... to enable bluetooth issue
sudo systemctl enable bluetooth.service
2
This works for me, but as a side effect, blueman-applet stoppped to work too. It starts, but doesn't appear in the indicator area, so there is no fast way to enable bluetooth, only in terminal.
– Yuri Gor
Sep 2 '17 at 21:02
In Xubuntu, at least, if you click on Blueman, it has the option of "Turn Bluetooth Off". I think this is what the OP would like automated. Your solution removes Blueman altogether, making it harder to re-enable Bluetooth if desired.
– Adrian Keister
Jan 30 '18 at 14:08
1
Put sudo systemctl disable bluetooth.service && sudo systemctl stop bluetooth.service into a Disable script, and chmod 755 on it. Do the same for sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service in an Enable script.
– Adrian Keister
Jan 30 '18 at 14:33
FINALLY! Ubuntu 18.10, the only thing that worked for me. Nothing else worked.
– Tyler
Feb 18 at 13:02
add a comment |
From ubuntu 16.04 onwards systemd manages startup services like bluetooth ... to view current status issue following in a terminal
sudo systemctl status bluetooth.service
to deactivate bluetooth on startup issue this
sudo systemctl disable bluetooth.service
then on next reboot bluetooth will not be active ... to enable bluetooth issue
sudo systemctl enable bluetooth.service
From ubuntu 16.04 onwards systemd manages startup services like bluetooth ... to view current status issue following in a terminal
sudo systemctl status bluetooth.service
to deactivate bluetooth on startup issue this
sudo systemctl disable bluetooth.service
then on next reboot bluetooth will not be active ... to enable bluetooth issue
sudo systemctl enable bluetooth.service
edited Sep 2 '17 at 22:06
answered Aug 1 '17 at 15:08
Scott StenslandScott Stensland
5,00242242
5,00242242
2
This works for me, but as a side effect, blueman-applet stoppped to work too. It starts, but doesn't appear in the indicator area, so there is no fast way to enable bluetooth, only in terminal.
– Yuri Gor
Sep 2 '17 at 21:02
In Xubuntu, at least, if you click on Blueman, it has the option of "Turn Bluetooth Off". I think this is what the OP would like automated. Your solution removes Blueman altogether, making it harder to re-enable Bluetooth if desired.
– Adrian Keister
Jan 30 '18 at 14:08
1
Put sudo systemctl disable bluetooth.service && sudo systemctl stop bluetooth.service into a Disable script, and chmod 755 on it. Do the same for sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service in an Enable script.
– Adrian Keister
Jan 30 '18 at 14:33
FINALLY! Ubuntu 18.10, the only thing that worked for me. Nothing else worked.
– Tyler
Feb 18 at 13:02
add a comment |
2
This works for me, but as a side effect, blueman-applet stoppped to work too. It starts, but doesn't appear in the indicator area, so there is no fast way to enable bluetooth, only in terminal.
– Yuri Gor
Sep 2 '17 at 21:02
In Xubuntu, at least, if you click on Blueman, it has the option of "Turn Bluetooth Off". I think this is what the OP would like automated. Your solution removes Blueman altogether, making it harder to re-enable Bluetooth if desired.
– Adrian Keister
Jan 30 '18 at 14:08
1
Put sudo systemctl disable bluetooth.service && sudo systemctl stop bluetooth.service into a Disable script, and chmod 755 on it. Do the same for sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service in an Enable script.
– Adrian Keister
Jan 30 '18 at 14:33
FINALLY! Ubuntu 18.10, the only thing that worked for me. Nothing else worked.
– Tyler
Feb 18 at 13:02
2
2
This works for me, but as a side effect, blueman-applet stoppped to work too. It starts, but doesn't appear in the indicator area, so there is no fast way to enable bluetooth, only in terminal.
– Yuri Gor
Sep 2 '17 at 21:02
This works for me, but as a side effect, blueman-applet stoppped to work too. It starts, but doesn't appear in the indicator area, so there is no fast way to enable bluetooth, only in terminal.
– Yuri Gor
Sep 2 '17 at 21:02
In Xubuntu, at least, if you click on Blueman, it has the option of "Turn Bluetooth Off". I think this is what the OP would like automated. Your solution removes Blueman altogether, making it harder to re-enable Bluetooth if desired.
– Adrian Keister
Jan 30 '18 at 14:08
In Xubuntu, at least, if you click on Blueman, it has the option of "Turn Bluetooth Off". I think this is what the OP would like automated. Your solution removes Blueman altogether, making it harder to re-enable Bluetooth if desired.
– Adrian Keister
Jan 30 '18 at 14:08
1
1
Put sudo systemctl disable bluetooth.service && sudo systemctl stop bluetooth.service into a Disable script, and chmod 755 on it. Do the same for sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service in an Enable script.
– Adrian Keister
Jan 30 '18 at 14:33
Put sudo systemctl disable bluetooth.service && sudo systemctl stop bluetooth.service into a Disable script, and chmod 755 on it. Do the same for sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service in an Enable script.
– Adrian Keister
Jan 30 '18 at 14:33
FINALLY! Ubuntu 18.10, the only thing that worked for me. Nothing else worked.
– Tyler
Feb 18 at 13:02
FINALLY! Ubuntu 18.10, the only thing that worked for me. Nothing else worked.
– Tyler
Feb 18 at 13:02
add a comment |
Type the following into a terminal:
sudo gedit /etc/modprobe.d/blacklist.conf
At the bottom of the file, add the line:
blacklist bluetooth
Save the file and restart - Bluetooth should now be disabled.
This won't work on my pc...
– Floqqi
Oct 16 '11 at 21:47
@Floqqi: Can you please try it again? I've updated my answer.
– Nathan Osman
Oct 16 '11 at 23:42
2
Tried about 20 things on my ubuntu 12 thinkpad, this is the only one that did the trick.
– OlivierBlanvillain
Sep 12 '13 at 16:57
add a comment |
Type the following into a terminal:
sudo gedit /etc/modprobe.d/blacklist.conf
At the bottom of the file, add the line:
blacklist bluetooth
Save the file and restart - Bluetooth should now be disabled.
This won't work on my pc...
– Floqqi
Oct 16 '11 at 21:47
@Floqqi: Can you please try it again? I've updated my answer.
– Nathan Osman
Oct 16 '11 at 23:42
2
Tried about 20 things on my ubuntu 12 thinkpad, this is the only one that did the trick.
– OlivierBlanvillain
Sep 12 '13 at 16:57
add a comment |
Type the following into a terminal:
sudo gedit /etc/modprobe.d/blacklist.conf
At the bottom of the file, add the line:
blacklist bluetooth
Save the file and restart - Bluetooth should now be disabled.
Type the following into a terminal:
sudo gedit /etc/modprobe.d/blacklist.conf
At the bottom of the file, add the line:
blacklist bluetooth
Save the file and restart - Bluetooth should now be disabled.
edited Oct 16 '11 at 23:45
answered Oct 16 '11 at 21:25
Nathan OsmanNathan Osman
21k32144237
21k32144237
This won't work on my pc...
– Floqqi
Oct 16 '11 at 21:47
@Floqqi: Can you please try it again? I've updated my answer.
– Nathan Osman
Oct 16 '11 at 23:42
2
Tried about 20 things on my ubuntu 12 thinkpad, this is the only one that did the trick.
– OlivierBlanvillain
Sep 12 '13 at 16:57
add a comment |
This won't work on my pc...
– Floqqi
Oct 16 '11 at 21:47
@Floqqi: Can you please try it again? I've updated my answer.
– Nathan Osman
Oct 16 '11 at 23:42
2
Tried about 20 things on my ubuntu 12 thinkpad, this is the only one that did the trick.
– OlivierBlanvillain
Sep 12 '13 at 16:57
This won't work on my pc...
– Floqqi
Oct 16 '11 at 21:47
This won't work on my pc...
– Floqqi
Oct 16 '11 at 21:47
@Floqqi: Can you please try it again? I've updated my answer.
– Nathan Osman
Oct 16 '11 at 23:42
@Floqqi: Can you please try it again? I've updated my answer.
– Nathan Osman
Oct 16 '11 at 23:42
2
2
Tried about 20 things on my ubuntu 12 thinkpad, this is the only one that did the trick.
– OlivierBlanvillain
Sep 12 '13 at 16:57
Tried about 20 things on my ubuntu 12 thinkpad, this is the only one that did the trick.
– OlivierBlanvillain
Sep 12 '13 at 16:57
add a comment |
You can change the services started at boot with the help of BUM.
Install it: sudo apt-get install bum
Run: sudo bum
Uncheck the box and click Apply.
Thank you, desgua, I was thinking about this kind of tools. I have used some in the past but they become obsolete and the new ubuntu, with their minimalistic obsession, comes with nothing of the kind. Is this the only yo know or the best yo know?
– Robert
May 5 '12 at 0:15
1
Maybe works but at first it has disappointed me because it started showing the bluetooth as not activated at boot time, why? and as not running when rfkill, the applet and hciconfig show it running. I turn off and on but bum continues showing the service as off. I activated the service at boot-up but the status of the service continues to be wrong.
– Robert
May 5 '12 at 1:26
sorry doesn't work on elementaryOS Freya
– Hoang Tran
Jul 9 '16 at 13:31
I get lots of "use of uninitialized value" warnings when it runs. Sorry, can't trust that.
– doug65536
Aug 8 '16 at 0:21
Now, the package is not available. It say, Bum is virtual.
– Satya Prakash
Jul 26 '17 at 19:27
|
show 2 more comments
You can change the services started at boot with the help of BUM.
Install it: sudo apt-get install bum
Run: sudo bum
Uncheck the box and click Apply.
Thank you, desgua, I was thinking about this kind of tools. I have used some in the past but they become obsolete and the new ubuntu, with their minimalistic obsession, comes with nothing of the kind. Is this the only yo know or the best yo know?
– Robert
May 5 '12 at 0:15
1
Maybe works but at first it has disappointed me because it started showing the bluetooth as not activated at boot time, why? and as not running when rfkill, the applet and hciconfig show it running. I turn off and on but bum continues showing the service as off. I activated the service at boot-up but the status of the service continues to be wrong.
– Robert
May 5 '12 at 1:26
sorry doesn't work on elementaryOS Freya
– Hoang Tran
Jul 9 '16 at 13:31
I get lots of "use of uninitialized value" warnings when it runs. Sorry, can't trust that.
– doug65536
Aug 8 '16 at 0:21
Now, the package is not available. It say, Bum is virtual.
– Satya Prakash
Jul 26 '17 at 19:27
|
show 2 more comments
You can change the services started at boot with the help of BUM.
Install it: sudo apt-get install bum
Run: sudo bum
Uncheck the box and click Apply.
You can change the services started at boot with the help of BUM.
Install it: sudo apt-get install bum
Run: sudo bum
Uncheck the box and click Apply.
edited Aug 1 '17 at 14:46
Scott Stensland
5,00242242
5,00242242
answered May 5 '12 at 0:09
desguadesgua
27.8k882112
27.8k882112
Thank you, desgua, I was thinking about this kind of tools. I have used some in the past but they become obsolete and the new ubuntu, with their minimalistic obsession, comes with nothing of the kind. Is this the only yo know or the best yo know?
– Robert
May 5 '12 at 0:15
1
Maybe works but at first it has disappointed me because it started showing the bluetooth as not activated at boot time, why? and as not running when rfkill, the applet and hciconfig show it running. I turn off and on but bum continues showing the service as off. I activated the service at boot-up but the status of the service continues to be wrong.
– Robert
May 5 '12 at 1:26
sorry doesn't work on elementaryOS Freya
– Hoang Tran
Jul 9 '16 at 13:31
I get lots of "use of uninitialized value" warnings when it runs. Sorry, can't trust that.
– doug65536
Aug 8 '16 at 0:21
Now, the package is not available. It say, Bum is virtual.
– Satya Prakash
Jul 26 '17 at 19:27
|
show 2 more comments
Thank you, desgua, I was thinking about this kind of tools. I have used some in the past but they become obsolete and the new ubuntu, with their minimalistic obsession, comes with nothing of the kind. Is this the only yo know or the best yo know?
– Robert
May 5 '12 at 0:15
1
Maybe works but at first it has disappointed me because it started showing the bluetooth as not activated at boot time, why? and as not running when rfkill, the applet and hciconfig show it running. I turn off and on but bum continues showing the service as off. I activated the service at boot-up but the status of the service continues to be wrong.
– Robert
May 5 '12 at 1:26
sorry doesn't work on elementaryOS Freya
– Hoang Tran
Jul 9 '16 at 13:31
I get lots of "use of uninitialized value" warnings when it runs. Sorry, can't trust that.
– doug65536
Aug 8 '16 at 0:21
Now, the package is not available. It say, Bum is virtual.
– Satya Prakash
Jul 26 '17 at 19:27
Thank you, desgua, I was thinking about this kind of tools. I have used some in the past but they become obsolete and the new ubuntu, with their minimalistic obsession, comes with nothing of the kind. Is this the only yo know or the best yo know?
– Robert
May 5 '12 at 0:15
Thank you, desgua, I was thinking about this kind of tools. I have used some in the past but they become obsolete and the new ubuntu, with their minimalistic obsession, comes with nothing of the kind. Is this the only yo know or the best yo know?
– Robert
May 5 '12 at 0:15
1
1
Maybe works but at first it has disappointed me because it started showing the bluetooth as not activated at boot time, why? and as not running when rfkill, the applet and hciconfig show it running. I turn off and on but bum continues showing the service as off. I activated the service at boot-up but the status of the service continues to be wrong.
– Robert
May 5 '12 at 1:26
Maybe works but at first it has disappointed me because it started showing the bluetooth as not activated at boot time, why? and as not running when rfkill, the applet and hciconfig show it running. I turn off and on but bum continues showing the service as off. I activated the service at boot-up but the status of the service continues to be wrong.
– Robert
May 5 '12 at 1:26
sorry doesn't work on elementaryOS Freya
– Hoang Tran
Jul 9 '16 at 13:31
sorry doesn't work on elementaryOS Freya
– Hoang Tran
Jul 9 '16 at 13:31
I get lots of "use of uninitialized value" warnings when it runs. Sorry, can't trust that.
– doug65536
Aug 8 '16 at 0:21
I get lots of "use of uninitialized value" warnings when it runs. Sorry, can't trust that.
– doug65536
Aug 8 '16 at 0:21
Now, the package is not available. It say, Bum is virtual.
– Satya Prakash
Jul 26 '17 at 19:27
Now, the package is not available. It say, Bum is virtual.
– Satya Prakash
Jul 26 '17 at 19:27
|
show 2 more comments
1. block bluetooth in rc.local
Add this line at the end of the file /etc/rc.local
right before the line exit 0
:
rfkill block bluetooth
This will do the trick, but only in older Ubuntu versions using upstart.
2. reenable rc.local on systemd
On Ubuntu 15.10 with systemd as startup manager the /etc/rc.local
file is not used by default any more, so call this on a terminal:
sudo systemctl edit --full rc-local
Which opens an editor. At the end of the file i added:
[Install]
WantedBy=multi-user.target
Those changes are activated by
sudo systemctl reenable rc-local
Now the file /etc/rc.local
is used as you know it.
3. disable blueman-applet on start
sudo sed -i 's/NoDisplay=true/NoDisplay=false/g' /etc/xdg/autostart/blueman.desktop
gnome-session-properties
Now blueman-applet is visible and you can disable it from startup programs
4. Reboot to see the effect
3
For me on Ubuntu 17.04 with blueman:gsettings set org.blueman.plugins.powermanager auto-power-on false
worked, from wiki.archlinux.org/index.php/Blueman. Although I ended up doingsudo apt remove blueman
then manage bluetooth through system settings and check "Show Bluetooth status in the menu bar". Blueman starting and turning on bluetooth was the issue.
– Michael Jackson
Sep 28 '17 at 14:29
add a comment |
1. block bluetooth in rc.local
Add this line at the end of the file /etc/rc.local
right before the line exit 0
:
rfkill block bluetooth
This will do the trick, but only in older Ubuntu versions using upstart.
2. reenable rc.local on systemd
On Ubuntu 15.10 with systemd as startup manager the /etc/rc.local
file is not used by default any more, so call this on a terminal:
sudo systemctl edit --full rc-local
Which opens an editor. At the end of the file i added:
[Install]
WantedBy=multi-user.target
Those changes are activated by
sudo systemctl reenable rc-local
Now the file /etc/rc.local
is used as you know it.
3. disable blueman-applet on start
sudo sed -i 's/NoDisplay=true/NoDisplay=false/g' /etc/xdg/autostart/blueman.desktop
gnome-session-properties
Now blueman-applet is visible and you can disable it from startup programs
4. Reboot to see the effect
3
For me on Ubuntu 17.04 with blueman:gsettings set org.blueman.plugins.powermanager auto-power-on false
worked, from wiki.archlinux.org/index.php/Blueman. Although I ended up doingsudo apt remove blueman
then manage bluetooth through system settings and check "Show Bluetooth status in the menu bar". Blueman starting and turning on bluetooth was the issue.
– Michael Jackson
Sep 28 '17 at 14:29
add a comment |
1. block bluetooth in rc.local
Add this line at the end of the file /etc/rc.local
right before the line exit 0
:
rfkill block bluetooth
This will do the trick, but only in older Ubuntu versions using upstart.
2. reenable rc.local on systemd
On Ubuntu 15.10 with systemd as startup manager the /etc/rc.local
file is not used by default any more, so call this on a terminal:
sudo systemctl edit --full rc-local
Which opens an editor. At the end of the file i added:
[Install]
WantedBy=multi-user.target
Those changes are activated by
sudo systemctl reenable rc-local
Now the file /etc/rc.local
is used as you know it.
3. disable blueman-applet on start
sudo sed -i 's/NoDisplay=true/NoDisplay=false/g' /etc/xdg/autostart/blueman.desktop
gnome-session-properties
Now blueman-applet is visible and you can disable it from startup programs
4. Reboot to see the effect
1. block bluetooth in rc.local
Add this line at the end of the file /etc/rc.local
right before the line exit 0
:
rfkill block bluetooth
This will do the trick, but only in older Ubuntu versions using upstart.
2. reenable rc.local on systemd
On Ubuntu 15.10 with systemd as startup manager the /etc/rc.local
file is not used by default any more, so call this on a terminal:
sudo systemctl edit --full rc-local
Which opens an editor. At the end of the file i added:
[Install]
WantedBy=multi-user.target
Those changes are activated by
sudo systemctl reenable rc-local
Now the file /etc/rc.local
is used as you know it.
3. disable blueman-applet on start
sudo sed -i 's/NoDisplay=true/NoDisplay=false/g' /etc/xdg/autostart/blueman.desktop
gnome-session-properties
Now blueman-applet is visible and you can disable it from startup programs
4. Reboot to see the effect
edited Dec 5 '16 at 16:27
answered Nov 10 '15 at 12:29
rubo77rubo77
15.2k3196202
15.2k3196202
3
For me on Ubuntu 17.04 with blueman:gsettings set org.blueman.plugins.powermanager auto-power-on false
worked, from wiki.archlinux.org/index.php/Blueman. Although I ended up doingsudo apt remove blueman
then manage bluetooth through system settings and check "Show Bluetooth status in the menu bar". Blueman starting and turning on bluetooth was the issue.
– Michael Jackson
Sep 28 '17 at 14:29
add a comment |
3
For me on Ubuntu 17.04 with blueman:gsettings set org.blueman.plugins.powermanager auto-power-on false
worked, from wiki.archlinux.org/index.php/Blueman. Although I ended up doingsudo apt remove blueman
then manage bluetooth through system settings and check "Show Bluetooth status in the menu bar". Blueman starting and turning on bluetooth was the issue.
– Michael Jackson
Sep 28 '17 at 14:29
3
3
For me on Ubuntu 17.04 with blueman:
gsettings set org.blueman.plugins.powermanager auto-power-on false
worked, from wiki.archlinux.org/index.php/Blueman. Although I ended up doing sudo apt remove blueman
then manage bluetooth through system settings and check "Show Bluetooth status in the menu bar". Blueman starting and turning on bluetooth was the issue.– Michael Jackson
Sep 28 '17 at 14:29
For me on Ubuntu 17.04 with blueman:
gsettings set org.blueman.plugins.powermanager auto-power-on false
worked, from wiki.archlinux.org/index.php/Blueman. Although I ended up doing sudo apt remove blueman
then manage bluetooth through system settings and check "Show Bluetooth status in the menu bar". Blueman starting and turning on bluetooth was the issue.– Michael Jackson
Sep 28 '17 at 14:29
add a comment |
I think that the best way is to disable the service from being started in the first place. There is a general method for disabling services which works perfectly:
sudo sh -c "echo 'manual' > /etc/init/bluetooth.override"
That works for Ubuntu 13.10 and probably for earlier versions as well.
how to turn on bluetooth, while using provided settings later on? say I want to use it just for 5 min. every 10 boots..
– b1r3k
Oct 10 '15 at 14:51
add a comment |
I think that the best way is to disable the service from being started in the first place. There is a general method for disabling services which works perfectly:
sudo sh -c "echo 'manual' > /etc/init/bluetooth.override"
That works for Ubuntu 13.10 and probably for earlier versions as well.
how to turn on bluetooth, while using provided settings later on? say I want to use it just for 5 min. every 10 boots..
– b1r3k
Oct 10 '15 at 14:51
add a comment |
I think that the best way is to disable the service from being started in the first place. There is a general method for disabling services which works perfectly:
sudo sh -c "echo 'manual' > /etc/init/bluetooth.override"
That works for Ubuntu 13.10 and probably for earlier versions as well.
I think that the best way is to disable the service from being started in the first place. There is a general method for disabling services which works perfectly:
sudo sh -c "echo 'manual' > /etc/init/bluetooth.override"
That works for Ubuntu 13.10 and probably for earlier versions as well.
answered Jan 18 '14 at 9:49
FelipeFelipe
5111
5111
how to turn on bluetooth, while using provided settings later on? say I want to use it just for 5 min. every 10 boots..
– b1r3k
Oct 10 '15 at 14:51
add a comment |
how to turn on bluetooth, while using provided settings later on? say I want to use it just for 5 min. every 10 boots..
– b1r3k
Oct 10 '15 at 14:51
how to turn on bluetooth, while using provided settings later on? say I want to use it just for 5 min. every 10 boots..
– b1r3k
Oct 10 '15 at 14:51
how to turn on bluetooth, while using provided settings later on? say I want to use it just for 5 min. every 10 boots..
– b1r3k
Oct 10 '15 at 14:51
add a comment |
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
This removed the bluetooth tray icon but left my bluetooth indicator light on (indicating power was still being sent to the radio). Edit: this in conjunction with Stepbaer's answer (InitiallyPowered = false
) worked for me. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:59
this did not work on my 64-bit Ubuntu 14.04 dell inspiron. Only rfkill worked for me.
– faizal
Jun 17 '14 at 7:19
add a comment |
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
This removed the bluetooth tray icon but left my bluetooth indicator light on (indicating power was still being sent to the radio). Edit: this in conjunction with Stepbaer's answer (InitiallyPowered = false
) worked for me. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:59
this did not work on my 64-bit Ubuntu 14.04 dell inspiron. Only rfkill worked for me.
– faizal
Jun 17 '14 at 7:19
add a comment |
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
edited Aug 22 '14 at 17:03
Seth♦
34.9k27112165
34.9k27112165
answered Aug 23 '12 at 13:00
Saeed ZarinfamSaeed Zarinfam
13.8k52940
13.8k52940
This removed the bluetooth tray icon but left my bluetooth indicator light on (indicating power was still being sent to the radio). Edit: this in conjunction with Stepbaer's answer (InitiallyPowered = false
) worked for me. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:59
this did not work on my 64-bit Ubuntu 14.04 dell inspiron. Only rfkill worked for me.
– faizal
Jun 17 '14 at 7:19
add a comment |
This removed the bluetooth tray icon but left my bluetooth indicator light on (indicating power was still being sent to the radio). Edit: this in conjunction with Stepbaer's answer (InitiallyPowered = false
) worked for me. (ThinkPad x201, Xubuntu 13.10)
– Kyle Falconer
Dec 20 '13 at 7:59
this did not work on my 64-bit Ubuntu 14.04 dell inspiron. Only rfkill worked for me.
– faizal
Jun 17 '14 at 7:19
This removed the bluetooth tray icon but left my bluetooth indicator light on (indicating power was still being sent to the radio). Edit: this in conjunction with Stepbaer's answer (
InitiallyPowered = false
) worked for me. (ThinkPad x201, Xubuntu 13.10)– Kyle Falconer
Dec 20 '13 at 7:59
This removed the bluetooth tray icon but left my bluetooth indicator light on (indicating power was still being sent to the radio). Edit: this in conjunction with Stepbaer's answer (
InitiallyPowered = false
) worked for me. (ThinkPad x201, Xubuntu 13.10)– Kyle Falconer
Dec 20 '13 at 7:59
this did not work on my 64-bit Ubuntu 14.04 dell inspiron. Only rfkill worked for me.
– faizal
Jun 17 '14 at 7:19
this did not work on my 64-bit Ubuntu 14.04 dell inspiron. Only rfkill worked for me.
– faizal
Jun 17 '14 at 7:19
add a comment |
You can edit your update-rc.d
settings. I used something similar to:
sudo update-rc.d bluetooth remove
In Debian Wheezy. Check out man update-rc.d
for more info on how to use it.
add a comment |
You can edit your update-rc.d
settings. I used something similar to:
sudo update-rc.d bluetooth remove
In Debian Wheezy. Check out man update-rc.d
for more info on how to use it.
add a comment |
You can edit your update-rc.d
settings. I used something similar to:
sudo update-rc.d bluetooth remove
In Debian Wheezy. Check out man update-rc.d
for more info on how to use it.
You can edit your update-rc.d
settings. I used something similar to:
sudo update-rc.d bluetooth remove
In Debian Wheezy. Check out man update-rc.d
for more info on how to use it.
answered Feb 13 '13 at 15:50
Keith SmileyKeith Smiley
1414
1414
add a comment |
add a comment |
Maybe you can turn it off in the Startup Applications.
But these applications are hidden by default.
Unhide the hidden Startup Applications in 12.04: Open the terminal and run these two commands:
cd /etc/xdg/autostart/
sudo sed --in-place 's/NoDisplay=true/NoDisplay=false/g' *.desktop
Now you can uncheck bluetooth. (Don't remove!)
Bluetooth is not listed among these applications, sadly.
– pfctdayelise
Jul 10 '15 at 12:11
add a comment |
Maybe you can turn it off in the Startup Applications.
But these applications are hidden by default.
Unhide the hidden Startup Applications in 12.04: Open the terminal and run these two commands:
cd /etc/xdg/autostart/
sudo sed --in-place 's/NoDisplay=true/NoDisplay=false/g' *.desktop
Now you can uncheck bluetooth. (Don't remove!)
Bluetooth is not listed among these applications, sadly.
– pfctdayelise
Jul 10 '15 at 12:11
add a comment |
Maybe you can turn it off in the Startup Applications.
But these applications are hidden by default.
Unhide the hidden Startup Applications in 12.04: Open the terminal and run these two commands:
cd /etc/xdg/autostart/
sudo sed --in-place 's/NoDisplay=true/NoDisplay=false/g' *.desktop
Now you can uncheck bluetooth. (Don't remove!)
Maybe you can turn it off in the Startup Applications.
But these applications are hidden by default.
Unhide the hidden Startup Applications in 12.04: Open the terminal and run these two commands:
cd /etc/xdg/autostart/
sudo sed --in-place 's/NoDisplay=true/NoDisplay=false/g' *.desktop
Now you can uncheck bluetooth. (Don't remove!)
answered May 5 '12 at 8:50
schiemanskischiemanski
31625
31625
Bluetooth is not listed among these applications, sadly.
– pfctdayelise
Jul 10 '15 at 12:11
add a comment |
Bluetooth is not listed among these applications, sadly.
– pfctdayelise
Jul 10 '15 at 12:11
Bluetooth is not listed among these applications, sadly.
– pfctdayelise
Jul 10 '15 at 12:11
Bluetooth is not listed among these applications, sadly.
– pfctdayelise
Jul 10 '15 at 12:11
add a comment |
No. It is not always in the startup applcations list. I think that the best solution is to add the rfkill command in rc.local script or to set the InitiallyPowered
parameter in /etc/bluetooth/main.conf
.
1
InitiallyPowered seems to be ignored for me.
– UpTheCreek
May 10 '15 at 9:42
add a comment |
No. It is not always in the startup applcations list. I think that the best solution is to add the rfkill command in rc.local script or to set the InitiallyPowered
parameter in /etc/bluetooth/main.conf
.
1
InitiallyPowered seems to be ignored for me.
– UpTheCreek
May 10 '15 at 9:42
add a comment |
No. It is not always in the startup applcations list. I think that the best solution is to add the rfkill command in rc.local script or to set the InitiallyPowered
parameter in /etc/bluetooth/main.conf
.
No. It is not always in the startup applcations list. I think that the best solution is to add the rfkill command in rc.local script or to set the InitiallyPowered
parameter in /etc/bluetooth/main.conf
.
edited Jun 10 '13 at 20:58
Robie Basak
12.6k24676
12.6k24676
answered May 5 '12 at 0:06
RobertRobert
186138
186138
1
InitiallyPowered seems to be ignored for me.
– UpTheCreek
May 10 '15 at 9:42
add a comment |
1
InitiallyPowered seems to be ignored for me.
– UpTheCreek
May 10 '15 at 9:42
1
1
InitiallyPowered seems to be ignored for me.
– UpTheCreek
May 10 '15 at 9:42
InitiallyPowered seems to be ignored for me.
– UpTheCreek
May 10 '15 at 9:42
add a comment |
1) Install the package smbios-utils and add it to Startup Applications with:
sudo smbios-wireless-ctl --bt 0
2) In terminal type:
sudo visudo
and add to the end of opened file /etc/sudoers
the line:
<your username> ALL = NOPASSWD: /usr/sbin/smbios-wireless-ctl
3) To switch bluetooth on during session, run in terminal:
sudo smbios-wireless-ctl --bt 1
This works for me on my Dell D630 with Ubuntu 13.10
Do you think thatsudo smbios-wireless-ctl --boot --bt 0
would work? Also, I'm not sure, but this may be Dell-specific.
– Hitechcomputergeek
May 2 '15 at 18:48
Actually, the package smbios-utils performs bios commands, so it switches on and off physical devices related to bios, so you may also use it to switch on and off wifi etc. I'm not sure if it works with any bios or not. At least, it works well with Dell. By the way, the last installations of Ubuntu 14.04 do same things with bluetooth and wifi applets, so I don't need any more in that package.
– victor
May 3 '15 at 19:22
I knew that. But if you dosmbios-wireless-ctl --help
, part of it has--boot Set BIOS boot-time setting.
I didn't know they fixed the Bluetooth, though; thanks for telling me.
– Hitechcomputergeek
May 4 '15 at 21:29
add a comment |
1) Install the package smbios-utils and add it to Startup Applications with:
sudo smbios-wireless-ctl --bt 0
2) In terminal type:
sudo visudo
and add to the end of opened file /etc/sudoers
the line:
<your username> ALL = NOPASSWD: /usr/sbin/smbios-wireless-ctl
3) To switch bluetooth on during session, run in terminal:
sudo smbios-wireless-ctl --bt 1
This works for me on my Dell D630 with Ubuntu 13.10
Do you think thatsudo smbios-wireless-ctl --boot --bt 0
would work? Also, I'm not sure, but this may be Dell-specific.
– Hitechcomputergeek
May 2 '15 at 18:48
Actually, the package smbios-utils performs bios commands, so it switches on and off physical devices related to bios, so you may also use it to switch on and off wifi etc. I'm not sure if it works with any bios or not. At least, it works well with Dell. By the way, the last installations of Ubuntu 14.04 do same things with bluetooth and wifi applets, so I don't need any more in that package.
– victor
May 3 '15 at 19:22
I knew that. But if you dosmbios-wireless-ctl --help
, part of it has--boot Set BIOS boot-time setting.
I didn't know they fixed the Bluetooth, though; thanks for telling me.
– Hitechcomputergeek
May 4 '15 at 21:29
add a comment |
1) Install the package smbios-utils and add it to Startup Applications with:
sudo smbios-wireless-ctl --bt 0
2) In terminal type:
sudo visudo
and add to the end of opened file /etc/sudoers
the line:
<your username> ALL = NOPASSWD: /usr/sbin/smbios-wireless-ctl
3) To switch bluetooth on during session, run in terminal:
sudo smbios-wireless-ctl --bt 1
This works for me on my Dell D630 with Ubuntu 13.10
1) Install the package smbios-utils and add it to Startup Applications with:
sudo smbios-wireless-ctl --bt 0
2) In terminal type:
sudo visudo
and add to the end of opened file /etc/sudoers
the line:
<your username> ALL = NOPASSWD: /usr/sbin/smbios-wireless-ctl
3) To switch bluetooth on during session, run in terminal:
sudo smbios-wireless-ctl --bt 1
This works for me on my Dell D630 with Ubuntu 13.10
edited Mar 15 '14 at 16:27
v2r
6,421113948
6,421113948
answered Mar 15 '14 at 15:58
victorvictor
634
634
Do you think thatsudo smbios-wireless-ctl --boot --bt 0
would work? Also, I'm not sure, but this may be Dell-specific.
– Hitechcomputergeek
May 2 '15 at 18:48
Actually, the package smbios-utils performs bios commands, so it switches on and off physical devices related to bios, so you may also use it to switch on and off wifi etc. I'm not sure if it works with any bios or not. At least, it works well with Dell. By the way, the last installations of Ubuntu 14.04 do same things with bluetooth and wifi applets, so I don't need any more in that package.
– victor
May 3 '15 at 19:22
I knew that. But if you dosmbios-wireless-ctl --help
, part of it has--boot Set BIOS boot-time setting.
I didn't know they fixed the Bluetooth, though; thanks for telling me.
– Hitechcomputergeek
May 4 '15 at 21:29
add a comment |
Do you think thatsudo smbios-wireless-ctl --boot --bt 0
would work? Also, I'm not sure, but this may be Dell-specific.
– Hitechcomputergeek
May 2 '15 at 18:48
Actually, the package smbios-utils performs bios commands, so it switches on and off physical devices related to bios, so you may also use it to switch on and off wifi etc. I'm not sure if it works with any bios or not. At least, it works well with Dell. By the way, the last installations of Ubuntu 14.04 do same things with bluetooth and wifi applets, so I don't need any more in that package.
– victor
May 3 '15 at 19:22
I knew that. But if you dosmbios-wireless-ctl --help
, part of it has--boot Set BIOS boot-time setting.
I didn't know they fixed the Bluetooth, though; thanks for telling me.
– Hitechcomputergeek
May 4 '15 at 21:29
Do you think that
sudo smbios-wireless-ctl --boot --bt 0
would work? Also, I'm not sure, but this may be Dell-specific.– Hitechcomputergeek
May 2 '15 at 18:48
Do you think that
sudo smbios-wireless-ctl --boot --bt 0
would work? Also, I'm not sure, but this may be Dell-specific.– Hitechcomputergeek
May 2 '15 at 18:48
Actually, the package smbios-utils performs bios commands, so it switches on and off physical devices related to bios, so you may also use it to switch on and off wifi etc. I'm not sure if it works with any bios or not. At least, it works well with Dell. By the way, the last installations of Ubuntu 14.04 do same things with bluetooth and wifi applets, so I don't need any more in that package.
– victor
May 3 '15 at 19:22
Actually, the package smbios-utils performs bios commands, so it switches on and off physical devices related to bios, so you may also use it to switch on and off wifi etc. I'm not sure if it works with any bios or not. At least, it works well with Dell. By the way, the last installations of Ubuntu 14.04 do same things with bluetooth and wifi applets, so I don't need any more in that package.
– victor
May 3 '15 at 19:22
I knew that. But if you do
smbios-wireless-ctl --help
, part of it has --boot Set BIOS boot-time setting.
I didn't know they fixed the Bluetooth, though; thanks for telling me.– Hitechcomputergeek
May 4 '15 at 21:29
I knew that. But if you do
smbios-wireless-ctl --help
, part of it has --boot Set BIOS boot-time setting.
I didn't know they fixed the Bluetooth, though; thanks for telling me.– Hitechcomputergeek
May 4 '15 at 21:29
add a comment |
On Ubuntu 16.04, I simply disabled the service from starting up using systemctl.
To do this, open up a terminal window and type the following:
sudo systemctl disable bluetooth
You can either reboot since now bluetooth will be disabled from starting up, or if you do not want to reboot and want to stop bluetooth right away, you can type:
sudo service bluetooth stop
add a comment |
On Ubuntu 16.04, I simply disabled the service from starting up using systemctl.
To do this, open up a terminal window and type the following:
sudo systemctl disable bluetooth
You can either reboot since now bluetooth will be disabled from starting up, or if you do not want to reboot and want to stop bluetooth right away, you can type:
sudo service bluetooth stop
add a comment |
On Ubuntu 16.04, I simply disabled the service from starting up using systemctl.
To do this, open up a terminal window and type the following:
sudo systemctl disable bluetooth
You can either reboot since now bluetooth will be disabled from starting up, or if you do not want to reboot and want to stop bluetooth right away, you can type:
sudo service bluetooth stop
On Ubuntu 16.04, I simply disabled the service from starting up using systemctl.
To do this, open up a terminal window and type the following:
sudo systemctl disable bluetooth
You can either reboot since now bluetooth will be disabled from starting up, or if you do not want to reboot and want to stop bluetooth right away, you can type:
sudo service bluetooth stop
answered Aug 22 '17 at 3:57
KenKen
501211
501211
add a comment |
add a comment |
We can disable bluetooth auto start this way:
sudo gedit /etc/bluetooth/main.conf
(gedit
is my fav editor, you can replace this with xed
or whatever that's installed on your system.)
At the very bottom of this file, there's this line:
#AutoEnable=false
Un-comment it, like this:
AutoEnable=false
doesn't work in ubuntu budgie 18.04
– Argento
Sep 3 '18 at 13:27
add a comment |
We can disable bluetooth auto start this way:
sudo gedit /etc/bluetooth/main.conf
(gedit
is my fav editor, you can replace this with xed
or whatever that's installed on your system.)
At the very bottom of this file, there's this line:
#AutoEnable=false
Un-comment it, like this:
AutoEnable=false
doesn't work in ubuntu budgie 18.04
– Argento
Sep 3 '18 at 13:27
add a comment |
We can disable bluetooth auto start this way:
sudo gedit /etc/bluetooth/main.conf
(gedit
is my fav editor, you can replace this with xed
or whatever that's installed on your system.)
At the very bottom of this file, there's this line:
#AutoEnable=false
Un-comment it, like this:
AutoEnable=false
We can disable bluetooth auto start this way:
sudo gedit /etc/bluetooth/main.conf
(gedit
is my fav editor, you can replace this with xed
or whatever that's installed on your system.)
At the very bottom of this file, there's this line:
#AutoEnable=false
Un-comment it, like this:
AutoEnable=false
answered Feb 20 '18 at 14:47
ShayanShayan
373419
373419
doesn't work in ubuntu budgie 18.04
– Argento
Sep 3 '18 at 13:27
add a comment |
doesn't work in ubuntu budgie 18.04
– Argento
Sep 3 '18 at 13:27
doesn't work in ubuntu budgie 18.04
– Argento
Sep 3 '18 at 13:27
doesn't work in ubuntu budgie 18.04
– Argento
Sep 3 '18 at 13:27
add a comment |
If you're using the Bluetooth applet in the top panel (blueman-applet), it has its own setting that will automatically turn Bluetooth on even if you've disabled it in other places (like /etc/bluetooth/main.conf or /etc/default/tlp).
To prevent Bluetooth from turning on at startup using the command line:
gsettings set org.blueman.plugins.powermanager auto-power-on false
Or through the GUI:
- Click the Bluetooth applet > Plugins > PowerManager > Configuration
- Uncheck Auto power-on
Next time you reboot, the Bluetooth applet will still be visible but Bluetooth will be off. To turn it on:
Click the Bluetooth applet > Turn Bluetooth On
In Ubuntu 18.04 this is the only solution I have found. Even if you change in /etc/bluetooth/main.conf, at the bottom, the option from AutoEnable=true to AutoEnable=false you cannot turn off the Bluetooth. In fact this option is for discovering new devices not for powering Bluetooth on or off.
– Alessandro D'lncal
Aug 19 '18 at 12:26
add a comment |
If you're using the Bluetooth applet in the top panel (blueman-applet), it has its own setting that will automatically turn Bluetooth on even if you've disabled it in other places (like /etc/bluetooth/main.conf or /etc/default/tlp).
To prevent Bluetooth from turning on at startup using the command line:
gsettings set org.blueman.plugins.powermanager auto-power-on false
Or through the GUI:
- Click the Bluetooth applet > Plugins > PowerManager > Configuration
- Uncheck Auto power-on
Next time you reboot, the Bluetooth applet will still be visible but Bluetooth will be off. To turn it on:
Click the Bluetooth applet > Turn Bluetooth On
In Ubuntu 18.04 this is the only solution I have found. Even if you change in /etc/bluetooth/main.conf, at the bottom, the option from AutoEnable=true to AutoEnable=false you cannot turn off the Bluetooth. In fact this option is for discovering new devices not for powering Bluetooth on or off.
– Alessandro D'lncal
Aug 19 '18 at 12:26
add a comment |
If you're using the Bluetooth applet in the top panel (blueman-applet), it has its own setting that will automatically turn Bluetooth on even if you've disabled it in other places (like /etc/bluetooth/main.conf or /etc/default/tlp).
To prevent Bluetooth from turning on at startup using the command line:
gsettings set org.blueman.plugins.powermanager auto-power-on false
Or through the GUI:
- Click the Bluetooth applet > Plugins > PowerManager > Configuration
- Uncheck Auto power-on
Next time you reboot, the Bluetooth applet will still be visible but Bluetooth will be off. To turn it on:
Click the Bluetooth applet > Turn Bluetooth On
If you're using the Bluetooth applet in the top panel (blueman-applet), it has its own setting that will automatically turn Bluetooth on even if you've disabled it in other places (like /etc/bluetooth/main.conf or /etc/default/tlp).
To prevent Bluetooth from turning on at startup using the command line:
gsettings set org.blueman.plugins.powermanager auto-power-on false
Or through the GUI:
- Click the Bluetooth applet > Plugins > PowerManager > Configuration
- Uncheck Auto power-on
Next time you reboot, the Bluetooth applet will still be visible but Bluetooth will be off. To turn it on:
Click the Bluetooth applet > Turn Bluetooth On
answered Jul 27 '18 at 17:12
bmaupinbmaupin
2,5362347
2,5362347
In Ubuntu 18.04 this is the only solution I have found. Even if you change in /etc/bluetooth/main.conf, at the bottom, the option from AutoEnable=true to AutoEnable=false you cannot turn off the Bluetooth. In fact this option is for discovering new devices not for powering Bluetooth on or off.
– Alessandro D'lncal
Aug 19 '18 at 12:26
add a comment |
In Ubuntu 18.04 this is the only solution I have found. Even if you change in /etc/bluetooth/main.conf, at the bottom, the option from AutoEnable=true to AutoEnable=false you cannot turn off the Bluetooth. In fact this option is for discovering new devices not for powering Bluetooth on or off.
– Alessandro D'lncal
Aug 19 '18 at 12:26
In Ubuntu 18.04 this is the only solution I have found. Even if you change in /etc/bluetooth/main.conf, at the bottom, the option from AutoEnable=true to AutoEnable=false you cannot turn off the Bluetooth. In fact this option is for discovering new devices not for powering Bluetooth on or off.
– Alessandro D'lncal
Aug 19 '18 at 12:26
In Ubuntu 18.04 this is the only solution I have found. Even if you change in /etc/bluetooth/main.conf, at the bottom, the option from AutoEnable=true to AutoEnable=false you cannot turn off the Bluetooth. In fact this option is for discovering new devices not for powering Bluetooth on or off.
– Alessandro D'lncal
Aug 19 '18 at 12:26
add a comment |
I using Sputnik Kernel, which fixed this on my Dell Inspiron 14R N4110.
add a comment |
I using Sputnik Kernel, which fixed this on my Dell Inspiron 14R N4110.
add a comment |
I using Sputnik Kernel, which fixed this on my Dell Inspiron 14R N4110.
I using Sputnik Kernel, which fixed this on my Dell Inspiron 14R N4110.
edited Oct 6 '12 at 12:16
Eliah Kagan
82.7k22227369
82.7k22227369
answered Sep 24 '12 at 23:53
Alex WiedermannAlex Wiedermann
111
111
add a comment |
add a comment |
I think you should edit
/etc/default/bluetooth
and set
BLUETOOTH_ENABLED=0
to disable the bluetooth service at boot
1
did not work on Ubuntu 14.04
– b1r3k
Sep 27 '15 at 17:28
add a comment |
I think you should edit
/etc/default/bluetooth
and set
BLUETOOTH_ENABLED=0
to disable the bluetooth service at boot
1
did not work on Ubuntu 14.04
– b1r3k
Sep 27 '15 at 17:28
add a comment |
I think you should edit
/etc/default/bluetooth
and set
BLUETOOTH_ENABLED=0
to disable the bluetooth service at boot
I think you should edit
/etc/default/bluetooth
and set
BLUETOOTH_ENABLED=0
to disable the bluetooth service at boot
answered Mar 6 '14 at 20:17
FabioFabio
111
111
1
did not work on Ubuntu 14.04
– b1r3k
Sep 27 '15 at 17:28
add a comment |
1
did not work on Ubuntu 14.04
– b1r3k
Sep 27 '15 at 17:28
1
1
did not work on Ubuntu 14.04
– b1r3k
Sep 27 '15 at 17:28
did not work on Ubuntu 14.04
– b1r3k
Sep 27 '15 at 17:28
add a comment |
For those of you where inserting the line rfkill block bluetooth
(or any other) in /etc/rc.local
doesn't work, try to include the same line in the end of ~/.bashrc
In my set up (Ubuntu 14.04, Thinkpad W540), no option worked inserting it in /etc/rc.local
but the former did work in bashrc. Note this will work just for the current user, not globally for all users.
add a comment |
For those of you where inserting the line rfkill block bluetooth
(or any other) in /etc/rc.local
doesn't work, try to include the same line in the end of ~/.bashrc
In my set up (Ubuntu 14.04, Thinkpad W540), no option worked inserting it in /etc/rc.local
but the former did work in bashrc. Note this will work just for the current user, not globally for all users.
add a comment |
For those of you where inserting the line rfkill block bluetooth
(or any other) in /etc/rc.local
doesn't work, try to include the same line in the end of ~/.bashrc
In my set up (Ubuntu 14.04, Thinkpad W540), no option worked inserting it in /etc/rc.local
but the former did work in bashrc. Note this will work just for the current user, not globally for all users.
For those of you where inserting the line rfkill block bluetooth
(or any other) in /etc/rc.local
doesn't work, try to include the same line in the end of ~/.bashrc
In my set up (Ubuntu 14.04, Thinkpad W540), no option worked inserting it in /etc/rc.local
but the former did work in bashrc. Note this will work just for the current user, not globally for all users.
answered Oct 19 '14 at 12:10
SamSam
535
535
add a comment |
add a comment |
On Ubuntu Studio 16.04 you can disable Bluetooth Applet in Startup in:
Session and Startup > Application Autostart > Bluetooth Applet
Here you can click in the field to disable it.
This is a perfectly good solution on my Xubuntu 17.10 machine, except for one thing: if the user wants to start using bluetooth again on the fly, he needs to execute sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service. But your solution definitely solves the bootup problem.
– Adrian Keister
Jan 30 '18 at 14:52
add a comment |
On Ubuntu Studio 16.04 you can disable Bluetooth Applet in Startup in:
Session and Startup > Application Autostart > Bluetooth Applet
Here you can click in the field to disable it.
This is a perfectly good solution on my Xubuntu 17.10 machine, except for one thing: if the user wants to start using bluetooth again on the fly, he needs to execute sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service. But your solution definitely solves the bootup problem.
– Adrian Keister
Jan 30 '18 at 14:52
add a comment |
On Ubuntu Studio 16.04 you can disable Bluetooth Applet in Startup in:
Session and Startup > Application Autostart > Bluetooth Applet
Here you can click in the field to disable it.
On Ubuntu Studio 16.04 you can disable Bluetooth Applet in Startup in:
Session and Startup > Application Autostart > Bluetooth Applet
Here you can click in the field to disable it.
edited Jan 30 '18 at 22:06
Adrian Keister
1502213
1502213
answered Aug 26 '16 at 18:05
amir-tamir-t
216214
216214
This is a perfectly good solution on my Xubuntu 17.10 machine, except for one thing: if the user wants to start using bluetooth again on the fly, he needs to execute sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service. But your solution definitely solves the bootup problem.
– Adrian Keister
Jan 30 '18 at 14:52
add a comment |
This is a perfectly good solution on my Xubuntu 17.10 machine, except for one thing: if the user wants to start using bluetooth again on the fly, he needs to execute sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service. But your solution definitely solves the bootup problem.
– Adrian Keister
Jan 30 '18 at 14:52
This is a perfectly good solution on my Xubuntu 17.10 machine, except for one thing: if the user wants to start using bluetooth again on the fly, he needs to execute sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service. But your solution definitely solves the bootup problem.
– Adrian Keister
Jan 30 '18 at 14:52
This is a perfectly good solution on my Xubuntu 17.10 machine, except for one thing: if the user wants to start using bluetooth again on the fly, he needs to execute sudo systemctl enable bluetooth.service && sudo systemctl start bluetooth.service. But your solution definitely solves the bootup problem.
– Adrian Keister
Jan 30 '18 at 14:52
add a comment |
Since Ubuntu 18.04 (with GNOME) you need to
Edit /etc/bluetooth/main.conf and find
AutoEnable = true
and change the value to:
AutoEnable = false
So this device is not powered on startup.
Edit /etc/default/tlp and find:
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit this line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
So this device is disabled on startup.
Then open Dash and search for "Startup Applications". Uncheck any items related to Bluetooth in the list. Click [Close] to save.
Point 4: Go to Settings -> Bluetooth -> Disable (at top right window).
– Omar Tariq
Jan 27 at 6:43
add a comment |
Since Ubuntu 18.04 (with GNOME) you need to
Edit /etc/bluetooth/main.conf and find
AutoEnable = true
and change the value to:
AutoEnable = false
So this device is not powered on startup.
Edit /etc/default/tlp and find:
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit this line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
So this device is disabled on startup.
Then open Dash and search for "Startup Applications". Uncheck any items related to Bluetooth in the list. Click [Close] to save.
Point 4: Go to Settings -> Bluetooth -> Disable (at top right window).
– Omar Tariq
Jan 27 at 6:43
add a comment |
Since Ubuntu 18.04 (with GNOME) you need to
Edit /etc/bluetooth/main.conf and find
AutoEnable = true
and change the value to:
AutoEnable = false
So this device is not powered on startup.
Edit /etc/default/tlp and find:
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit this line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
So this device is disabled on startup.
Then open Dash and search for "Startup Applications". Uncheck any items related to Bluetooth in the list. Click [Close] to save.
Since Ubuntu 18.04 (with GNOME) you need to
Edit /etc/bluetooth/main.conf and find
AutoEnable = true
and change the value to:
AutoEnable = false
So this device is not powered on startup.
Edit /etc/default/tlp and find:
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit this line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
So this device is disabled on startup.
Then open Dash and search for "Startup Applications". Uncheck any items related to Bluetooth in the list. Click [Close] to save.
edited Oct 25 '18 at 22:23
answered Oct 25 '18 at 5:31
naXanaXa
205110
205110
Point 4: Go to Settings -> Bluetooth -> Disable (at top right window).
– Omar Tariq
Jan 27 at 6:43
add a comment |
Point 4: Go to Settings -> Bluetooth -> Disable (at top right window).
– Omar Tariq
Jan 27 at 6:43
Point 4: Go to Settings -> Bluetooth -> Disable (at top right window).
– Omar Tariq
Jan 27 at 6:43
Point 4: Go to Settings -> Bluetooth -> Disable (at top right window).
– Omar Tariq
Jan 27 at 6:43
add a comment |
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
add a comment |
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
add a comment |
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
I add
"/etc/init.d/bluetooth stop"
into
"/etc/rc.local"
before "exit 0" command for boot with bluetooth turned off.
answered Aug 23 '12 at 13:05
Saeed ZarinfamSaeed Zarinfam
13.8k52940
13.8k52940
add a comment |
add a comment |
Solution for my notebook
"BIOS - USB Configuration - EHCI2 : Disabled"
EHCI1 is for usb ports (actually My notebook has 2 usb 2.0 ports)
add a comment |
Solution for my notebook
"BIOS - USB Configuration - EHCI2 : Disabled"
EHCI1 is for usb ports (actually My notebook has 2 usb 2.0 ports)
add a comment |
Solution for my notebook
"BIOS - USB Configuration - EHCI2 : Disabled"
EHCI1 is for usb ports (actually My notebook has 2 usb 2.0 ports)
Solution for my notebook
"BIOS - USB Configuration - EHCI2 : Disabled"
EHCI1 is for usb ports (actually My notebook has 2 usb 2.0 ports)
edited Mar 27 '14 at 19:17
answered Mar 27 '14 at 18:46
MSPMSP
11
11
add a comment |
add a comment |
Edit /etc/default/grub
:
sudo nano /etc/default/grub
and change the following line:
GRUB_CMDLINE_LINUX=""
to say this instead:
GRUB_CMDLINE_LINUX="bluetooth.blacklist=yes"
Then, update grub and reboot:
sudo update-grub
add a comment |
Edit /etc/default/grub
:
sudo nano /etc/default/grub
and change the following line:
GRUB_CMDLINE_LINUX=""
to say this instead:
GRUB_CMDLINE_LINUX="bluetooth.blacklist=yes"
Then, update grub and reboot:
sudo update-grub
add a comment |
Edit /etc/default/grub
:
sudo nano /etc/default/grub
and change the following line:
GRUB_CMDLINE_LINUX=""
to say this instead:
GRUB_CMDLINE_LINUX="bluetooth.blacklist=yes"
Then, update grub and reboot:
sudo update-grub
Edit /etc/default/grub
:
sudo nano /etc/default/grub
and change the following line:
GRUB_CMDLINE_LINUX=""
to say this instead:
GRUB_CMDLINE_LINUX="bluetooth.blacklist=yes"
Then, update grub and reboot:
sudo update-grub
answered Sep 21 '15 at 5:58
mchidmchid
23.2k25285
23.2k25285
add a comment |
add a comment |
This should disable bluetooth from starting on Debian based systems:
sudo chkconfig bluetooth off
or on RedHat based systems
systemctl disable bluetooth.service
add a comment |
This should disable bluetooth from starting on Debian based systems:
sudo chkconfig bluetooth off
or on RedHat based systems
systemctl disable bluetooth.service
add a comment |
This should disable bluetooth from starting on Debian based systems:
sudo chkconfig bluetooth off
or on RedHat based systems
systemctl disable bluetooth.service
This should disable bluetooth from starting on Debian based systems:
sudo chkconfig bluetooth off
or on RedHat based systems
systemctl disable bluetooth.service
answered Oct 16 '17 at 20:18
StanislavStanislav
21719
21719
add a comment |
add a comment |
I found another answer using tlp that works great for me with Ubuntu 18.04. Probably first tlp must be installed with
sudo apt install tlp
Then the file
/etc/default/tlp
contains some settings about devices like wifi and bluetooth. There is the key
RESTORE_DEVICE_STATE_ON_STARTUP
which is by default set to 0. After I switched it to 1 my last setting is remembered on the next boot. That means when I disable bluetooth in the top panel it stays disabled and when I enable bluetooth it stays enabled. Also there is the key
DEVICES_TO_DISABLE_ON_STARTUP
which can be set to
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
Now bluetooth will be disabled on each boot. After changing this configuration bluetooth will can be enabled and disabled through menu and panel item. I think it's better than removing it from kernel modules.
TLP is not installed by default in Ubuntu. You should update your post accordingly.
– linrunner
Feb 11 at 17:07
@linrunner Ok, didn't know what that. I tested on a fresh Ubuntu Budgie from Tuxedo. There it worked. I fixed my answer.
– Thomas Sablik
Feb 11 at 18:07
add a comment |
I found another answer using tlp that works great for me with Ubuntu 18.04. Probably first tlp must be installed with
sudo apt install tlp
Then the file
/etc/default/tlp
contains some settings about devices like wifi and bluetooth. There is the key
RESTORE_DEVICE_STATE_ON_STARTUP
which is by default set to 0. After I switched it to 1 my last setting is remembered on the next boot. That means when I disable bluetooth in the top panel it stays disabled and when I enable bluetooth it stays enabled. Also there is the key
DEVICES_TO_DISABLE_ON_STARTUP
which can be set to
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
Now bluetooth will be disabled on each boot. After changing this configuration bluetooth will can be enabled and disabled through menu and panel item. I think it's better than removing it from kernel modules.
TLP is not installed by default in Ubuntu. You should update your post accordingly.
– linrunner
Feb 11 at 17:07
@linrunner Ok, didn't know what that. I tested on a fresh Ubuntu Budgie from Tuxedo. There it worked. I fixed my answer.
– Thomas Sablik
Feb 11 at 18:07
add a comment |
I found another answer using tlp that works great for me with Ubuntu 18.04. Probably first tlp must be installed with
sudo apt install tlp
Then the file
/etc/default/tlp
contains some settings about devices like wifi and bluetooth. There is the key
RESTORE_DEVICE_STATE_ON_STARTUP
which is by default set to 0. After I switched it to 1 my last setting is remembered on the next boot. That means when I disable bluetooth in the top panel it stays disabled and when I enable bluetooth it stays enabled. Also there is the key
DEVICES_TO_DISABLE_ON_STARTUP
which can be set to
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
Now bluetooth will be disabled on each boot. After changing this configuration bluetooth will can be enabled and disabled through menu and panel item. I think it's better than removing it from kernel modules.
I found another answer using tlp that works great for me with Ubuntu 18.04. Probably first tlp must be installed with
sudo apt install tlp
Then the file
/etc/default/tlp
contains some settings about devices like wifi and bluetooth. There is the key
RESTORE_DEVICE_STATE_ON_STARTUP
which is by default set to 0. After I switched it to 1 my last setting is remembered on the next boot. That means when I disable bluetooth in the top panel it stays disabled and when I enable bluetooth it stays enabled. Also there is the key
DEVICES_TO_DISABLE_ON_STARTUP
which can be set to
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
Now bluetooth will be disabled on each boot. After changing this configuration bluetooth will can be enabled and disabled through menu and panel item. I think it's better than removing it from kernel modules.
edited Feb 11 at 18:11
answered Feb 10 at 23:31
Thomas SablikThomas Sablik
143110
143110
TLP is not installed by default in Ubuntu. You should update your post accordingly.
– linrunner
Feb 11 at 17:07
@linrunner Ok, didn't know what that. I tested on a fresh Ubuntu Budgie from Tuxedo. There it worked. I fixed my answer.
– Thomas Sablik
Feb 11 at 18:07
add a comment |
TLP is not installed by default in Ubuntu. You should update your post accordingly.
– linrunner
Feb 11 at 17:07
@linrunner Ok, didn't know what that. I tested on a fresh Ubuntu Budgie from Tuxedo. There it worked. I fixed my answer.
– Thomas Sablik
Feb 11 at 18:07
TLP is not installed by default in Ubuntu. You should update your post accordingly.
– linrunner
Feb 11 at 17:07
TLP is not installed by default in Ubuntu. You should update your post accordingly.
– linrunner
Feb 11 at 17:07
@linrunner Ok, didn't know what that. I tested on a fresh Ubuntu Budgie from Tuxedo. There it worked. I fixed my answer.
– Thomas Sablik
Feb 11 at 18:07
@linrunner Ok, didn't know what that. I tested on a fresh Ubuntu Budgie from Tuxedo. There it worked. I fixed my answer.
– Thomas Sablik
Feb 11 at 18:07
add a comment |
I had to use a brute-force method to stop bluetoothd from being automatically started at boot. I renamed the executable so it couldn't be found.
It's faster starting things in parallel. At least that's the idea.
– Douglas Leeder
Sep 28 '12 at 13:48
add a comment |
I had to use a brute-force method to stop bluetoothd from being automatically started at boot. I renamed the executable so it couldn't be found.
It's faster starting things in parallel. At least that's the idea.
– Douglas Leeder
Sep 28 '12 at 13:48
add a comment |
I had to use a brute-force method to stop bluetoothd from being automatically started at boot. I renamed the executable so it couldn't be found.
I had to use a brute-force method to stop bluetoothd from being automatically started at boot. I renamed the executable so it couldn't be found.
edited Feb 1 '13 at 8:17
Flimm
21.7k1563122
21.7k1563122
answered Jul 6 '12 at 1:02
bluesdiva2001bluesdiva2001
71
71
It's faster starting things in parallel. At least that's the idea.
– Douglas Leeder
Sep 28 '12 at 13:48
add a comment |
It's faster starting things in parallel. At least that's the idea.
– Douglas Leeder
Sep 28 '12 at 13:48
It's faster starting things in parallel. At least that's the idea.
– Douglas Leeder
Sep 28 '12 at 13:48
It's faster starting things in parallel. At least that's the idea.
– Douglas Leeder
Sep 28 '12 at 13:48
add a comment |
You can also use this Graphic application that also does this bluetooth manager
add a comment |
You can also use this Graphic application that also does this bluetooth manager
add a comment |
You can also use this Graphic application that also does this bluetooth manager
You can also use this Graphic application that also does this bluetooth manager
answered Dec 27 '14 at 13:26
deFreitasdeFreitas
204211
204211
add a comment |
add a comment |
You need to disable it from the Start Up Applications list in System Settings.
Click on the cog in the top right hand side of the menu bar and then select System Settings.
Click on Start Up Applications then scroll down until you find the bluetooth setting, take the tick from the box and you all done.
2
I can't find bluetooth in the Start Up Applications..
– Floqqi
Oct 16 '11 at 21:40
5
That doesn't actually stop the Bluetooth subsystems and hardware from running (and importantly: consuming battery). It just stops the applet running.
– Oli♦
Oct 16 '11 at 23:59
@Oli - thanks for the heads up, I never actually knew that ! I assumed if you disabled it in the start up applications it did not start the process at all.
– Mark Rooney
Oct 17 '11 at 9:44
1
Sadly, it's not in the startup applications in 11.10.
– Amanda
Jan 28 '12 at 1:24
add a comment |
You need to disable it from the Start Up Applications list in System Settings.
Click on the cog in the top right hand side of the menu bar and then select System Settings.
Click on Start Up Applications then scroll down until you find the bluetooth setting, take the tick from the box and you all done.
2
I can't find bluetooth in the Start Up Applications..
– Floqqi
Oct 16 '11 at 21:40
5
That doesn't actually stop the Bluetooth subsystems and hardware from running (and importantly: consuming battery). It just stops the applet running.
– Oli♦
Oct 16 '11 at 23:59
@Oli - thanks for the heads up, I never actually knew that ! I assumed if you disabled it in the start up applications it did not start the process at all.
– Mark Rooney
Oct 17 '11 at 9:44
1
Sadly, it's not in the startup applications in 11.10.
– Amanda
Jan 28 '12 at 1:24
add a comment |
You need to disable it from the Start Up Applications list in System Settings.
Click on the cog in the top right hand side of the menu bar and then select System Settings.
Click on Start Up Applications then scroll down until you find the bluetooth setting, take the tick from the box and you all done.
You need to disable it from the Start Up Applications list in System Settings.
Click on the cog in the top right hand side of the menu bar and then select System Settings.
Click on Start Up Applications then scroll down until you find the bluetooth setting, take the tick from the box and you all done.
answered Oct 16 '11 at 21:13
Mark RooneyMark Rooney
5,98112957
5,98112957
2
I can't find bluetooth in the Start Up Applications..
– Floqqi
Oct 16 '11 at 21:40
5
That doesn't actually stop the Bluetooth subsystems and hardware from running (and importantly: consuming battery). It just stops the applet running.
– Oli♦
Oct 16 '11 at 23:59
@Oli - thanks for the heads up, I never actually knew that ! I assumed if you disabled it in the start up applications it did not start the process at all.
– Mark Rooney
Oct 17 '11 at 9:44
1
Sadly, it's not in the startup applications in 11.10.
– Amanda
Jan 28 '12 at 1:24
add a comment |
2
I can't find bluetooth in the Start Up Applications..
– Floqqi
Oct 16 '11 at 21:40
5
That doesn't actually stop the Bluetooth subsystems and hardware from running (and importantly: consuming battery). It just stops the applet running.
– Oli♦
Oct 16 '11 at 23:59
@Oli - thanks for the heads up, I never actually knew that ! I assumed if you disabled it in the start up applications it did not start the process at all.
– Mark Rooney
Oct 17 '11 at 9:44
1
Sadly, it's not in the startup applications in 11.10.
– Amanda
Jan 28 '12 at 1:24
2
2
I can't find bluetooth in the Start Up Applications..
– Floqqi
Oct 16 '11 at 21:40
I can't find bluetooth in the Start Up Applications..
– Floqqi
Oct 16 '11 at 21:40
5
5
That doesn't actually stop the Bluetooth subsystems and hardware from running (and importantly: consuming battery). It just stops the applet running.
– Oli♦
Oct 16 '11 at 23:59
That doesn't actually stop the Bluetooth subsystems and hardware from running (and importantly: consuming battery). It just stops the applet running.
– Oli♦
Oct 16 '11 at 23:59
@Oli - thanks for the heads up, I never actually knew that ! I assumed if you disabled it in the start up applications it did not start the process at all.
– Mark Rooney
Oct 17 '11 at 9:44
@Oli - thanks for the heads up, I never actually knew that ! I assumed if you disabled it in the start up applications it did not start the process at all.
– Mark Rooney
Oct 17 '11 at 9:44
1
1
Sadly, it's not in the startup applications in 11.10.
– Amanda
Jan 28 '12 at 1:24
Sadly, it's not in the startup applications in 11.10.
– Amanda
Jan 28 '12 at 1:24
add a comment |
protected by Community♦ Oct 15 '14 at 14:26
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
I don't think that "should be the natural default configuration", people are bound to want to use Bluetooth on their computers without having to turn it on (you don't seem to have a Bluetooth mouse or keyboard, if those were your primary input devices you'd want Bluetooth on from boot). However I do agree that a way to choose how you want Bluetooth to be on boot would be useful to have.
– roadmr
May 4 '12 at 20:25
57
The normal and natural thing is to let you choose, in the bluetooth settings, whether you want it on or off when it boots. It is not natural to have people turning it off or on every time they turn on their computer. We are talking about making Linux the best desktop system, not the worst, aren't we?
– Robert
May 4 '12 at 20:30
We agree that letting people choose is the best option. See here for some possible ways of doing this. answers.launchpad.net/ubuntu/+source/bluez/+question/51440
– roadmr
May 4 '12 at 20:31
1
This is bug #1073669.
– colan
Jul 14 '15 at 20:44
3
It's kind of unbelievable that, on the 14th edition, we are still "teaching" Ubuntu developers things like "the option to have bluetooth on or off on boot should be available to normal users, and not just to those fond of searching in interminable lines of public forums".
– Rodrigo
Aug 28 '15 at 12:08