Non-flatpak sandboxed (firejail) applications cannot access portals

[WhyNotHugo]

trafficstars

Non-Flatpak applications cannot access the settings portal. E.g.: Running d-feet with Firejail results in this error:

However, in this scenario d-feet is sandboxed but is granted full read-write access to all D-Bus endpoints. It seems that the issue it that the portal itself is assuming that any sandboxed application is a Flatpak application, and ends up calling parse_app_info_from_flatpak_info, which fails in this case since /proc/%u/root is inaccessible to the current user.

[TingPing]

It seems that the issue it that the portal itself is assuming that any sandboxed application is a Flatpak application

The portal checks the processes filesystem to see if its a Flatpak. I'd assume handling this specific failure as unsandboxed wouldn't be a security issue but I'm not sure.

[WhyNotHugo]

See #741