How can I set bluetooth off as default?
Whenever I turn my bluetooth off from the settings menu, it's back on after reboot. I know this has already been asked but I've tried all answers that have been provided and nothing seems to work.
The most popular suggestion is: Run sudoedit /etc/rc.local and add this before line with exit 0:
rfkill block bluetooth
When I do this, an empty file opens up and it's not even rc.local if I'm correct. (see screenshot).
I'm running Ubuntu 18.04 LTS.

If I run ls -l /etc/rc.local this comes up:

If I run: sudo rfkill list all:

I've tried everything in this link except installing BUM: How can I deactivate Bluetooth on system startup?
boot bluetooth settings
|
show 1 more comment
Whenever I turn my bluetooth off from the settings menu, it's back on after reboot. I know this has already been asked but I've tried all answers that have been provided and nothing seems to work.
The most popular suggestion is: Run sudoedit /etc/rc.local and add this before line with exit 0:
rfkill block bluetooth
When I do this, an empty file opens up and it's not even rc.local if I'm correct. (see screenshot).
I'm running Ubuntu 18.04 LTS.

If I run ls -l /etc/rc.local this comes up:

If I run: sudo rfkill list all:

I've tried everything in this link except installing BUM: How can I deactivate Bluetooth on system startup?
boot bluetooth settings
2
Well, what's the link to the other suggestions you tried ? Yes, the file in screenshot is a temp file, which is odd. Did you runsudoedit /etc/rc.localor did it differ somehow ? Doesls -l /etc/rc.localsuggests it's a symlink ?
– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:24
Also,sudo rfkill list alloutput would be nice to add
– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:25
1
"When I do this, an empty file opens up and it's not even rc.local if I'm correct. " Yes it is. Custom method in Linux: editing a file in use is bad practice, so a file in /tmp/ is created and mv to the place it needs to be. Next: you did not find anything on blacklisting the bt module?! I find that odd ;)
– Rinzwind
Jun 16 '18 at 9:45
I've tried everything in this link except installing BUM: askubuntu.com/questions/67758/…
– Lucy C
Jun 17 '18 at 19:22
1
Possible duplicate of How can I deactivate Bluetooth on system startup?
– naXa
Oct 25 '18 at 5:22
|
show 1 more comment
Whenever I turn my bluetooth off from the settings menu, it's back on after reboot. I know this has already been asked but I've tried all answers that have been provided and nothing seems to work.
The most popular suggestion is: Run sudoedit /etc/rc.local and add this before line with exit 0:
rfkill block bluetooth
When I do this, an empty file opens up and it's not even rc.local if I'm correct. (see screenshot).
I'm running Ubuntu 18.04 LTS.

If I run ls -l /etc/rc.local this comes up:

If I run: sudo rfkill list all:

I've tried everything in this link except installing BUM: How can I deactivate Bluetooth on system startup?
boot bluetooth settings
Whenever I turn my bluetooth off from the settings menu, it's back on after reboot. I know this has already been asked but I've tried all answers that have been provided and nothing seems to work.
The most popular suggestion is: Run sudoedit /etc/rc.local and add this before line with exit 0:
rfkill block bluetooth
When I do this, an empty file opens up and it's not even rc.local if I'm correct. (see screenshot).
I'm running Ubuntu 18.04 LTS.

If I run ls -l /etc/rc.local this comes up:

If I run: sudo rfkill list all:

