Solved Bluetooth Quit Working.

Solved issue
Sherri is a Cat

Sherri is a Cat

Well-Known Member
Joined
May 8, 2021
Messages
1,178
Reaction score
677
Credits
10,199
WARNING

Please be patient with my brain. I'm exhausted, my life is still crazy!

Thank you.

HP 14 Laptop

HP 14" PC Laptop

I was watching the news, Bluetooth speaker connected. No problems.
Went to the bathroom.
Came back.
Integrated laptop speakers are in use now instead of the Bluetooth
Bluetooth icon is missing from the system tray.
Opening the Bluetooth manager, I don't see my device. I can't search for devices.
Yes, the device IS ON
My phone DOES recognize and pair with the Bluetooth speaker
Eventually this message pops up.


1715660800724.png



I updated the system.
Rebooted
No change

I decided to take the lazy fix. I used a Snapshot in Timeshift.
Rebooted
It didn't work.

'rfkill list' does not indicate any existence of a kill switch for Bluetooth devices.

1715662314714.png



Just for giggles, I entered rfkill unblock bluetooth. Nothing happened.

1715662512380.png



Maybe something happened with Blueman??

'gsettings get org.blueman.plugins.po'


1715662890922.png



I'm still a newbie. My brain is running at about 15% capacity lately. Things look like gibberish and I'm having trouble figuring out what to do from here.

I hope this is clear!
Thank you!
 


G'day Sherri, I am not of much use in the bluetooth department, but you might provide the output for

Code: 
systemctl status bluetooth.service

to whomever happens along, for starters.

Good luck.

Wiz
 
I had a similar experience [once] and it was due to the headphone's battery running down
 
Code: 
systemctl status bluetooth.service
○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth ser>
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth ser>
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth ser>
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth ser>
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pres>
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth serv>
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth serv>
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth serv>
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth serv>
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset>
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth servic>
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth servic>
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth servic>
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth servic>
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: e>
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service b>
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service b>
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service b>
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service b>
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being s>
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being s>
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being s>
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being s>
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
























○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 00:04:55 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:05:46 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:24:13 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 00:25:27 PsuedoBoo systemd[1]: Condition check resulted in Bluetooth service being skipped.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-9/9 (END)
 
Brickwizard said:
I had a similar experience [once] and it was due to the headphone's battery running down
Click to expand...
GatorsFan said:
I was like @Brickwizard - batteries going dead, dead or weak batteries make for no connection
Click to expand...

Did that change the system settings though?
The speaker still had a 30% charge on it.
I don't even have a Bluetooth icon in the system tray anymore.

I have some more updates. I'll install those and try again.

1715714244824.png
 
Try
sudo systemctl start bluetooth.service
Click to expand...
now open the GUI utility for the Bluetooth and make sure Bluetooth is set on "on"
in the terminal type

bluetoothctl
Click to expand...
make sure that the command

show
Click to expand...
actually shows something similar to

bluetooth]# show
Controller 20:16:D8:95:E5:03 (public)
Name: debian
Alias: debian
Class: 0x007c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
Click to expand...
 
Sherri is a Cat said:
The speaker still had a 30% charge on it.
Click to expand...
Give it a charge....maybe leave it plugged in?..is that possible?
Sherri is a Cat said:
I don't even have a Bluetooth icon in the system tray anymore.
Click to expand...
click on menu...type in Startup Apllications....

Is Blueman Applet present there ?

One click to highlight it....make sure it is turned ON there.......then click on the arrow down the bottom....that will run it now..
 
linuxhall.org

Troubleshooting Bluetooth Connectivity Issues in Linux: Step-by-Step

Bluetooth technology has become an integral part of our lives, allowing us to connect our devices wirelessly and stream audio, transfer files, and connect peripherals effortlessly. While Bluetooth on Linux is generally reliable, like any technology, it can sometimes run into connectivity issues.
linuxhall.org
 
Good news, it's working again. I don't know why.

What happened followed by some thoughts on possible reasons or factors that may have caused this.

***First a note on a special note that may or may not deserve it's own thread, I'm not sure. We seem to have a tendency to get side tracked with tangents around here:oops:. My note on a side note is related in that it's rooted in this thread so I'll leave it here for now.

I'm glad it's working again. However, I want to know why it's working again. This is how I learned everything about the Giant. This is a brick in my foundation of Linux knowledge. My next problem may not have anything to do with Bluetooth devices. In my experience, something in the nuts and bolts of this issue could very well help with trouble shooting some other issue, even if it doesn't seem to be related. This is a learning experience for me. :D

So there's that.

The other thing is that my life is still really crazy. I don't have nearly as much time to spend on Linux as I did a couple of months ago. I started this thread last night, but couldn't get back to it until nearly a day later. (I had to stop writing this post 8 hours ago too). Therefor, this shouldn't be a priority for anyone.

So now, this is what happened.

The updates were for Brave, Zoom and Ungoogled. They don't seem to be related and shouldn't have anything to do with Bluetooth connections, drivers, etc., etc. Drawing on my experience with the Giant, it could.

I updated them and then restarted the system. Still no change.

Again drawing on my experience with the Giant, sometimes the system has to be shut down and left that way for a while to get things going again. I did that. I left it off for about 10 minutes. When I started up the system again, the Bluetooth system icon reappeared in the tray. My PC is connected to the speaker and working fine. And thank god for that. I can't stand the integrated speakers on this laptop!!!

As for why this happened, I have a few thoughts.

Right now I'm still using this cheap laptop. I suspect it's probably more like a Chromebook than an actual laptop. I didn't want to spend much on a laptop because I prefer my ASUS. I also didn't think I'd still be using it a month later.

HP Stream - 14-cb171wm Product Specifications

Maybe it's the hardware. This laptop only has 4GB of RAM and a 64 GB hard disc drive. HDD, not an SSD.

1715720400671.png


Because the HDD is so small, I'm only keeping one snap shot. This laptop is a temporary solution for me. If I have to reinstall LM, I'm fine with that. I have all of my files backed up.

I have a 128GB flash drive I could use for SnapShots. I'll have to ask @wizardfromoz to help me with that. I'll want to put them on a partition and I'm not particularly concerned about keeping very many.

So those are my thoughts. Now I'm going to look closer at the previous replies.
 
Sherri is a Cat said:
I have a 128GB flash drive I could use for SnapShots.
Click to expand...
Plug the 128gb flash drive into the laptop

In the Settings of Timeshift, go to Location, and look for the flash drive. When you have located it, click beside it to choose that location. All snapshots will then save to that flash drive.
There is no need to partition that flash drive. Timeshift will automatically create a folder which only it will use.
 
Condobloke said:
linuxhall.org

Troubleshooting Bluetooth Connectivity Issues in Linux: Step-by-Step

Bluetooth technology has become an integral part of our lives, allowing us to connect our devices wirelessly and stream audio, transfer files, and connect peripherals effortlessly. While Bluetooth on Linux is generally reliable, like any technology, it can sometimes run into connectivity issues.
linuxhall.org
Click to expand...
I've seen a lot of people having issues with Bluetooth. Until now, I thought I was the exception.

I guess I'm not so exceptional.
 
I'm not sure I should mark this thread as "Solved". Bluetooth is fine now, but I don't think this thread would be useful. The only thing I actually did was shut down the laptop for a while. I guess that part might help, but I don't think this thread would be good reference material.
 
Mark it solved anyway....at least you have stated you are unaware what actually " fixed" it.

Someone else may just close the lid and walk away for a while and have the same lucky ending.

That's as much as you can do
 
The code I pasted in a previous reply to Wizardfromoz shows this

○ bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pres>

Active: inactive (dead)

Why would shutting down the system for a while reactivate it?
 
who knows?....not me. Bluetooth and I are definitely not acquainted well enough for me to know the answer to that
 
Condobloke said:
There is no need to partition that flash drive.
Click to expand...

Actually, Brian - you do need to partition it, with one partition, but you do need to format it to to EXT4 - only filesystem, Timeshift with work with, unless using the BTRFS.

Once formatted to EXT4, if not parititioned, Timeshift will generate its own folder, named Timeshift.

Wiz
 
Last edited:
Edited above
 
You must log in or register to reply here.

Staff online

Members online

Total: 655 (members: 9, guests: 646)

Latest posts

Top