Control: tag -1 + moreinfo Hi,
> I have installed xrdp 0.9.0~20160601+git703fedd-3~bpo8+1 on a Jessie > machine. For all users who started an xrdp session there is a new > file named > > .thinclient_drives > > This file is not accessible at all: > > # file .thinclient_drives > .thinclient_drives: sticky, directory > # cd .thinclient_drives > bash: cd: .thinclient_drives: No such file or directory > # ls -la .thinclient_drives > ls: cannot access .thinclient_drives: Permission denied > > In MidnightCommander it is displayer in red with a leading '?' > dated 01.01.1990 is owned by root and has all permissions unset > (like `chmod 000 .thinclient_drives`) > > As root I can remove this dir using > > rm -rf .thinclient_drives > > but that's the only option I've found to deal with this. This is correct and has nothing to do with xrdp (itself). The directory is managed by FUSE to hold the drives mapped from the RDP client. What you see is the expected behaviour for all FUSE-managed mount points (try sshfs, for example). Not even root can access FUSE mountpoints of other users - that is annoying, but has nothing to do with xrdp. > The problem that occures from this is that when starting > Thunar it claims that it can't open this dir (which is > correct) and seems to stop gvfs scanning from then on and > users can not see their network mounts. Normally, the user who mounted the FUSE directory should be able to acces it like normal. I guess gvfsd in jessie is running as root and doing nasty magic through policykit or something? > $ grep -R thinclient_drives > debian/patches/fusepath.diff:- /* define FUSE mount point to > ~/xrdp_client, ~/thinclient_drives */ > debian/patches/fusepath.diff:+ /* define FUSE mount point to > ~/.xrdp_client, ~/.thinclient_drives */ > debian/patches/fusepath.diff:-FuseMountName=thinclient_drives > debian/patches/fusepath.diff:+FuseMountName=.thinclient_drives > sesman/sesman.ini:FuseMountName=thinclient_drives > sesman/chansrv/chansrv_fuse.c: /* define FUSE mount point to > ~/xrdp_client, ~/thinclient_drives */ > > so it is definitely xrdp that's causing this strange dir. xrdp creates it as a FUSE mountpoint. but the consequences you see definitely look like a combination of the bad behaviours oF FUSE and gvfs in jessie (or in general?). I expect this to also happen with an sshfs mount. Could you try that? If you still think this is specific to xrdp, please explain why. If not, this should be discussed with the gvfs maintainers. Cheers, Nik -- * mirabilos is handling my post-1990 smartphone * <mirabilos> Aaah, it vibrates! Wherefore art thou, demonic device?? PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
