I see a heap of bluetooth stuff in the logs

qruqs · 21 December 2025 21:11

Stuff like this:

dec 21 19:15:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 19:15:10 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

Not just one or two lines, there are hundreds of them, seems to spit a pair of lines out every 30 seconds or so, as if it’s looking for something that should be there. But I have, to my knowledge, never had a bluetooth device connected, ever, on any computer. And most certainly not this one.

Any idea how to stop that? Sure, it’s just some log entries, but the logs get drowned by all these lines. Something I should turn off, then what? And how? I checked this “Bluez” thing using pamac (GUI) and it says that Qt6 is involved, and some gadget called bluedevil (o.Ô).

inxi -E tells me:

Bluetooth:
  Message: No bluetooth data found.

Need more info? Ask.

Thanks.

Nachlese · 21 December 2025 21:34

Your system doesn’t even have a bluetooth adapter?

You could try stopping and/or disabling the service:

systemctl status bluetooth.service
systemctl stop bluetooth.service
systemctl disable bluetooth.service

… if that works:
remember that you did that when, some time in the future, you might wonder why it doesn’t want to work

nikgnomic · 21 December 2025 21:46

If you don’t need Bluetooth support, uninstall bluez

pamac remove bluez

qruqs · 21 December 2025 21:49

I don’t think there is one, but I’m not sure how to interpret this:

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

dec 21 22:36:40 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:37:10 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:37:40 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:38:10 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:38:40 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:39:10 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:39:40 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:40:10 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:40:40 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
dec 21 22:41:10 majtaytre systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

This “dead” thing probably means that I now have to hold a funeral, or perhaps perform root canal surgery. If a tooth turns blue, then that’s severe toothache. 8)

I’ll try the rest of your suggestions and see what happens and report back later after inspecting the logs.

Thanks.

@nikgnomic Maybe, but the option @Nachlese suggested strikes me as a little better. Then, as he said, I can just turn the daemon on again. If I uninstall the software/driver, I must also remember what it was I uninstalled. I’ll keep your suggestion in mind, though. Might come in handy later, if the other option doesn’t work.

Thanks.

Nachlese · 21 December 2025 21:52

it tells you that the bluetooth service is enabled (system will try to start it),
that it is not the default setting that it is enabled
and that it is inactive (dead) because it couldn’t be started
I’d guess because there is no bluetooth adapter to be started …

Aragorn · 21 December 2025 21:59

It’s required as a dependency for fwupd, so it may not be wise to uninstall it.

I would recommend masking it instead.

qruqs · 21 December 2025 22:07

Okay, here’s what the logs say now:

dec 21 23:05:40 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:05:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:04:40 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:04:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:03:40 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:03:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:02:40 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:02:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:01:40 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:01:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false

Seems to me that only one of the lines disappeared. @Aragorn said something about “masking”, is that something other than what I just did?

Aragorn · 21 December 2025 22:09

sudo systemctl mask bluetooth.service

… prevents any other service from starting it as a dependency.

qruqs · 21 December 2025 22:14

Okay, tried that:

$ sudo systemctl mask bluetooth.service
[sudo] password for qruqs: 
Created symlink '/etc/systemd/system/bluetooth.service' → '/dev/null'.

That service I turned off, must not be running or anything before this works…?

I get this in the logs anyway:

dec 21 23:12:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:11:40 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:11:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:10:40 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false
dec 21 23:10:10 majtaytre kdeconnectd[4936]: Cannot find Bluez 5 adapter for device search false

qruqs · 21 December 2025 22:22

Aha! I found this:
https://www.mail-archive.com/kde-bugs-dist@kde.org/msg1122258.html

Might be worth waiting for a fix?

Nachlese · 21 December 2025 23:11

Isn’t that also a service that could be disabled?
I’d guess so, from the name.
Or some autostart option in your Plasma settings?
I’m not familiar with Plasma - there are many people here who are.

scotty65 · 21 December 2025 23:21

Try opening KDE Connect from the Application Launcher, or by running kdeconnect-app from a terminal.

When the GUI appears, click on the configuration icon at the bottom of the left column (next to your machine name). That will open the settings where you can disable the Bluetooth backend option:

soundofthunder · 22 December 2025 01:38

You may wish to disable Bluetooth as a backend for KDE Connect:

qruqs · 22 December 2025 06:26

Silence! At last. All night it’s been writing those lines to the log.

@scotty65 found it. I see @soundofthunder [found out || knew about] the same thing, but Scotty was first, so I’ll mark his suggestion as the Solution.

Thanks to all! 8)

soundofthunder · 22 December 2025 07:56

The warning message was a dead giveaway, as is said.

nikgnomic · 22 December 2025 11:21

ArchWiki - Bluetooth - Installation

Install the bluez package, providing the Bluetooth protocol stack.

system · 25 December 2025 11:21

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.