[Bug]: Executable won't start through "Run Executable" with custom Z: device, but will through explorer

[jnvsor]

Describe the bug

When Z: is a portal executables in Z: won't start through "Run Executable". They fail silently, so I check "Run in terminal" to see the error:

wine: could not open working directory L"unix\\run\\flatpak\\doc\\290691a8\\", starting in the Windows directory.
Application could not be started, or no application associated with the specifi
ed file.
ShellExecuteEx failed: File not found.

Starting explorer and navigating to Z: allows me to start the executable as expected (As will starting CMD and running it from there)

To Reproduce

• Create a gaming environment bottle
• Set the Z: drive to a different folder
• Try to run an executable inside the Z: drive

Package

Flatpak from Flathub

Distribution

Debian Sid

Debugging Information

Official Package: true
Version: '51.11'
DE/WM: lightdm-xsession
Display:
    X.org: true
    X.org (port): :0.0
    Wayland: false
Graphics:
    vendors:
        amd:
            vendor: amd
            envs:
                DRI_PRIME: '1'
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/radeon_icd.x86_64.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/radeon_icd.i686.json
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.7.12-amd64
Disk:
    Total: 33577865216
    Free: 33577701376
RAM:
    MemTotal: 62.5GiB
    MemAvailable: 55.8GiB
Bottles_envs: null

Troubleshooting Logs

14:56:58 (INFO) Launching an executable… 
14:56:58 (INFO) Using EasyAntiCheat runtime 
14:56:58 (INFO) Using BattlEye runtime 
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
14:57:16 (INFO) Drive z: path changed to /run/user/1000/doc/f4c4c66d/folder
14:57:31 (INFO) Launching an executable… 
14:57:31 (INFO) Using EasyAntiCheat runtime 
14:57:31 (INFO) Using BattlEye runtime 
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
wine: could not open working directory L"unix\\run\\flatpak\\doc\\53b256e2\\", starting in the Windows directory.
14:57:31 (WARNING) ShellExecuteEx exception seems occurred. 
14:57:43 (INFO) Drive z: path changed to / 
14:57:47 (INFO) Launching an executable… 
14:57:47 (INFO) Using EasyAntiCheat runtime 
14:57:47 (INFO) Using BattlEye runtime 
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely

Additional context

When setting a custom folder for Z: (Anything other than /) a folder is created under /run/user/$UID/doc/ -- So far so good, looks like a portal. When trying to run an executable in that folder a second folder is created under /run/user/$UID/doc/ containing only the executable (no sibling files) and the executable fails to run trying to run from that path.

Starting explorer and running the executable from there does work, but the entire Z: drive disappears if I have per-bottle sandboxing enabled, which may be related since this behavior also only occurs when Z: is mapped to something other than /.

Since / seems to be the only path that's accessed directly rather than through /run/user/$UID/doc/ I presume this has something to do with portals, but I don't know enough about portals to tell.

Last week this was working fine, but I haven't done any system updates in that time (Nor do I know enough about flatpak to screw with portal settings) so I don't know how it broke. The bug survives a reboot so it's not a temporary state issue