I've tried everything in this link except installing BUM: How can I deactivate Bluetooth on system startup?
boot bluetooth settings
boot bluetooth settings
edited Jun 17 '18 at 23:13
Lucy C
asked Jun 16 '18 at 4:10
Lucy CLucy C
5518
5518
2
Well, what's the link to the other suggestions you tried ? Yes, the file in screenshot is a temp file, which is odd. Did you runsudoedit /etc/rc.localor did it differ somehow ? Doesls -l /etc/rc.localsuggests it's a symlink ?
– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:24
Also,sudo rfkill list alloutput would be nice to add
– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:25
1
"When I do this, an empty file opens up and it's not even rc.local if I'm correct. " Yes it is. Custom method in Linux: editing a file in use is bad practice, so a file in /tmp/ is created and mv to the place it needs to be. Next: you did not find anything on blacklisting the bt module?! I find that odd ;)
– Rinzwind
Jun 16 '18 at 9:45
I've tried everything in this link except installing BUM: askubuntu.com/questions/67758/…
– Lucy C
Jun 17 '18 at 19:22
1
Possible duplicate of How can I deactivate Bluetooth on system startup?
– naXa
Oct 25 '18 at 5:22
|
show 1 more comment
2
Well, what's the link to the other suggestions you tried ? Yes, the file in screenshot is a temp file, which is odd. Did you runsudoedit /etc/rc.localor did it differ somehow ? Doesls -l /etc/rc.localsuggests it's a symlink ?
– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:24
Also,sudo rfkill list alloutput would be nice to add
– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:25
1
"When I do this, an empty file opens up and it's not even rc.local if I'm correct. " Yes it is. Custom method in Linux: editing a file in use is bad practice, so a file in /tmp/ is created and mv to the place it needs to be. Next: you did not find anything on blacklisting the bt module?! I find that odd ;)
– Rinzwind
Jun 16 '18 at 9:45
I've tried everything in this link except installing BUM: askubuntu.com/questions/67758/…
– Lucy C
Jun 17 '18 at 19:22
1
Possible duplicate of How can I deactivate Bluetooth on system startup?
– naXa
Oct 25 '18 at 5:22
2
2
Well, what's the link to the other suggestions you tried ? Yes, the file in screenshot is a temp file, which is odd. Did you run
sudoedit /etc/rc.local or did it differ somehow ? Does ls -l /etc/rc.local suggests it's a symlink ?– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:24
Well, what's the link to the other suggestions you tried ? Yes, the file in screenshot is a temp file, which is odd. Did you run
sudoedit /etc/rc.local or did it differ somehow ? Does ls -l /etc/rc.local suggests it's a symlink ?– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:24
Also,
sudo rfkill list all output would be nice to add– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:25
Also,
sudo rfkill list all output would be nice to add– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:25
1
1
"When I do this, an empty file opens up and it's not even rc.local if I'm correct. " Yes it is. Custom method in Linux: editing a file in use is bad practice, so a file in /tmp/ is created and mv to the place it needs to be. Next: you did not find anything on blacklisting the bt module?! I find that odd ;)
– Rinzwind
Jun 16 '18 at 9:45
"When I do this, an empty file opens up and it's not even rc.local if I'm correct. " Yes it is. Custom method in Linux: editing a file in use is bad practice, so a file in /tmp/ is created and mv to the place it needs to be. Next: you did not find anything on blacklisting the bt module?! I find that odd ;)
– Rinzwind
Jun 16 '18 at 9:45
I've tried everything in this link except installing BUM: askubuntu.com/questions/67758/…
– Lucy C
Jun 17 '18 at 19:22
I've tried everything in this link except installing BUM: askubuntu.com/questions/67758/…
– Lucy C
Jun 17 '18 at 19:22
1
1
Possible duplicate of How can I deactivate Bluetooth on system startup?
– naXa
Oct 25 '18 at 5:22
Possible duplicate of How can I deactivate Bluetooth on system startup?
– naXa
Oct 25 '18 at 5:22
|
show 1 more comment
5 Answers
5
active
oldest
votes
I've tested this and it's persistent across reboots.
Click the bluetooth logo between the keyboard and battery icons on the system tray. Then click the "Bluetooth ON" selection and it changes to "Bluetooth OFF":

