Skip to content

Use next in line portal.conf when no backend is defined for a particular interface #1865

@maxcabrajac

Description

@maxcabrajac

Operating System

N/A

XDG Desktop Portal version

1.20

XDG Desktop Portal version (Other)

No response

Desktop Environment

Other

Desktop Environment (Other)

N/A

Expected Behavior

(Using gnome as an example)

$XDG_DATA_DIRS/xdg-desktop-portal/gnome-portals.conf

[preferred]
default=gnome;gtk;
org.freedesktop.impl.portal.Secret=gnome-keyring;

$XDG_CONFIG_HOME/xdg-desktop-portal/gnome-portals.conf

[preferred]
org.freedesktop.impl.portal.FileChooser=gtk;

The user expects the following:
Calls to the FileChooser interface will be processed by x-d-p-gtk.
Calls to the Secret interface will be processed by x-d-p-gnome-keyring.
Calls to any other interface will be processed by either x-d-p-gnome or x-d-p-gtk (because of default=gnome;gtk;)

Current Behavior

Calls to the FileChooser interface will be processed by x-d-p-gtk.
Calls to any other interface will fallback to the deprecated backend choosing method (based on UseIn & Lexicographical ordering)

Anything else we should know?

Currently, x-d-p looks for $DIR/portals.conf if $DIR/$DESKTOP-portals.conf doesn't exist.
If $HIGH_PRECEDENCE_DIR/$DESKTOP-portals.conf exists, should $HIGH_PRECEDENCE_DIR/portals.conf be read before $LOW_PRECEDENCE_DIR/$DESKTOP-portals.conf or skipped?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions