Arch Linux

Cbhihe

Member

Registered: 2017-04-09

Posts: 233

[SOLVED] Host complains about bluetooth config dir mode

Background info:
On an up to date Arch system, which just underwent a recovery from a near catastrophic event: "> sudo chown -R radicale:radicale /"
The system now seems operational, complete with gdm, but glitches may remain.

Issue:
The following cropped up in the outputs of "systemctl status bluetooth.service" and of "sudo journalctl -xeu bluetooth":

> systemctl status bluetooth.service
...
systemd[1291]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
...
> sudo journalctl -eu bluetooth
Oct 04 11:35:26 HOST systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Oct 04 11:35:27 HOST systemd[1]: Starting Bluetooth service...
Oct 04 11:35:27 HOST systemd[895]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Oct 04 11:35:27 HOST bluetoothd[895]: Bluetooth daemon 5.65
Oct 04 11:35:27 HOST systemd[1]: Started Bluetooth service.
Oct 04 11:35:27 HOST bluetoothd[895]: Starting SDP server
Oct 04 11:35:27 HOST bluetoothd[895]: Bluetooth management interface 1.22 initialized

/sys/class/bluetooth only contains a link named hci0 that points to directory /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0.
That target directory has permissions 755 (drwxr-xr-x), but I don't know whether that is the correct place to change permission to octal 555.
The bluetooth.service seems to function well as far as device pairing, sending and receiving files are concerned.

Is acting on this necessary ? How ?

Last edited by Cbhihe (2022-10-04 13:36:13)

---

I like strawberries, therefore I'm not a bot.

Cbhihe

Member

Registered: 2017-04-09

Posts: 233

Re: [SOLVED] Host complains about bluetooth config dir mode

This is actually a small Debian bug -a rather harmless one at that- reported here https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1866517.html.

Modifying systemd's bluetooth.service unit, i.e. changing the ConfigurationDirectoryMode value from 0555 to 0755, reconciles the /etc/bluetooth directory created by bluez with mode 0755 with the service unit's key-value setting of 0555. Warnings disappears after:

> sudo systemctl daemon-reload
> sudo systemctl restart bluetooth

---

I like strawberries, therefore I'm not a bot.