Currently Fedora 35 KDE just ships with xdg-desktop-portal-gtk, but there is a problem, as stated from the bug report I link below:
xdg-desktop-portal-gtk explicitly disables the building of the Settings portal.
This breaks font antialiasing in kde wayland.
The workaround is to install xdg-desktop-portal-gnome. I think xdg-desktop-portal-gnome should be included by default in Fedora 35 KDE unless xdg-desktop-portal-gtk can be fixed before release.
https://bugzilla.redhat.com/show_bug.cgi?id=2012315
https://github.com/flatpak/xdg-desktop-portal-gtk/issues/355
We should be shipping xdg-desktop-portal-kde, something is wrong here. Do we need to ship xdg-desktop-portal-gnome too?
xdg-desktop-portal-kde
xdg-desktop-portal-gnome
@siosm, @rdieter: are we missing something here?
Metadata Update from @ngompa: - Issue tagged with: experience
Yes, keep shipping xdg-desktop-portal-kde. However, now, xdg-desktop-portal-gtk is broken because it was updated and built without the settings portal, that was shifted to xdg-desktop-portal-gnome. So now, on KDE wayland, in order to have good anti aliased fonts in GTK applications on wayland, xdg-desktop-portal-gnome needs to be shipped also, in addition to xdg-desktop-portal-kde, or xdg-desktop-portal-gtk needs to be rebuilt with the settings portal which is now optional.
Basically, without xdg-desktop-portal-gnome, fonts are jagged (non-antialiased) in GTK applications on flatpak, in KDE wayland session. Previously xdg-desktop-portal-gtk, which I think comes by default, fixed that. However, the latest update to xdg-desktop-portal-gtk removed the settings portal needed for font settings in flatpak applications, now there's a new xdg-desktop-portal-gnome package that is needed. xdg-desktop-portal-kde does not contain the needed settings portal for gtk applications running in flatpak.
Oh man, what a mess... 🤦‍♂️
@ngompa Do you understand the issue?
Yeah, sadly I do. The transition to xdg-desktop-portal-gnome for GNOME is unfortunately rather disruptive since they're yanking settings from xdg-desktop-portal-gtk in the process.
xdg-desktop-portal-gtk
The runtime dependencies for xdg-desktop-portal-gnome don't look that bad, so we can ship it. But how is the more interesting question. We get xdg-desktop-portal-gtk through the rich dependency that pulls it in when gtk3 is installed. Do we ask for this with gtk4 then? Or do we just bite the bullet and add it to the kickstart to pull it in?
gtk3
gtk4
I'm not sure, I'm not a developer / packager, just a passionate end user who likes to report bugs.
Also reported in https://discussion.fedoraproject.org/t/logout-login-bugs-in-plasma-wayland-should-i-be-using-x11/33226/7
I think we should at least add it to the default set of packages for Kinoite as Flatpaks are the primary way to install applications there. No opinion for the classic KDE Spin.
It's not like we don't have Flatpak enablement shipped in the mainline KDE spin either, so I'm inclined to ship it there too, it's just I'm not sure what the best mechanism is.
We can add it to our comps group.
https://pagure.io/workstation-ostree-config/pull-request/247
https://pagure.io/fedora-comps/pull-request/683
Metadata Update from @siosm: - Issue tagged with: kinoite
Merged the comps PR
Metadata Update from @siosm: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.