guss77
December 13, 2024, 7:10am
21
I have verified that Neon channels (at least the ones I’m tracking - which are all other than unstable) are now back on xdg-desktop-portal 1.18.4, that doesn’t have that issue.
For tracking, as I don’t expect anyone to take interest in a comment on a closed GitHub issue (it’s just the nature of the beast
opened 08:47AM - 12 Dec 24 UTC
bug
### Operating System
Neon 6.2
### XDG Desktop Portal version
Other
### XDG D… esktop Portal version (Other)
1.19.0
### Desktop Environment
KDE
### Desktop Environment (Other)
_No response_
### Expected Behavior
with `GTK_USE_PORTAL=1` (needed in order for GTK apps to use the desktop environment file dialogs) on Wayland, GTK3 apps should look and behave like they do on X11 and also on Wayland without `GTK_USE_PORTAL` (except for the portal file dialogs):
This is how `awf-gtk3` looks for me on Plasma Wayland, without `GTK_USE_PORTAL=1` :
We can also get the same behavior by setting `GTK_USE_PORTAL=1` and forcing XWayland rendering.
### Current Behavior
This is how `awf-gtk3` looks for me on Plasma Wayland, with `GTK_USE_PORTAL=1`
This behavior is new for 1.19.0 - it works fine if I downgrade to 1.18.3. Looking at the D-Bus calls, it looks like XDG Desktop Portal does not call the `gtk` implementation service (and depending on its startup triggers, it may no even start if it is set to start lazily with systemd D-Bus trigger).
### Steps to Reproduce
1. Install xdg-desktop-portal 1.19.0
2. Set the environment variable `GTK_USE_PORTAL=1`
3. Start a Plasma Wayland session
4. Start any GTK 3 application.
### Anything else we should know?
This behavior was originally reported on the closed issue #1123 - that was closed as dup of #1112. I'm reporting this again as (a) probably nobody pays attention to closed issues; (b) at least this behavior seems unrelated to #1112 (and I believe also the originally reported behavior there).
My `/usr/share/xdg-desktop-portal/kde-portals.conf` - which I know XDG Desktop Portal reads, because I `strace`d it - looks like this:
```
[preferred]
default=kde
org.freedesktop.impl.portal.Settings=kde;gtk;
org.freedesktop.impl.portal.Secret=kwallet
```
1 Like
guss77
December 13, 2024, 7:16am
22
What happens with people that already have 1.19 installed? Will they be kept on the broken version until upstream issues a fixed 1.19?
claydoh
December 13, 2024, 9:46am
23
The pins @carlosd mentions will iirc cause it to downgrade the existing package to the previous one.
It looks like the update just came down the pike, and this is what happened.
After the first update which sets the new apt pins, you will need to update again to downgrade xdg-desktop-portal.
guss77
December 22, 2024, 7:28pm
24
The problem seems to have been fixed in xdg-desktop-portal, and the changes are scheduled for release 1.20 (which is not actually scheduled yet, but hopefully soon).
2 Likes
) I opened a fresh issue here: