Linux: SLADE cannot 'see' some root owned FSOs to which user has read access

[MartinHowe426]

SLADE Version

3.2.5

OS

Linux

Editor

Resource editor

Steps to Reproduce and Observed Behavior

1. Go to 'Edit|Set Base Resource Archive' then click 'Add Archive'
2. Browse to a directory containing doom2.wad -> /usr/share/doom2/doom2.wad
3. SLADE correctly identifies the file as a symlink in the directory listing
4. Click the file
5. SLADE replies 'Please choose an existing file'
6. Try to browse to the original file
7. SLADE's file browser cannot 'see' /usr/share/doom2
8. Additionally, using CTRL-L to edit the path as text fails
9. /usr/share/doom2 -> /usr/share/games/doom2/1.9 is itself a symbolic link
10. But SLADE cannot even 'see' /usr/share/games and that is an actual directory and not a link
11. So that doesn't work either :(

Expected Behavior

1. The file should be selected and added to the archive list.
2. File browser should be able to 'see' root-owned files and folders for which the user has read access.
3. Specifying the full path to root-owned files and folders for which the user has read access should work.

Screenshots

[cyber199]

Possibly related, but SLADE cannot see /usr/games at all on my system (which is where I have GZDoom installed). using the PPA from DRD Team fixes this, so the problem may be with Flatpak permissions not allowing SLADE to see "unsafe" directories such as where other binaries are commonly installed.