Re: Troubleshooting issues with xdg-desktop-portal and flatpak on XFCE
Reply #3 –
Thanks for the replies.
I wanted to run Discord through flatpak since it sandboxes the application. Since Discord is proprietary, I think this is a good idea. I might be ignorant but I am not sure if AppImage also runs in a sandbox. This may also be the cause of these issues though. That said, I was running on a KDE desktop environment on Artix recently and the filechooser worked through Discord running through a flatpak there, so I know it is possible.
I still find it interesting why I am having this issue and would like to try and nail down a cause, especially if my system is misconfigured in any way. I feel like that could cause issues down the line for not just flatpaks.
As for the output of `pgrep -a 'xdg|dbus'`:
796 /usr/bin/dbus-daemon --system --nofork --nopidfile --print-address=4
1016 dbus-launch --autolaunch adbb587324d2d03a45a47d3865224490 --binary-syntax --close-stderr
1017 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
1065 /usr/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session
1066 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
1101 /bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus_0
1413 /usr/lib/xdg-desktop-portal
1419 /usr/lib/xdg-document-portal
1424 /usr/lib/xdg-permission-store
1436 /usr/lib/xdg-desktop-portal-xapp
8592 xdg-dbus-proxy --args=42
I am a bit ignorant as to what I am looking at here, but nothing seems out of the ordinary to my eye.