FreeRDP Flatpak Fails RDP Connection Test Due to Missing tsclient\home\.local\share\winapps Directory Mount #868
Unanswered
Frickeldave
asked this question in
Support
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What happened?
Summary
The automated RDP connection test in setup.sh (ECRDPFAIL, exit status 14) fails when using FreeRDP Flatpak (flatpak run com.freerdp.FreeRDP), despite manual xfreerdp connections working perfectly. The root cause is that the test file cannot be created at \tsclient\home.local\share\winapps\FreeRDP_Connection_Test because the tsclient home drive mount doesn't exist or isn't accessible within the Flatpak sandbox.
Environment
OS: Linux Mint 22 (min22/Podman backend)
FreeRDP: Flatpak com.freerdp.FreeRDP (detected by setup.sh as FREERDP_COMMAND="flatpak run --command=xfreerdp com.freerdp.FreeRDP" in winapps.conf)
WinApps: Latest from bash <(curl https://raw.githubusercontent.com/winapps-org/winapps/main/setup.sh)
Backend: Podman Windows container (min22)
RDP: Manual connections work ✓, automated test fails ✗
Error Details
text
Attempting to establish a Remote Desktop connection with Windows... Failed!
ERROR: REMOTE DESKTOP PROTOCOL FAILURE.
Exiting with status '14'.
Log channel (FreeRDP_Test_20260119_0921_852946507.log):
text
[09:21:28:066] [WARN][com.freerdp.crypto] - Certificate verification failure 'self-signed certificate (18)'
/dev/fd/63: line 1661: 79603 Killed $FREERDP_COMMAND ... /app:"C:\Windows\System32\cmd.exe",cmd:"/C type NUL > \tsclient\home.local\share\winapps\FreeRDP_Connection_Test && tsdiscon"
Root Cause (from setup.sh analysis):
bash
readonly TEST_PATH_WIN="${USER_APPDATA_PATH_WIN}\FreeRDP_Connection_Test"
readonly USER_APPDATA_PATH_WIN='\tsclient\home.local\share\winapps'
The +home-drive flag should mount Linux $HOME as tsclient\home, but Flatpak sandbox blocks this directory creation/access when using FREERDP_COMMAND="flatpak run --command=xfreerdp com.freerdp.FreeRDP".
Steps to Reproduce
Add to ~/.config/winapps/winapps.conf: FREERDP_COMMAND="flatpak run --command=xfreerdp com.freerdp.FreeRDP"
Install FreeRDP Flatpak: flatpak install flathub com.freerdp.FreeRDP
Configure valid RDP credentials in winapps.conf
Run bash <(curl https://raw.githubusercontent.com/winapps-org/winapps/main/setup.sh)
Select "Install" → "Current User" → "Manual"
→ Fails at RDP test with status 14
Manual Verification
xfreerdp ... (system-wide) → ✅ Creates tsclient mount, test passes
FREERDP_COMMAND="flatpak run --command=xfreerdp com.freerdp.FreeRDP" → ❌ No tsclient\home.local\share\winapps, cmd.exe killed
Workarounds Tested
flatpak override --filesystem=home com.freerdp.FreeRDP → Partial help, but tsclient mount still unreliable
Manual directory creation in Windows → Directory exists, but RDP session can't access via Flatpak
System FreeRDP3-x11 → ✅ Works perfectly (recommended fix)
Suggested Fix
Detect Flatpak in setup.sh and warn/suggest system freerdp3-x11 installation
Add Flatpak-specific flags: --filesystem=~/.local/share/winapps --filesystem=host
Fallback test path: Use C:\temp\ instead of tsclient for Flatpak compatibility
Enhanced logging: Show FREERDP_COMMAND expansion and tsclient mount status
Setup.sh Context
bash
Line ~1661 - Failing command:
$FREERDP_COMMAND $RDP_FLAGS_NON_WINDOWS /cert:tofu ... +home-drive /app:"C:\Windows\System32\cmd.exe",cmd:"/C type NUL > $TEST_PATH_WIN && tsdiscon" /v:"$RDP_IP"
This is a common Flatpak sandbox limitation affecting WinApps/min22 users who set FREERDP_COMMAND="flatpak run --command=xfreerdp com.freerdp.FreeRDP" in their config. System freerdp3-x11 resolves it completely.
Your FreeRDP version and where you got it from
FreeRDP 3.20.2 Flatpack
Your Linux distribution and version
Min22
Your
winapps.confLogs
Terms
Beta Was this translation helpful? Give feedback.
All reactions