[ISSUE] GTK Flatpak Apps no longer apply themes after update ?

[ISSUE] GTK Flatpak Apps no longer apply themes after update ?

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

New issue by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/46311

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.5_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFF

### Package(s) Affected

flatpak-1.15.4_2 flatpak-kcm-5.27.8_1 xdg-desktop-portal-gtk-1.14.1_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Given we grand read access to `~/.themes` and `~/.icons`, and that we enable a specific env var, the selected theme in the env var should be applied (it was up until recently).

### Actual behaviour

Recently, it stopped working, out of the blue, without any reasons. 

I believe it started happening since flatpak-kcm update, but i might be wrong.
QT apps do work as intended tho, so perhaps it is linked to the xdg gtk portal too?

### Steps to reproduce

1. sudo xbps-install -Su
2. Update flatpak-kcm
3. Theme no longer works on gtk apps :(

Re: GTK Flatpak Apps no longer apply themes after update ?

[mayhair]

[-- Attachment #1: Type: text/plain, Size: 239 bytes --]

New comment by mayhair on void-packages repository

https://github.com/void-linux/void-packages/issues/46311#issuecomment-1742522331

Comment:
See https://github.com/void-linux/void-packages/issues/46317#issuecomment-1742516097 for a fix.

Re: GTK Flatpak Apps no longer apply themes after update ?

[mayhair]

[-- Attachment #1: Type: text/plain, Size: 246 bytes --]

New comment by mayhair on void-packages repository

https://github.com/void-linux/void-packages/issues/46311#issuecomment-1742522331

Comment:
See https://github.com/void-linux/void-packages/issues/46317#issuecomment-1742516097 for a workaround.

Re: [ISSUE] [CLOSED] GTK Flatpak Apps no longer apply themes after update ?

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

Closed issue by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/46311

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.5_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFF

### Package(s) Affected

flatpak-1.15.4_2 flatpak-kcm-5.27.8_1 xdg-desktop-portal-gtk-1.14.1_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Given we grand read access to `~/.themes` and `~/.icons`, and that we enable a specific env var, the selected theme in the env var should be applied (it was up until recently).

### Actual behaviour

Recently, it stopped working, out of the blue, without any reasons. 

I believe it started happening since flatpak-kcm update, but i might be wrong.
QT apps do work as intended tho, so perhaps it is linked to the xdg gtk portal too?

### Steps to reproduce

1. sudo xbps-install -Su
2. Update flatpak-kcm
3. Theme no longer works on gtk apps :(

Re: GTK Flatpak Apps no longer apply themes after update ?

[SpidFightFR]

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/46311#issuecomment-1743761632

Comment:
Thank you, @mayhair ! :pray: 

Indeed this solved the issue for me.
If that can help someone, here is my config for Plasma: (this should be located in `~/.config/xdg-desktop-portal/` - for newcomers, to avoid more searching)

<details><summary>kde-portals.conf</summary>

```
[preferred]
# use xdg-desktop-portal-gtk for every portal interface
default=gtk
# except for the xdg-desktop-portal-wlr supplied interfaces
org.freedesktop.impl.portal.Screencast=kde
org.freedesktop.impl.portal.Screenshot=kde
#uses KDE file dialog instead of the gtk file dialog
org.freedesktop.impl.portal.FileChooser=kde
```

</details>

On a sidenote, this would be much appreciated from the xdg desktop portals team to let us *truly* know when such a major change comes up instead of doing it the shady way. :stuck_out_tongue_winking_eye: