Description of problem: Right now, xdg-desktop-portal-gtk explicitly disables the building of the Settings portal. This is a problem, because: - GTK within a Flatpak environment reads the font and DPI settings from the `org.gnome.desktop.interface` settings namespace. - The namespace is *not* available at all from any portals other than the GTK and GNOME implementations. Version-Release number of selected component (if applicable): 1.10 How reproducible: Very easily. Steps to Reproduce: 1. Run the following command on the host system (you can substitute many other settings here, but we'll just use font-hinting): gdbus call -e -d org.freedesktop.portal.Desktop -o /org/freedesktop/portal/desktop -m org.freedesktop.portal.Settings.Read org.gnome.desktop.interface font-hinting 2. Run it inside any Flatpak shell, e.g.: flatpak run --command=gdbus org.freedesktop.Platform//21.08 call -e -d org.freedesktop.portal.Desktop -o /org/freedesktop/portal/desktop -m org.freedesktop.portal.Settings.Read org.gnome.desktop.interface font-hinting 3. Compare the output of the two. On Workstation, they both return the same result. On the KDE spin, the version inside the Flatpak will fail, due to the settings key not existing. Actual results: Font settings are available to Flatpaks so that they can display their graphics correctly. Expected results: Font settings are not available inside Flatpaks. Additional info: You can see in the GTK source code where the settings are only read from two different namespaces: https://gitlab.gnome.org/GNOME/gtk/-/blob/master/gdk/wayland/gdkdisplay-wayland.c#L1478-1515 Neither of these are available via the KDE portal exclusively.
Installing xdg-desktop-portal-gnome and rebooting works around the issue for now.
Could re-enabling the settings portal regress anything on Workstation or KDE? Since users have been installing xdg-desktop-portal-gnome anyways, and nothing critical seems to be going wrong, I think it is suitable to re-enable the settings portal here for now. I am curious if there's a better way to solve this, but for now it's probably better to just quickly fix this since 35 release is coming up.
Note this is both an upstream AND a downstream bug. We need to fix the upstream defaults to unbreak other distros, but that's not enough because we also have them explicitly set in our downstream spec. (In reply to Vincent Chernin from comment #2) > Could re-enabling the settings portal regress anything on Workstation or KDE? Maybe, but if so we'll just need to figure out how to deal with it.
Note upstream has merged a fix. https://github.com/flatpak/xdg-desktop-portal-gtk/pull/362 What's left is for upstream to tag a new release, and then for this package to be updated (and to stop explictly disabling appchooser and settings).
(In reply to Vincent Chernin from comment #4) > (and to stop explictly disabling appchooser and settings). Hi David, OK for me to make this change?
FEDORA-2021-328b84f07c has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-328b84f07c
This change will not affect Workstation, as both xdg-desktop-portal-gtk and xdg-desktop-portal-gnome are included there. The upstream release will be good for defaults, but this can be handled entirely downstream as well.
FEDORA-2021-328b84f07c has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-328b84f07c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-328b84f07c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-328b84f07c has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.