![](https://seccdn.libravatar.org/avatar/b4047644c59f2d63b88e9464c02743fd.jpg?s=120&d=mm&r=g)
On 03/14/2016 10:16 AM, Tom Kacvinsky wrote:
On Mar 14, 2016, at 10:56, Patrick Shanahan
wrote: * Tom Kacvinsky
[03-14-16 10:42]: I am using openSUSE Leap on a Dell Latitude E5550. Previously, when I went to "Settings | Configure Desktop | Bluetooth", it would allow me to remove devices (which is now not working) and would scan for devices (which is also now not working).
I recently updated software (security patches), but I didn’t see anything in there that would have changed how Bluetooth operates.
I don’t know how to troubleshoot this. Any ideas?
Your posts are not wrapped at < 78 chars, please adjust.
I have been called on this several times. I apologize.
First step would be "systemctl restart bluetooth" second, "systemctl status bluetooth”
That worked, bluetooth is activated and I can scan for devices and pair.
The next question I have is why did this service not start upon reboot?
Tom: On my not-all-that-different Dell 9400, bluetooth always starts at boot, but doesn't always restart on awake from hybernate or sleep. (suspend to disk, or suspend to ram) I often, but not alwayse, find my BT mouse not working upon resuming. Grrr! I used to sigh an just reboot, because it was quicker than trying all the various systemd incantations. Then I noticed that I had a "FN" key combo to enter airplane mode. Some other machines have a hardware switch. I discovered that pop to airplane mode, count to 5, pop out of airplane mode, and everything works. Further, you can explain this to your grandmother whereas you have not a single chance of getting her to remember the systemd command. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org