I’m using flatpak for some applications, and have configured the xdg portal - I’m using the gtk portal. While I’m not using gnome, to my knowledge this should still work.
Whenever I open a link in a flatpak application, it instead prompts me to install an application via gnome software. According to
xdg-settings get default-web-browser
this should open with firefox.desktop.
What am I doing wrong? Is this an upstream bug? Should I be using gconf to configure the default browser? Is this a bug in our implementation of the portal configuration?
I have the same problem
I have gnome and LXQt installed, when I log into gnome, everything works
but when using LXQt and xdg-desktop-portal-kde I get the same error
A problem is definitively that the gnome portal is running
and it seems it is the one that is being used
systemctl --user status xdg-desktop-portal-gnome.service
● xdg-desktop-portal-gnome.service - Portal service (GNOME implementation)
Loaded: loaded (/etc/systemd/user/xdg-desktop-portal-gnome.service; static)
Active: active (running) since Tue 2022-11-08 08:51:44 CET; 12min ago
Main PID: 133224 (.xdg-desktop-po)
Tasks: 9 (limit: 38414)
Memory: 26.4M
CPU: 220ms
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/xdg-desktop-portal-gnome.service
└─133224 /nix/store/bhavkr6x64i9dxi7z1ka2n86m6hisma6-xdg-desktop-portal-gnome-43.1/libexec/xdg-desktop-portal-gnome
Nov 08 08:51:44 desktop systemd[1749]: Starting Portal service (GNOME implementation)...
Nov 08 08:51:44 desktop systemd[1749]: Started Portal service (GNOME implementation).
Nov 08 08:51:44 desktop .xdg-desktop-po[133224]: Unhandled parent window type
Nov 08 08:51:44 desktop .xdg-desktop-po[133224]: Failed to associate portal window with parent window
Yes, I was suggesting that as a potential reason for why all applications are suddenly using the portal when they shouldn’t, I misunderstood that as “I’d like lxqt to stop using the portal for its file chooser”.
In retrospect, obviously lxqt is a desktop and not an application, it was probably late ;p
However, opening firefox via systemd-run fails without errors:
tlater ~ $ systemd-run --user -P gio open https://tlater.net
Running as unit: run-u78.service
# Nothing happens, return controls to shell
Curiously, I had a chromium installed with flatpak previously (to use MS teams, which now supports firefox). I did manage to open a link in it, which previously did not work. Just still not in my host’s firefox - possibly related to it being installed with home-manager?
Yep, that seems to be it, installed Firefox with environment.systemPackages and it just works now. Any idea why my home-manager profile is not playing ball? I have no idea how to further debug this.
I suppose this would be something to raise on that upstream if not.
On the day I said I’ve fixed it
I only ran systemctl --user import-environment PATH and systemctl --user restart xdg-desktop-portal-gnome.service xdg-desktop-portal.service
and added this config (and thought with this, all is fixed)