You are not logged in.
When Bluez.Experimental flag is true (I need it to read headphones battery level) it spams to the journal messages like:
bluetoothd[398]: Adv Monitor app :1.803 disconnected from D-Bus
Just look at it:
139580! messages in a few days
Basically it logs each second or even faster.
I do want to have an abilities to read the battery status of my headphones (Galaxy Buds Pro) but obviously I really don't what to have that much spam in the journal.
The only thing I've changed in the /etc/bluetooth/main.conf is the Experimental flag. Everything else is commented out.
Bluetooth works normally. Battery status from experimental flag works too.
Why this can happen? Where should I look to investigate?
Or can I at least set LogLevel for Bluez? (couldn't find how to do this yet)?
Last edited by Dmitry Gashko (2023-04-21 18:52:23)
Offline
Ok, I got it.
Honestly it's just too obvious and stupid.
I had an idea that these messages can be not and error messages but ignored it for some time...
But it's actually just each my requests for a battery status.
Each time I call:
bluetoothctl info $1 | awk -F '[()]' '/Battery Percentage/ {print $2}'
It logged the message to the journal.
I'm using it in polybar module I've wrote recently at 2 am... and it has default interval in 0.5s.
I'll increase it to a few minutes and it should be good
Offline
Hi Had a nearly identical issue but the spamming was caused by the bluetooth system tray applet. Disabling this made the messages go away for me.
Offline