From: Bastien Nocera <hadess@hadess.net>
To: Jan-Michael Brummer <jan.brummer@tabos.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/1] Add cover art support
Date: Tue, 04 Aug 2026 00:29:37 +0200 [thread overview]
Message-ID: <a2f0a4fdec3a761053ae83ee06c51adbe6cec3ff.camel@hadess.net> (raw)
In-Reply-To: <6716CF9D-9856-4371-B55E-FFB8E6914B74@tabos.org>
On Mon, 2026-08-03 at 23:03 +0200, Jan-Michael Brummer wrote:
> Maybe you have an alternative solution in mind? I'm open to change
> it.
I think you might need to extend MPRIS to allow making image data
available instead of a URL.
This could also help with avoiding, say, gnome-shell having to make
https calls to fetch a remote cover, or third-party playback control
apps having to cross apps boundaries to get to another sandbox app's
cover art.
Maybe this new feature is what we want?
https://gitlab.freedesktop.org/mpris/mpris-spec/-/merge_requests/4
I looked through the MPRIS repo after writing the above.
Cheers
> Am 3. August 2026 22:56:39 MESZ schrieb Bastien Nocera
> <hadess@hadess.net>:
> > Hey,
> >
> > On Mon, 2026-08-03 at 21:55 +0200, Jan-Michael wrote:
> > > # Filesystem lockdown
> > > -ProtectHome=true
> > > +# Cover art referenced by MediaPlayer1 metadata (mpris:artUrl)
> > > usually
> > > +# lives in the user's home directory (e.g. ~/.cache of the
> > > player),
> > > so
> > > +# bluetoothd needs read access to serve it via the AVRCP BIP
> > > responder.
> > > +ProtectHome=read-only
> > >
> >
> > This is going to be a show-stopper.
> >
> > Having a root-running daemon rummaging around in user's files is
> > not
> > something we want *at all*.
> >
> > Cheers
next prev parent reply other threads:[~2026-08-03 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 19:55 [PATCH BlueZ 0/1] Add cover art support Jan-Michael
2026-08-03 19:55 ` [PATCH BlueZ 1/1] " Jan-Michael
2026-08-03 20:56 ` Bastien Nocera
[not found] ` <6716CF9D-9856-4371-B55E-FFB8E6914B74@tabos.org>
2026-08-03 22:29 ` Bastien Nocera [this message]
2026-08-03 21:29 ` bluez.test.bot
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=a2f0a4fdec3a761053ae83ee06c51adbe6cec3ff.camel@hadess.net \
--to=hadess@hadess.net \
--cc=jan.brummer@tabos.org \
--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