xdg-desktop-portal-gtk is needed by some GTK apps installed as Appimages and Flatpak to fix anti-aliasing and various problems on KDE Plasma, the one that shouldn’t be installed is xdg-desktop-portal-gnome.
After removing xdg-desktop-portal-gtk then rebooting, the issue is still persistent, for now only downgrading those 3 packages fixes it.
Very old issue that for some reason needed to be explicitly addressed months ago even though no one should have mutliple portal frontends, and kde certainly shouldnt have the gtk version…
Though … your described issue should likely have nothing to do with the portal(s).
Also … why are you reposting?
Oh I see aragorn sorta told you to … but I doubt they meant come here with your portal assumptions.
You were already told to remove xdg-desktop-portal-gtk.
Notice it depends on portal. No particular backend, though many unobservant users may end up believing that *portal-gtk is somehow required because its the first suggestion to fill the dep, though any can be used, and on kde it should be … *portal-kde.
And … it is probably worth noting if your ‘problem apps’ are these kinds of non-native format like Flatpaks, etc.
Ah, so in the specific case of using Wayland+Flatpak+Gtk on a Non-gtk desktops an unresolved bug (now not considered a bug?) dictates using *-portal-gtk.
News to me.
But still only one will be used at a given time. And I have portal/portal-kde installed with no erroneous affect on gtk/FF … and you state that downgrading has an impact … I have to then assume its something to do with *portal-gtk and/or your environment (variables).
Multiple backends can be installed, and they are located in /usr/share/xdg-desktop-portal/portals/*.portal. Each portal backend file contains a list of interfaces that it can handle, and the desktop environments that it can be used in. When a request is made, xdg-desktop-portal will use the XDG_CURRENT_DESKTOPenvironment variable to determine which backend it will use for the request. If more than one backend can be used for the current desktop, the first one in alphabetical order is chosen. If no backend for the current desktop can handle the interface, no backend is available for the current desktop, or xdg-desktop-portal can’t determine the current desktop, then it will choose the first portal in alphabetical order between all of the installed portals that support the requested interface.
I use that variable too (only on firefox) in order … to use the kde portal.
But here it has not had a negative affect - before or after recent unstable upgrade.
Fonts are also fine, but I dont use flatpak.
Stop. Has anyone actually looked at the upstream changes with 1.18.0 and the Arch package changes regarding it? No? Then please do that before recycling old information that may or may not have been ever accurate to begin with.
Rework how portal implementations are loaded. This new, more robust system allows selecting specific backends for specific portals, and layering them when necessary. Platforms that provide portals implementation are encouraged to provide a suitable configuration file.
But its not really elaborated upon.
I suppose man portals.conf is where one would look …
For what its worth I created
# Use xdg-desktop-portal-kde for every portal interface...
But with only the one portal it may not have been necessary.
Folks with multiple on the other hand may wish to configure the file.
Are you sure it’s actually the GTK portal that they use? I am asking because I have noticed that some applications — e.g. telegram-desktop — have begun using the qt6 version of the portal instead of the qt5 version.