After comments I discovered that Ubuntu 18.04 with Gnome interface doesn't work like Ubuntu 16.04 with Unity interface.
The solution is to edit /etc/default/tlp and find:
# Radio devices to disable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit the last line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
I'm gonna assume you really did think I haven't tried the most basic solution. When I do this, the bluetooth is back on after reboot.
– Lucy C
Jun 17 '18 at 22:53
@LucyC I just noticed from your screenshots you don't even have the bluetooth icon in systray. Furthermore you are using Gnome interface and not Unity 16.04 interface like me. Are you using Ubuntu 18.04?
– WinEunuuchs2Unix
Jun 17 '18 at 23:04
I'm running Ubuntu 18.04 LTS. My bluetooth icon can be found in the dropdown settings menu as shown here: [ibb.co/h5pmaJ]
– Lucy C
Jun 17 '18 at 23:09
@LucyC I'll reboot using Ubuntu 18.04 LTS with default Gnome interface and check it out.
– WinEunuuchs2Unix
Jun 17 '18 at 23:10
@LucyC After rebooting into Ubuntu 18.40 I was shocked to learn under the Gnome interface the setting isn't retained. On searching for a solution I found a duplicate question with an accepted answer so voted to close your question as a duplicate. So now I'll boot back into 16.04 which just works :)
– WinEunuuchs2Unix
Jun 17 '18 at 23:20
|
show 7 more comments
Well, I have a suggession. I think most of the people will try to make the devices to remember the state of the previous shutdown. Thus if wifi/bluetooth is turned off/on before the previous shutdown, then after rebooting, wifi/bluetooth remains off/on according the previous state.
To do this, go to the file /etc/default/tlp and search for the line
RESTORE_DEVICE_STATE_ON_STARTUP=0
This is set as "0" by default, which means that remembering the state of radio is disabled by default. To make it remember the previous state, replace "0" with "1".
If you set this as "1", the lines after that will not be read by the system.
If you specifically wants to set some radio to be on or off at start up, then follow the lines
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
and
#DEVICES_TO_ENABLE_ON_STARTUP="bluetooth wifi wwan"
and remove the '#' to activate any of those line. And you can choose between bluetooth/wifi/wwan or all of them.
Do as you need.
add a comment |
I have a workaround for your case...
I'm using Ubuntu Mate 18.04, in my case I just click on "MENU/Preferences/Startup Applications".
A window called "Startup Applications Preferences" pops up. Find the entry called "Blueman Applet" and remove the tick/tag from it so that it becomes disabled (grayed out). As a result, all the applications related with Bluetooth will not load the next time(s) you boot up your system.
The annoying part is that you will have to reverse this procedure and reboot to get bluetooth back to work in case you need it.
Hope this helps
JaMedSyS
add a comment |
the rc.local way appears right to me, yet I'd do it slightly different:
sudo nano /etc/rc.local
either the file is empty - it has just been created by you - or not, edit it to look like this:
#!/bin/sh
rfkill block bluetooth
exit 0
the first and last lines are important.
add a comment |
I work under Xubuntu 18.04. Here is a solution that finally worked for me.
First, I edited the file
/etc/bluetooth/main.conf(undersudomode enabled). At the very end of the file, I changed the lineAutoEnable=truetoAutoEnable=falseSecond, I went to the main menu, then picked
Settings > Session and Startup. In theApplications autostartsection I disabledBlueman applet(see line 2 in the picture below).

- After reboot, the
Blueman appleticon is no longer visible in the system tray but if you enterrfkill list allin the terminal, you see the following:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Which means that the Bluetooth is now off. The key to the problem, it seems, is ridiculously simple. Any attempt to switch the Blueman applet on also switches on the Bluetooth no matter what happened before. So, no Blueman applet, no more Bluetooth on boot. At least, for me.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1047018%2fhow-can-i-set-bluetooth-off-as-default%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've tested this and it's persistent across reboots.
Click the bluetooth logo between the keyboard and battery icons on the system tray. Then click the "Bluetooth ON" selection and it changes to "Bluetooth OFF":

After comments I discovered that Ubuntu 18.04 with Gnome interface doesn't work like Ubuntu 16.04 with Unity interface.
The solution is to edit /etc/default/tlp and find:
# Radio devices to disable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit the last line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
I'm gonna assume you really did think I haven't tried the most basic solution. When I do this, the bluetooth is back on after reboot.
– Lucy C
Jun 17 '18 at 22:53
@LucyC I just noticed from your screenshots you don't even have the bluetooth icon in systray. Furthermore you are using Gnome interface and not Unity 16.04 interface like me. Are you using Ubuntu 18.04?
– WinEunuuchs2Unix
Jun 17 '18 at 23:04
I'm running Ubuntu 18.04 LTS. My bluetooth icon can be found in the dropdown settings menu as shown here: [ibb.co/h5pmaJ]
– Lucy C
Jun 17 '18 at 23:09
@LucyC I'll reboot using Ubuntu 18.04 LTS with default Gnome interface and check it out.
– WinEunuuchs2Unix
Jun 17 '18 at 23:10
@LucyC After rebooting into Ubuntu 18.40 I was shocked to learn under the Gnome interface the setting isn't retained. On searching for a solution I found a duplicate question with an accepted answer so voted to close your question as a duplicate. So now I'll boot back into 16.04 which just works :)
– WinEunuuchs2Unix
Jun 17 '18 at 23:20
|
show 7 more comments
I've tested this and it's persistent across reboots.
Click the bluetooth logo between the keyboard and battery icons on the system tray. Then click the "Bluetooth ON" selection and it changes to "Bluetooth OFF":

After comments I discovered that Ubuntu 18.04 with Gnome interface doesn't work like Ubuntu 16.04 with Unity interface.
The solution is to edit /etc/default/tlp and find:
# Radio devices to disable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit the last line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
I'm gonna assume you really did think I haven't tried the most basic solution. When I do this, the bluetooth is back on after reboot.
– Lucy C
Jun 17 '18 at 22:53
@LucyC I just noticed from your screenshots you don't even have the bluetooth icon in systray. Furthermore you are using Gnome interface and not Unity 16.04 interface like me. Are you using Ubuntu 18.04?
– WinEunuuchs2Unix
Jun 17 '18 at 23:04
I'm running Ubuntu 18.04 LTS. My bluetooth icon can be found in the dropdown settings menu as shown here: [ibb.co/h5pmaJ]
– Lucy C
Jun 17 '18 at 23:09
@LucyC I'll reboot using Ubuntu 18.04 LTS with default Gnome interface and check it out.
– WinEunuuchs2Unix
Jun 17 '18 at 23:10
@LucyC After rebooting into Ubuntu 18.40 I was shocked to learn under the Gnome interface the setting isn't retained. On searching for a solution I found a duplicate question with an accepted answer so voted to close your question as a duplicate. So now I'll boot back into 16.04 which just works :)
– WinEunuuchs2Unix
Jun 17 '18 at 23:20
|
show 7 more comments
I've tested this and it's persistent across reboots.
Click the bluetooth logo between the keyboard and battery icons on the system tray. Then click the "Bluetooth ON" selection and it changes to "Bluetooth OFF":

After comments I discovered that Ubuntu 18.04 with Gnome interface doesn't work like Ubuntu 16.04 with Unity interface.
The solution is to edit /etc/default/tlp and find:
# Radio devices to disable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit the last line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
I've tested this and it's persistent across reboots.
Click the bluetooth logo between the keyboard and battery icons on the system tray. Then click the "Bluetooth ON" selection and it changes to "Bluetooth OFF":

