distributions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: classabbyamp <abby@voidlinux.org>
To: Sam James <sam@gentoo.org>, distributions@lists.linux.dev
Subject: Re: Integration work needed for >=xdg-desktop-portal-1.18.0
Date: Fri, 13 Oct 2023 23:15:16 -0400	[thread overview]
Message-ID: <5CC94C02-DF99-4A13-9576-58B0F809CA63@voidlinux.org> (raw)
In-Reply-To: <87sf6dap1g.fsf@gentoo.org>



On October 13, 2023 10:55:21 p.m. EDT, Sam James <sam@gentoo.org> wrote:
>Hi all,
>
>xdg-desktop-portal-1.18.0 changes its behaviour if no portals are
>configured by the user, installed portals, or desktop environments.
>
>Simon has a good summary at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050911#35
>for what one needs to do.
>
>I've filed a Gentoo tracker bug at https://bugs.gentoo.org/915704
>with a list of things I'm aware of that need handling, but I'll
>include a list here of some useful references:
>* https://github.com/flatpak/xdg-desktop-portal/issues/1017
>* https://github.com/flatpak/xdg-desktop-portal/issues/1077
>* https://github.com/flatpak/xdg-desktop-portal/issues/1102
>
>Thanks to abby from Void and to psykose as well for the heads up.
>
>best,
>sam
>


On Void we're shipping a default portals.conf to ensure all users have at least some working portal, regardless of WM or DE (assuming they installed one of the backends):

    [preferred]
    default=*

in the lowest-precedence location, /usr/share/xdg-desktop-portal.

More of the rationale behind this is available in the commit:
https://github.com/void-linux/void-packages/commit/b4c404aac0af3ced08671a8840cd261198689cef

      parent reply	other threads:[~2023-10-14  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-14  2:55 Integration work needed for >=xdg-desktop-portal-1.18.0 Sam James
2023-10-14  3:11 ` classabbyamp
2023-10-14  3:15 ` classabbyamp [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=5CC94C02-DF99-4A13-9576-58B0F809CA63@voidlinux.org \
    --to=abby@voidlinux.org \
    --cc=distributions@lists.linux.dev \
    --cc=sam@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).