All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Stefan Herbrechtsmeier
	<stefan.herbrechtsmeier-oss@weidmueller.com>,
	f_l_k@t-online.de, Yi Zhao <yi.zhao@windriver.com>
Cc: openembedded-core@lists.openembedded.org,
	Scott Murray <scott.murray@konsulko.com>
Subject: Re: [OE-core] [PATCH] bluez5: install /var/lib/bluetooth directory
Date: Thu, 14 Apr 2022 17:22:19 +0100	[thread overview]
Message-ID: <1e34b7db2161ffbfeb4c4091c81759923a8e45db.camel@linuxfoundation.org> (raw)
In-Reply-To: <7a6794ed-2ddf-b64d-ea33-cb11eb3759d2@weidmueller.com>

On Wed, 2022-04-13 at 10:21 +0200, Stefan Herbrechtsmeier wrote:
> Hi,
> 
> Am 11.04.2022 um 09:17 schrieb Stefan Herbrechtsmeier via 
> lists.openembedded.org:
> > Am 08.04.2022 um 22:03 schrieb Markus Volk via lists.openembedded.org:
> > > also had this issue and found out, that the bluetooth service did come 
> > > up, once bluetooth was enabled
> > > 
> > > My fix was to edit like this
> > > 
> > > ReadWritePaths=:/var/lib/bluetooth
> > > 
> > > The colon ensures that the service won't fail if the directory doesn't 
> > > exist
> > 
> > Regarding the documentation the ReadOnlyPaths and ReadWritePaths makes 
> > not sense because ProtectSystem=full mounts /usr, boot loader and /etc 
> > directories read-only.
> > 
> > Have somebody report the problem to the bluez project?
> 
> I have open an issue:
> https://github.com/bluez/bluez/issues/329
> 
> I will post a patch when we come to a solution.

We have a slight challenge in that I'd like to build 4.0 rc2 but I think there
will be complaints if this is left broken.

I'm going to post a version of your patch and hope that improves things. If
anyone knows of issues with that patch please let me know ASAP.

Cheers,

Richard



      reply	other threads:[~2022-04-14 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  8:15 [PATCH] bluez5: install /var/lib/bluetooth directory Yi Zhao
2022-04-08  8:34 ` [OE-core] " Stefan Herbrechtsmeier
2022-04-08  9:23   ` Yi Zhao
2022-04-08 10:51     ` Stefan Herbrechtsmeier
2022-04-08 11:01       ` Yi Zhao
2022-04-08 20:03         ` Markus Volk
2022-04-11  7:17           ` Stefan Herbrechtsmeier
     [not found]           ` <16E4C65A42F3BFA4.4406@lists.openembedded.org>
2022-04-13  8:21             ` Stefan Herbrechtsmeier
2022-04-14 16:22               ` Richard Purdie [this message]

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=1e34b7db2161ffbfeb4c4091c81759923a8e45db.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=f_l_k@t-online.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=scott.murray@konsulko.com \
    --cc=stefan.herbrechtsmeier-oss@weidmueller.com \
    --cc=yi.zhao@windriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.