After comments I discovered that Ubuntu 18.04 with Gnome interface doesn't work like Ubuntu 16.04 with Unity interface.
The solution is to edit /etc/default/tlp and find:
# Radio devices to disable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
Edit the last line to read:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
edited Jun 17 '18 at 23:53
answered Jun 17 '18 at 21:38
WinEunuuchs2UnixWinEunuuchs2Unix
44.7k1080171
44.7k1080171
I'm gonna assume you really did think I haven't tried the most basic solution. When I do this, the bluetooth is back on after reboot.
– Lucy C
Jun 17 '18 at 22:53
@LucyC I just noticed from your screenshots you don't even have the bluetooth icon in systray. Furthermore you are using Gnome interface and not Unity 16.04 interface like me. Are you using Ubuntu 18.04?
– WinEunuuchs2Unix
Jun 17 '18 at 23:04
I'm running Ubuntu 18.04 LTS. My bluetooth icon can be found in the dropdown settings menu as shown here: [ibb.co/h5pmaJ]
– Lucy C
Jun 17 '18 at 23:09
@LucyC I'll reboot using Ubuntu 18.04 LTS with default Gnome interface and check it out.
– WinEunuuchs2Unix
Jun 17 '18 at 23:10
@LucyC After rebooting into Ubuntu 18.40 I was shocked to learn under the Gnome interface the setting isn't retained. On searching for a solution I found a duplicate question with an accepted answer so voted to close your question as a duplicate. So now I'll boot back into 16.04 which just works :)
– WinEunuuchs2Unix
Jun 17 '18 at 23:20
|
show 7 more comments
I'm gonna assume you really did think I haven't tried the most basic solution. When I do this, the bluetooth is back on after reboot.
– Lucy C
Jun 17 '18 at 22:53
@LucyC I just noticed from your screenshots you don't even have the bluetooth icon in systray. Furthermore you are using Gnome interface and not Unity 16.04 interface like me. Are you using Ubuntu 18.04?
– WinEunuuchs2Unix
Jun 17 '18 at 23:04
I'm running Ubuntu 18.04 LTS. My bluetooth icon can be found in the dropdown settings menu as shown here: [ibb.co/h5pmaJ]
– Lucy C
Jun 17 '18 at 23:09
@LucyC I'll reboot using Ubuntu 18.04 LTS with default Gnome interface and check it out.
– WinEunuuchs2Unix
Jun 17 '18 at 23:10
@LucyC After rebooting into Ubuntu 18.40 I was shocked to learn under the Gnome interface the setting isn't retained. On searching for a solution I found a duplicate question with an accepted answer so voted to close your question as a duplicate. So now I'll boot back into 16.04 which just works :)
– WinEunuuchs2Unix
Jun 17 '18 at 23:20
I'm gonna assume you really did think I haven't tried the most basic solution. When I do this, the bluetooth is back on after reboot.
– Lucy C
Jun 17 '18 at 22:53
I'm gonna assume you really did think I haven't tried the most basic solution. When I do this, the bluetooth is back on after reboot.
– Lucy C
Jun 17 '18 at 22:53
@LucyC I just noticed from your screenshots you don't even have the bluetooth icon in systray. Furthermore you are using Gnome interface and not Unity 16.04 interface like me. Are you using Ubuntu 18.04?
– WinEunuuchs2Unix
Jun 17 '18 at 23:04
@LucyC I just noticed from your screenshots you don't even have the bluetooth icon in systray. Furthermore you are using Gnome interface and not Unity 16.04 interface like me. Are you using Ubuntu 18.04?
– WinEunuuchs2Unix
Jun 17 '18 at 23:04
I'm running Ubuntu 18.04 LTS. My bluetooth icon can be found in the dropdown settings menu as shown here: [ibb.co/h5pmaJ]
– Lucy C
Jun 17 '18 at 23:09
I'm running Ubuntu 18.04 LTS. My bluetooth icon can be found in the dropdown settings menu as shown here: [ibb.co/h5pmaJ]
– Lucy C
Jun 17 '18 at 23:09
@LucyC I'll reboot using Ubuntu 18.04 LTS with default Gnome interface and check it out.
– WinEunuuchs2Unix
Jun 17 '18 at 23:10
@LucyC I'll reboot using Ubuntu 18.04 LTS with default Gnome interface and check it out.
– WinEunuuchs2Unix
Jun 17 '18 at 23:10
@LucyC After rebooting into Ubuntu 18.40 I was shocked to learn under the Gnome interface the setting isn't retained. On searching for a solution I found a duplicate question with an accepted answer so voted to close your question as a duplicate. So now I'll boot back into 16.04 which just works :)
– WinEunuuchs2Unix
Jun 17 '18 at 23:20
@LucyC After rebooting into Ubuntu 18.40 I was shocked to learn under the Gnome interface the setting isn't retained. On searching for a solution I found a duplicate question with an accepted answer so voted to close your question as a duplicate. So now I'll boot back into 16.04 which just works :)
– WinEunuuchs2Unix
Jun 17 '18 at 23:20
|
show 7 more comments
Well, I have a suggession. I think most of the people will try to make the devices to remember the state of the previous shutdown. Thus if wifi/bluetooth is turned off/on before the previous shutdown, then after rebooting, wifi/bluetooth remains off/on according the previous state.
To do this, go to the file /etc/default/tlp and search for the line
RESTORE_DEVICE_STATE_ON_STARTUP=0
This is set as "0" by default, which means that remembering the state of radio is disabled by default. To make it remember the previous state, replace "0" with "1".
If you set this as "1", the lines after that will not be read by the system.
If you specifically wants to set some radio to be on or off at start up, then follow the lines
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
and
#DEVICES_TO_ENABLE_ON_STARTUP="bluetooth wifi wwan"
and remove the '#' to activate any of those line. And you can choose between bluetooth/wifi/wwan or all of them.
Do as you need.
add a comment |
Well, I have a suggession. I think most of the people will try to make the devices to remember the state of the previous shutdown. Thus if wifi/bluetooth is turned off/on before the previous shutdown, then after rebooting, wifi/bluetooth remains off/on according the previous state.
To do this, go to the file /etc/default/tlp and search for the line
RESTORE_DEVICE_STATE_ON_STARTUP=0
This is set as "0" by default, which means that remembering the state of radio is disabled by default. To make it remember the previous state, replace "0" with "1".
If you set this as "1", the lines after that will not be read by the system.
If you specifically wants to set some radio to be on or off at start up, then follow the lines
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
and
#DEVICES_TO_ENABLE_ON_STARTUP="bluetooth wifi wwan"
and remove the '#' to activate any of those line. And you can choose between bluetooth/wifi/wwan or all of them.
Do as you need.
add a comment |
Well, I have a suggession. I think most of the people will try to make the devices to remember the state of the previous shutdown. Thus if wifi/bluetooth is turned off/on before the previous shutdown, then after rebooting, wifi/bluetooth remains off/on according the previous state.
To do this, go to the file /etc/default/tlp and search for the line
RESTORE_DEVICE_STATE_ON_STARTUP=0
This is set as "0" by default, which means that remembering the state of radio is disabled by default. To make it remember the previous state, replace "0" with "1".
If you set this as "1", the lines after that will not be read by the system.
If you specifically wants to set some radio to be on or off at start up, then follow the lines
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
and
#DEVICES_TO_ENABLE_ON_STARTUP="bluetooth wifi wwan"
and remove the '#' to activate any of those line. And you can choose between bluetooth/wifi/wwan or all of them.
Do as you need.
Well, I have a suggession. I think most of the people will try to make the devices to remember the state of the previous shutdown. Thus if wifi/bluetooth is turned off/on before the previous shutdown, then after rebooting, wifi/bluetooth remains off/on according the previous state.
To do this, go to the file /etc/default/tlp and search for the line
RESTORE_DEVICE_STATE_ON_STARTUP=0
This is set as "0" by default, which means that remembering the state of radio is disabled by default. To make it remember the previous state, replace "0" with "1".
If you set this as "1", the lines after that will not be read by the system.
If you specifically wants to set some radio to be on or off at start up, then follow the lines
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
and
#DEVICES_TO_ENABLE_ON_STARTUP="bluetooth wifi wwan"
and remove the '#' to activate any of those line. And you can choose between bluetooth/wifi/wwan or all of them.
Do as you need.
answered Jul 2 '18 at 17:55
SurajitSurajit
716
716
add a comment |
add a comment |
I have a workaround for your case...
I'm using Ubuntu Mate 18.04, in my case I just click on "MENU/Preferences/Startup Applications".
A window called "Startup Applications Preferences" pops up. Find the entry called "Blueman Applet" and remove the tick/tag from it so that it becomes disabled (grayed out). As a result, all the applications related with Bluetooth will not load the next time(s) you boot up your system.
The annoying part is that you will have to reverse this procedure and reboot to get bluetooth back to work in case you need it.
Hope this helps
JaMedSyS
add a comment |
I have a workaround for your case...
I'm using Ubuntu Mate 18.04, in my case I just click on "MENU/Preferences/Startup Applications".
A window called "Startup Applications Preferences" pops up. Find the entry called "Blueman Applet" and remove the tick/tag from it so that it becomes disabled (grayed out). As a result, all the applications related with Bluetooth will not load the next time(s) you boot up your system.
The annoying part is that you will have to reverse this procedure and reboot to get bluetooth back to work in case you need it.
Hope this helps
JaMedSyS
add a comment |
I have a workaround for your case...
I'm using Ubuntu Mate 18.04, in my case I just click on "MENU/Preferences/Startup Applications".
A window called "Startup Applications Preferences" pops up. Find the entry called "Blueman Applet" and remove the tick/tag from it so that it becomes disabled (grayed out). As a result, all the applications related with Bluetooth will not load the next time(s) you boot up your system.
The annoying part is that you will have to reverse this procedure and reboot to get bluetooth back to work in case you need it.
Hope this helps
JaMedSyS
I have a workaround for your case...
I'm using Ubuntu Mate 18.04, in my case I just click on "MENU/Preferences/Startup Applications".
A window called "Startup Applications Preferences" pops up. Find the entry called "Blueman Applet" and remove the tick/tag from it so that it becomes disabled (grayed out). As a result, all the applications related with Bluetooth will not load the next time(s) you boot up your system.
The annoying part is that you will have to reverse this procedure and reboot to get bluetooth back to work in case you need it.
Hope this helps
JaMedSyS
answered Oct 30 '18 at 17:02
JamMedSySJamMedSyS
114
114
add a comment |
add a comment |
the rc.local way appears right to me, yet I'd do it slightly different:
sudo nano /etc/rc.local
either the file is empty - it has just been created by you - or not, edit it to look like this:
#!/bin/sh
rfkill block bluetooth
exit 0
the first and last lines are important.
add a comment |
the rc.local way appears right to me, yet I'd do it slightly different:
sudo nano /etc/rc.local
either the file is empty - it has just been created by you - or not, edit it to look like this:
#!/bin/sh
rfkill block bluetooth
exit 0
the first and last lines are important.
add a comment |
the rc.local way appears right to me, yet I'd do it slightly different:
sudo nano /etc/rc.local
either the file is empty - it has just been created by you - or not, edit it to look like this:
#!/bin/sh
rfkill block bluetooth
exit 0
the first and last lines are important.
the rc.local way appears right to me, yet I'd do it slightly different:
sudo nano /etc/rc.local
either the file is empty - it has just been created by you - or not, edit it to look like this:
#!/bin/sh
rfkill block bluetooth
exit 0
the first and last lines are important.
answered Nov 30 '18 at 20:14
db429db429
1,336517
1,336517
add a comment |
add a comment |
I work under Xubuntu 18.04. Here is a solution that finally worked for me.
First, I edited the file
/etc/bluetooth/main.conf(undersudomode enabled). At the very end of the file, I changed the lineAutoEnable=truetoAutoEnable=falseSecond, I went to the main menu, then picked
Settings > Session and Startup. In theApplications autostartsection I disabledBlueman applet(see line 2 in the picture below).

- After reboot, the
Blueman appleticon is no longer visible in the system tray but if you enterrfkill list allin the terminal, you see the following:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Which means that the Bluetooth is now off. The key to the problem, it seems, is ridiculously simple. Any attempt to switch the Blueman applet on also switches on the Bluetooth no matter what happened before. So, no Blueman applet, no more Bluetooth on boot. At least, for me.
add a comment |
I work under Xubuntu 18.04. Here is a solution that finally worked for me.
First, I edited the file
/etc/bluetooth/main.conf(undersudomode enabled). At the very end of the file, I changed the lineAutoEnable=truetoAutoEnable=falseSecond, I went to the main menu, then picked
Settings > Session and Startup. In theApplications autostartsection I disabledBlueman applet(see line 2 in the picture below).

- After reboot, the
Blueman appleticon is no longer visible in the system tray but if you enterrfkill list allin the terminal, you see the following:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Which means that the Bluetooth is now off. The key to the problem, it seems, is ridiculously simple. Any attempt to switch the Blueman applet on also switches on the Bluetooth no matter what happened before. So, no Blueman applet, no more Bluetooth on boot. At least, for me.
add a comment |
I work under Xubuntu 18.04. Here is a solution that finally worked for me.
First, I edited the file
/etc/bluetooth/main.conf(undersudomode enabled). At the very end of the file, I changed the lineAutoEnable=truetoAutoEnable=falseSecond, I went to the main menu, then picked
Settings > Session and Startup. In theApplications autostartsection I disabledBlueman applet(see line 2 in the picture below).

