bluetooth "blues"...
-
I like to discuss this with somebody. I am using "systemctl" to control / verify that bluetooth service is actually running. Works so, so. The "problem" is AFTER I reboot the Ubuntu "bluetooth setting" - located on very right top of the desktop - ALWAYS shows "Bluetooth off". I cannot restart bluetooth using this "setting" - it does not react at all to "Bluetooth on". I am puzzled why I need to use "systemctl start bluetooth" get the service running. My code DOES not stops the service - only verifies it is running. Thanks
-
I like to discuss this with somebody. I am using "systemctl" to control / verify that bluetooth service is actually running. Works so, so. The "problem" is AFTER I reboot the Ubuntu "bluetooth setting" - located on very right top of the desktop - ALWAYS shows "Bluetooth off". I cannot restart bluetooth using this "setting" - it does not react at all to "Bluetooth on". I am puzzled why I need to use "systemctl start bluetooth" get the service running. My code DOES not stops the service - only verifies it is running. Thanks
Check to see if bluetooth is enabled
systemctl is-enabled bluetooth.service. If it is enabled, you'll need to dig into the logs to figure out why its not coming up. If it is disabled, then as root:systemctl enable --now bluetooth.servicewhich will tell systemd that it should start the bluetooth service on boot. The--nowflag is optional and will start the given service immediately. Without it, you will either have to start the service manually (systemctl start bluetooth.service) or reboot the system. It's probably a good idea to reboot the system as soon as you may after enabling the service, just to check it is coming up OK, or debug why it isn't."A little song, a little dance, a little seltzer down your pants" Chuckles the clown
-
Check to see if bluetooth is enabled
systemctl is-enabled bluetooth.service. If it is enabled, you'll need to dig into the logs to figure out why its not coming up. If it is disabled, then as root:systemctl enable --now bluetooth.servicewhich will tell systemd that it should start the bluetooth service on boot. The--nowflag is optional and will start the given service immediately. Without it, you will either have to start the service manually (systemctl start bluetooth.service) or reboot the system. It's probably a good idea to reboot the system as soon as you may after enabling the service, just to check it is coming up OK, or debug why it isn't."A little song, a little dance, a little seltzer down your pants" Chuckles the clown
Thank you, you have nailed it...I assume some of my "safety code" accidentally disabled the service. Or maybe I should blame it on bad weather, or somebody else , as is customary. What was a real challenge - navigate thru all " why are you doing that?... post detail error ...post your (formatted ) code...you have asked this before...I do not know the answwr, but L like... I am really hesitant to ask questions on this forum, I always get flamed.... Anyway, thanks for you help, much appreciated.