Reputation: 69
I am actually trying to figure out where the DBG("") prints are going when I do a music stream using bluez to my headset. So basically I want to know where all the bluez debug messages are getting printed, be it any kind of bluetooth operation. ex: scan, inquiry , connect and so on .
Hopefully someone can help me with this . Thanks in advance .
Upvotes: 6
Views: 17939
Reputation: 183
To add to datafridge's answer above, I didn't have /usr/lib/systemd/system/bluetooth.service
in Ubuntu 16.04 with BlueZ 5.41.
The file was at /etc/systemd/system/bluetooth.target.wants/bluetooth.service
and the entry to be modified was
ExecStart=/usr/lib/bluez5/bluetooth/bluetoothd –d
The logs can also be seen using
journalctl --unit=bluetooth -f
Upvotes: 10
Reputation: 157
I have no Ubuntu here at the moment, but this is the way it works on Fedora and I'm sure it is very similar on Ubuntu, especially the systemd-part:
enable debugging by adding a -d
after
ExecStart=/usr/libexec/bluetooth/bluetoothd
in /usr/lib/systemd/system/bluetooth.service
Save, then:
$ systemctl daemon-reload
$ systemctl restart bluetooth
Now you get your information in /var/log/syslog
Upvotes: 11