- After reboot, the
Blueman appleticon is no longer visible in the system tray but if you enterrfkill list allin the terminal, you see the following:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Which means that the Bluetooth is now off. The key to the problem, it seems, is ridiculously simple. Any attempt to switch the Blueman applet on also switches on the Bluetooth no matter what happened before. So, no Blueman applet, no more Bluetooth on boot. At least, for me.
I work under Xubuntu 18.04. Here is a solution that finally worked for me.
First, I edited the file
/etc/bluetooth/main.conf(undersudomode enabled). At the very end of the file, I changed the lineAutoEnable=truetoAutoEnable=falseSecond, I went to the main menu, then picked
Settings > Session and Startup. In theApplications autostartsection I disabledBlueman applet(see line 2 in the picture below).

- After reboot, the
Blueman appleticon is no longer visible in the system tray but if you enterrfkill list allin the terminal, you see the following:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Which means that the Bluetooth is now off. The key to the problem, it seems, is ridiculously simple. Any attempt to switch the Blueman applet on also switches on the Bluetooth no matter what happened before. So, no Blueman applet, no more Bluetooth on boot. At least, for me.
edited 2 hours ago
answered 4 hours ago
Alexei KouprianovAlexei Kouprianov
466
466
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1047018%2fhow-can-i-set-bluetooth-off-as-default%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Well, what's the link to the other suggestions you tried ? Yes, the file in screenshot is a temp file, which is odd. Did you run
sudoedit /etc/rc.localor did it differ somehow ? Doesls -l /etc/rc.localsuggests it's a symlink ?– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:24
Also,
sudo rfkill list alloutput would be nice to add– Sergiy Kolodyazhnyy
Jun 16 '18 at 4:25
1
"When I do this, an empty file opens up and it's not even rc.local if I'm correct. " Yes it is. Custom method in Linux: editing a file in use is bad practice, so a file in /tmp/ is created and mv to the place it needs to be. Next: you did not find anything on blacklisting the bt module?! I find that odd ;)
– Rinzwind
Jun 16 '18 at 9:45
I've tried everything in this link except installing BUM: askubuntu.com/questions/67758/…
– Lucy C
Jun 17 '18 at 19:22
1
Possible duplicate of How can I deactivate Bluetooth on system startup?
– naXa
Oct 25 '18 at 5:22