Source: lomiri-session Severity: normal Tags: trixie sid User: xdg-desktop-por...@packages.debian.org Usertags: portals.conf
xdg-desktop-portal 1.17.x introduces a new way to select which portals will be used for which desktop environments, modelled on mimeapps.list: - each desktop environment should provide a file like /usr/share/xdg-desktop-portal/lomiri-portals.conf - the filename is ${DESKTOP}-portals.conf where ${DESKTOP} is the desktop environment's entry in $XDG_CURRENT_DESKTOP (the same as the DesktopNames from /usr/share/{x,wayland-}sessions/*.desktop), folded to lower case - sysadmins and users can override this via files named portals.conf or ${DESKTOP}-portals.conf in various locations like /etc/xdg-desktop-portal and ~/.config/xdg-desktop-portal Please see portals.conf(5) or its source code https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst for full details. As a backwards-compatibility mechanism, x-d-p will fall back to trying to guess the most appropriate portals from the portals' UseIn= fields, but it will log warnings when it does that, and anyway Debian doesn't currently ship any portal backends that are flagged as suitable for Lomiri. Please add a lomiri-portals.conf to tell x-d-p more explicitly what backends Lomiri is meant to be using by default. For example, if it's a GTK-based environment where xdg-desktop-portal-gtk is the most appropriate backend, it might look like this: [preferred] default=gtk; I don't know much about Lomiri, so I can't assess what the most appropriate portal backend for it would be! But it seems to be a descendant of Ubuntu's Unity, so GTK is probably reasonably appropriate. Or if it has its own portal(s), a more elaborate lomiri-portals.conf like the one added for GNOME in https://salsa.debian.org/gnome-team/gnome-session/-/commit/b201c9c40e3adc7bf0b1c3504bef4c8602aac31d might be desirable. Thanks, smcv