Linux bluetooth development
 help / color / mirror / Atom feed
From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 88cb39: bluetooth.service: Fix ConfigurationDirectory warning
Date: Thu, 20 Aug 2026 02:56:54 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1148981/000000-88cb39@github.com> (raw)

  Branch: refs/heads/1148981
  Home:   https://github.com/bluez/bluez
  Commit: 88cb39994075a97ad282b5769fe4c29411a6d38a
      https://github.com/bluez/bluez/commit/88cb39994075a97ad282b5769fe4c29411a6d38a
  Author: Bastien Nocera <hadess@hadess.net>
  Date:   2026-08-20 (Thu, 20 Aug 2026)

  Changed paths:
    M src/bluetooth.service.in

  Log Message:
  -----------
  bluetooth.service: Fix ConfigurationDirectory warning

When running "systemctl start bluetooth.service" on some systems, this
error would appear:
systemd[8067]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)

ConfigurationDirectoryMode was mistakenly thought to help sandbox the
daemon, but the service configuration already sets ProtectSystem=strict
but "If [ProtectSystem is] set to "strict" the entire file system
hierarchy is mounted read-only", so bluetoothd can't write to
/etc/bluetooth anyway.

Fixes: 00cfb36e20e3 ("bluetooth.service: Set ConfigurationDirectoryMode")
Closes: https://github.com/bluez/bluez/issues/414



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-08-20  9:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bluez/bluez/push/refs/heads/1148981/000000-88cb39@github.com \
    --to=noreply@github.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox