Created attachment 825065 [details] Log of flatpak run --verbose re.sonny.Tangram Hello, I've experienced that multiple Flatpak apps won't start if one clicks on their .desktop shortcuts. They run when using flatpak run org.gnome.example but I get this error: GLib-GIO-WARNING **: 09:21:29.880: Can't find module 'dconf' specified in GSETTINGS_BACKEND I've attached an example log when running re.sonny.Tangram. But other apps output similar errors. Regards, Konstantin Tutsch
Can you try installing the gnome-base/dconf package to see if that help?
I had already checked if it is installed. It is. I also reemerged it. Nothing changed.
To clarify, it's reporting that the flakpak you're running is missing the dconf module. I don't know if that's to be expected (ref: https://blogs.gnome.org/mclasen/2019/07/12/settings-in-a-sandbox-world/); but the workaround suggested does get rid of the message. I used Flatseal to add GSETTINGS_BACKEND=keyfile gobally.
I am experiencing this exact problem, but I am not sure the bug report title is actually connected to the problem of not being able to launch Flatpak apps by using their icon (.desktop file). This is an issue with dbus and/or Flatpak, and it specifically affects Flatpak apps with DbusActivatable=true in their .desktop files. As best I can tell, it seems like the session bus is not finding the .service files that Flatpak creates. The .service files are under ~/.local/share/flatpak/app, and their presence should be found via XDG_DATA_DIRS by dbus. But this does not happen. From what I can tell, everything is configured correctly. Don't know too much about dbus unfortunately. One "workaround" for this situation is to copy the Flatpak service files to ~/.local/share/dbus-1/service: cp -L ~/.local/share/flatpak/exports/share/dbus-1/services/*.service ~/.local/share/dbus-1/services/ This should allow the Flatpak apps to launch via .desktop files. Not sure what other effects it could have though. I'm thinking this is more of a problem with dbus than Flatpak, but I am not sure.
gnome-base/dconf sets GSETTINGS_BACKEND=dconf globally through /etc/env.d/51dconf but it's not ideal for applications like Flatpak that run as a sandbox. I also saw this message when running steam so I created /usr/local/bin/steam as a wrapper that sets GSETTINGS_BACKEND=keyfile. Since Gentoo sets GSETTINGS_BACKEND=dconf explicitly, sys-apps/flatpak should also create a wrapper that sets GSETTINGS_BACKEND=keyfile, unless it already does so, or unless Flatpak already does it somewhere internally.
In my case, I can run flatpak apps but still see this message... (I use OpenRC, to be clear; I see mentions of .service files in other comments) Setting GSETTINGS_BACKEND=keyfile in flatseal removes the warning, nut then instead throws the following message for some reason: ``` LaunchProcess: failed to execvp: xdg-settings ```
(In reply to Neko-san from comment #6) > Setting GSETTINGS_BACKEND=keyfile in flatseal removes the warning, nut then > instead throws the following message for some reason: > ``` > LaunchProcess: failed to execvp: > xdg-settings That might be unrelated. Google the error.
I did; the only information I've been able to come across on it are implications that xdg-settings isn't installed (it is), a portal isn't installed (there is), or that (supposedly) "flatpak --user" wasn't specifically used (which I would find odd because I don't see how that should prevent it from accessing xdg-settings (Admittedly though, this does seem separate to me too on the surface as far as I can tell)
(In reply to Neko-san from comment #8) > (Admittedly though, this does seem separate to me too on the surface as far > as I can tell) Consider creating a new bug post or ask a question about it in the forums.
(In reply to knifed from comment #4) > I am experiencing this exact problem, but I am not sure the bug report title > is actually connected to the problem of not being able to launch Flatpak > apps by using their icon (.desktop file). > > This is an issue with dbus and/or Flatpak, and it specifically affects > Flatpak apps with DbusActivatable=true in their .desktop files. As best I > can tell, it seems like the session bus is not finding the .service files > that Flatpak creates. The .service files are under > ~/.local/share/flatpak/app, and their presence should be found via > XDG_DATA_DIRS by dbus. But this does not happen. > > From what I can tell, everything is configured correctly. Don't know too > much about dbus unfortunately. > > One "workaround" for this situation is to copy the Flatpak service files to > ~/.local/share/dbus-1/service: > > cp -L ~/.local/share/flatpak/exports/share/dbus-1/services/*.service > ~/.local/share/dbus-1/services/ > > This should allow the Flatpak apps to launch via .desktop files. Not sure > what other effects it could have though. > > I'm thinking this is more of a problem with dbus than Flatpak, but I am not > sure. Exact same issue with my flatpaks too but only some of them (fractal and loupe, both are rust programs but papers with is half c half rust is fine).
