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

Bug#984782: marked as done (xrdp session is not using the same PATH as a console session)

Your message dated Thu, 28 Oct 2021 17:03:42 +0000
with message-id <E1mg8oY-00043g-Cv@fasolo.debian.org>
and subject line Bug#984782: fixed in xrdp 0.9.17-2
has caused the Debian Bug report #984782,
regarding xrdp session is not using the same PATH as a console session
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.)


-- 
984782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984782
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xrdp
Severity: normal
Tags: patch

xrdp project member here.

While working on an xrdp issue
(https://github.com/neutrinolabs/xrdp/issues/1773) we ascertained that
the PATH elements /bin and /usr/bin were swapped between a console
session and an xrdp session.

This is on a Kubuntu system.

The consequence of this was that the timeshift-gtk executable was being
found in /bin on the xrdp session. Consequently, polkit was unable to
find the correct action to apply, and the invocation failed. When run
explicitly from /usr/bin, the invocation succeeded.

Further investigation showed that on Ubuntu flavours, pan_env.so is
being used to set the PATH (and indeed the locale). Unlike the Buster
system I've got here, the PATH isn't set explicitly in /etc/profile.

For xrdp issue #1773, we resolved user's immediate problem by applying
this patch to /etc/xrdp/startwm.sh:-

--- startwm.sh.orig 2021-01-13 13:02:36.017117908 +0000
+++ startwm.sh 2021-01-12 13:50:10.396884171 +0000
@@ -2,6 +2,11 @@
 # xrdp X session start script (c) 2015, 2017 mirabilos
 # published under The MirOS Licence

+# Emulate pam_env.so
+if test -r /etc/environment; then
+ . /etc/environment
+fi
+
 if test -r /etc/profile; then
  . /etc/profile
 fi

Note that this file is an upstream file to the xrdp project.

This bug is a request to either adopt the patch above, or include
the corresponding pam_env calls in /etc/pam.d/xrdp-sesman. An
advantage of the second is that I believe you would be able to
remove the locale stuff from /etc/xrdp/startwm.sh, but I haven't
tested this.

I originally reported this fault on 2021-01-13 as
https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1911435, but now
realise that this wasn't at all helpful.

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (100, 'focal-backports') 
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-44-generic (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) 
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xrdp depends on:
ii  adduser              3.118ubuntu2
ii  init-system-helpers  1.57
ii  libc6                2.31-0ubuntu9.2
ii  libfuse2             2.9.9-3
ii  libjpeg8             8c-2ubuntu8
ii  libopus0             1.3.1-0ubuntu1
ii  libpam0g             1.3.1-5ubuntu4.1
ii  libssl1.1            1.1.1f-1ubuntu2.2
ii  libx11-6             2:1.6.9-2ubuntu1.1
ii  libxfixes3           1:5.0.3-2
ii  libxrandr2           2:1.5.2-0ubuntu1
ii  lsb-base             11.1.0ubuntu2
ii  ssl-cert             1.0.39

Versions of packages xrdp recommends:
ii  fuse      2.9.9-3
pn  xorgxrdp  <none>

Versions of packages xrdp suggests:
pn  guacamole                  <none>
pn  xrdp-pulseaudio-installer  <none>

--- End Message ---
--- Begin Message --- 
Source: xrdp
Source-Version: 0.9.17-2
Done: Thorsten Glaser <tg@mirbsd.de>

We believe that the bug you reported is fixed in the latest version of
xrdp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 984782@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Glaser <tg@mirbsd.de> (supplier of updated xrdp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Format: 1.8
Date: Thu, 28 Oct 2021 18:37:04 +0200
Source: xrdp
Architecture: source
Version: 0.9.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers <debian-remote@lists.debian.org>
Changed-By: Thorsten Glaser <tg@mirbsd.de>
Closes: 984782 996418
Changes:
 xrdp (0.9.17-2) unstable; urgency=medium
 .
   * Initialise the environment properly (Closes: #996418, #984782)
     (LP#1911435)
Checksums-Sha1:
 76580c2d4402680f6cb57dbf75d3ab1546e5f51f 2295 xrdp_0.9.17-2.dsc
 b2b95dbdd71a160c573ddc58cf0c1a39c11abb5e 22728 xrdp_0.9.17-2.debian.tar.xz
Checksums-Sha256:
 f8acfa3b40abeb63339eadabd30a1e5f20ca33af0e78f7605cfe9f4950170d18 2295 xrdp_0.9.17-2.dsc
 418417097a5d16ea0f83522f2e6c2cad07d48e18c67cf1859aa26a5d5c4b3983 22728 xrdp_0.9.17-2.debian.tar.xz
Files:
 32c634de86c1d035e8be21097187aebb 2295 net optional xrdp_0.9.17-2.dsc
 460c3baac4ee32596271842cd3335701 22728 net optional xrdp_0.9.17-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８　☕☂☄

iQIcBAEBCQAGBQJhetKmAAoJEHa1NLLpkAfgO3EP/04m6xL3JEEBgAp8U5Lte8tP
JyI91g5pqZ0OmGX6CfKJlnpDar3cbxW/VKSHSHolmW2cRkAL1F4fO+Q7/cRXEMWt
IgZo/g7i4WzK1TuIemj9Nt/MiPoSpshROk7iZKILvQyjZ0vqe9YRivnMCGi+NYgY
HMYqKZ2b/WcBghh0myieZwaAVA/bwO6m19p+iBL3KIwa6WCvcCuuy6hld2iKJtmR
Jb8HLJlgdlXlCiKdDXV4erWooDKTgVXBlkzN+UO4iEbK8zxR4zyncWWIIsPUjf6G
Pf+lQDm14+0dvBG/Bs8ItA9TafKKkBSLtk+PW1Of8S7A2SvXIsg8pafxXe/DeZVv
wUMD/SWk7xQCweDfMQWz86NvdFYEyk7u1r+cr+jIZvH8gxdgMo9zd4V8JswPOZIL
8QYioltSDWTWkcAti8N0EI9Fh57EDBwQPHCU5MNObUcdpAr2bgagkrg9vjpqtGlb
9wPQFNxJTq7YjnC2y2XJeoG/G3BP8ihf5Eh7iN666Em+MBdkfHypYka9kUXi+PR7
9BIdZEsGscD50Rb3RiNbHpMvQvklSODCA0tCa1efJ2oBz8K+ZhYeOTrXBSwOx7fJ
dW8gBNVrP+FRyKOG0Mkl5e3g1JbwEzdMtL5Jv7U6NrGt9+6s6i8wZC2bJr2V3JPN
XLnsrh/569dqf9pV0ZQ7
=bHgV
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: