Closed jgaovvv closed 3 months ago
@jgaovvv - apologies for not getting back to you sooner. I thought I'd replied to this, but it seems I'd failed to do so.
Upon further investigations, this is a regression caused by #2032. As part of that fix, we needed to identify the characteristics of the directory containing the FUSE mount point. It seems when I added the code to do this, I added it in the wrong place. So everything's fine if the mount point is just one level down from an existing directory, but if it's two or more levels down the directories aren't detected.
Workaround; define your user-specific mount points to be one level below an existing directory.
xrdp version
0.9.25
Detailed xrdp version, build options
Operating system & version
Red Hat Enterprise Linux release 9.3 (Plow)
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
tigervnc-server-minimal-1.13.1-2.el9.x86_64
What desktop environment do you use?
GNOME 40 (x11)
Environment xrdp running on
Physical PC with a Nvidia card
What's your client?
RDP client on Windows 11
Area(s) with issue?
File transfer / drive redirection
Steps to reproduce
On a RHEL 9.3 system, install xrdp from EPEL repo.
In /etc/xrdp/sesman.ini, set:
Then created the directory:
✔️ Expected Behavior
Selected Windows local drives should mount under the /media/thinclient_drives/%u/thinclient_drives/
❌ Actual Behavior
No directories created under the /media/thinclient_drives after the RDP session connected. Copy-paste works fine.
Also I see the xrdp-chansrv.10.log:
Anything else?
No response