[SOLVED] Disable bluetooth at startup on Linux Mint 19 Cinnamon.

[vishgaur]

This is not a question but a solution itself.
I am writing this solution because I searched it a lot. I almost died searching for a solution to my problem "How to disable bluetooth at the startup on Linux Mint 19, Cinnamon, TARA" and found NO SOLUTION AT ALL ON THE WHOLE WEB.
That was pretty strange.

Solutions those did not work:

1. Code: Select all

   sudo service bluetooth stop

2. Code: Select all

   sudo gedit /etc/rc.local

   I had no file named rc.local in my directory and thus opening it from terminal showed an empty text file. So, adding anything to it was meaningless.

3. Code: Select all

   sudo systemctl disable bluetooth.service

   Didn't even disable already active bluetooth that I could have done with 2 clicks right away. Useless.

4. Code: Select all

   sudo xed /etc/bluetooth/main.conf

   Edited last line to false (default is FALSE, IDK how my default was set to TRUE. Maybe because I had tried this solution earlier and when it didn't work I forgot to change the entry to default value).

5. Code: Select all

   rfkill block bluetooth

   It disabled my bluetooth but only once, and bluetooth again restarted on next reboot/boot. So, all it did was something again I could do with 2 simple clicks, then why to type the terminal command?

Finally, the solution that worked for me was nowhere on web. How I came to this solution? After using LM for 3 months I became quite familiar with codes and settings on Linux and started to resolve my issues myself.
One day I was trying to setup an executable command to execute on startup each and every time I start my system. So, I headed to the startup apps from start menu and created a custom command. There I got the idea that

Code: Select all

rfkill block bluetooth

was able to stop bluetooth but just once, why not create a custom command for it on startup so that each time I start my system, this command gets executed and disables bluetooth on startup.

SOLUTION:

1. GO TO: Start Menu>>Startup Applications
2. Click on + (Soft Button denoted by "PLUS/ADDITION/+" sign/symbol at the bottom of the "Startup Applications" window).
3. Click on "Custom command."
4. Add any name/description you like ( I named DISABLE BLUETOOTH, name and description doesn't matter, what matters is the command)
5. Add Command as:

   Code: Select all

   rfkill block bluetooth

You can test it by selecting the new entry you made in startup applications menu and executing it manually by clicking on gear icon and then on every reboot the command will execute by itself and bluetooth will get disabled after reboot.

Hope it helps someone who is already frustrated by the non-working solutions.

[ArisBos]

Great!! I searched long on the internet, until I found your solution. Many thanks!

[anywayitgoeson]

Cheers for the solution. I was getting really frustrated by all those ...pseudo solutions until I came across your solution. Simple!

[Luontokoodaus]

Registered just to say thanks a lot for posting!

[Sir Charles]

Code: Select all

sudo systemctl disable bluetooth.service

Didn't even disable already active bluetooth that I could have done with 2 clicks right away. Useless.

Code: Select all

sudo systemctl disable --now bluetooth.service

would have done it.

For an "stronger disablement":

Code: Select all

sudo systemctl mask --now bluetooth.service

disable NAME...
Disables one or more units. This removes all symlinks to the unit
files backing the specified units from the unit configuration
directory, and hence undoes any changes made by enable or link.

--now
When used with enable, the units will also be started. When used
with disable or mask, the units will also be stopped. The start or
stop operation is only carried out when the respective enable or
disable operation has been successful.


mask NAME...
Mask one or more units, as specified on the command line. This will
link these unit files to /dev/null, making it impossible to start
them. This is a stronger version of disable, since it prohibits all
kinds of activation of the unit, including enablement and manual
activation. Use this option with care. This honors the --runtime
option to only mask temporarily until the next reboot of the
system. The --now option may be used to ensure that the units are
also stopped. This command expects valid unit names only, it does
not accept unit file paths.

unmask NAME...
Unmask one or more unit files, as specified on the command line.
This will undo the effect of mask. This command expects valid unit
names only, it does not accept unit file paths.

from: man sytsemctl

[Zhu Jia You]

Code: Select all

sudo apt remove --purge blueberry
sudo apt install blueman

System settings ==> Preferences ==> Startup Applications ==> Blueman Applet ==> TURN OFF IT

This works for me on Linux Mint 19.2 Cinnamon

[Monsieurzik]

To get the tip.

[quini]

Hi!

Worked for me! Thanks!

[vishgaur]

Glad to see that it worked for many people.

I've seen people giving solutions that I had already tried then (2 years ago).

They might be working today but to be honest none of them worked back then. What I did works on older OS versions and newer ones as well. It was nothing but automatic execution of command to disable bluetooth at startup. It was handy because it only disabled bluetooth once and if you needed bluetooth then it was just one click away.
Other solutions might disable it as badly as you would need to troubleshoot in order to enable it (but back then, nothing disabled it).

[JuanjoD]

Great! Thanks!

Edit1: Just needed to include full path to rfkill in command

Edit2: In the end, I'm using what is described here https://winaero.com/disable-bluetooth-a ... r-blueman/ as I use blueman

[hman2]

Code: Select all

sudo systemctl disable --now bluetooth.service

would have done it.

For an "stronger disablement":

Code: Select all

sudo systemctl mask --now bluetooth.service

Nope. Simply yields

Code: Select all

Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
insserv: warning: current start runlevel(s) (empty) of script `bluetooth' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `bluetooth' overrides LSB defaults (0 1 6).
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
insserv: warning: current start runlevel(s) (empty) of script `bluetooth' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `bluetooth' overrides LSB defaults (0 1 6).

but leaves bluetooth running. What puzzles me is that the whole bluetooth subsystem isn't even bothered by the fact that I have no BT hardware, at all.. It's just a waste of ressources.

but rfkill block bluetooth doesn't get rid of it, too... So there is still no solution.