[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#831873: marked as done (xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root)

Your message dated Thu, 27 Oct 2016 23:35:28 +0200
with message-id <20161027213528.vg75no4wbvvwjfnj@portux.lan.naturalnet.de>
and subject line Not reproducible
has caused the Debian Bug report #831873,
regarding xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
831873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831873
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xrdp
Severity: important

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.

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.

When browsing the packaging git of xrdp I see:

$ 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.

Kind regards

        Andreas.


-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xrdp depends on:
ii  adduser      3.113+nmu3
ii  libc6        2.19-18+deb8u4
ii  libpam0g     1.1.8-3.1+deb8u1+b1
ii  libssl1.0.0  1.0.1t-1+deb8u2
ii  libx11-6     2:1.6.2-3
ii  libxfixes3   1:5.0.1-2+b2

Versions of packages xrdp recommends:
pn  vnc4server | tightvncserver | vnc-server  <none>

xrdp suggests no packages.

--- End Message ---
--- Begin Message --- 
Control: tag -1 =

As the bug is not reproducible and, if at all, a bug in gvfs, I am closing
this bug report after a few weeks of no feedback.

Cheers,
Nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Contributor

LPIC-3 Linux Enterprise Professional (Security)

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: