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

Bug#996418: marked as done (xrdp-sesman: fails to initialise environment properly)

Your message dated Thu, 28 Oct 2021 17:03:42 +0000
with message-id <E1mg8oY-00043l-Dl@fasolo.debian.org>
and subject line Bug#996418: fixed in xrdp 0.9.17-2
has caused the Debian Bug report #996418,
regarding xrdp-sesman: fails to initialise environment properly
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.)


-- 
996418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996418
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: dbus-x11
Version: 1.12.20-2
Severity: normal
X-Debbugs-Cc: tg@mirbsd.de

Hi, not sure which package is actually at fault here, but here we go.
Please reassign (and notify the target package maintainers) as needed.

This machine used to be an unstable machine but some time before the
release I switched it to bullseye. The date range in question (February
to March 2021) are when it still was on sid.

I have not yet noticed this because it only affects one command. The
problem is that it picked up the "wrong" version of the command, the
one from /usr/bin instead of the one from /usr/local/bin.

This machine is a regular desktop but also has xrdp+xorgxrdp installed
so I can use it while working remotely. The xrdp sessions log to
~/.xsession-errors which is where I could spot the first possible cause
for this error.

My ~/.xsession-errors contains, with some information snipped for
legibility:

-----cutting here may damage your screen surface-----
⇒ Feb 25  2021, 16:22:09+0100 (CET), 2021-W08-4 (Thu) ⇐
Xsession: X session started for tglase at Thu Feb 25 16:22:09 CET 2021
WARNING: tempfile is deprecated; consider using mktemp instead.
localuser:tglase being added to access control list
localuser:boinc being added to access control list
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
[…]
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
[…]
Xsession: X session started for tglase at Fri Mar 12 19:11:35 CET 2021
WARNING: tempfile is deprecated; consider using mktemp instead.
localuser:tglase being added to access control list
localuser:boinc being added to access control list
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
[…]
dbus-update-activation-environment: setting PATH=/sbin:/bin:/usr/bin:/usr/local/bin
[…]
-----cutting here may damage your screen surface-----

From the top, these are:

- one line from my ~/.profile
- 5 + 1 lines from the session start
- 6 + 1 lines from the start of the next session

The lower session is definitely xrdp+xorgxrdp, as one of the xset
calls from ~/.xsessionrc failed. The first call may very well be
from kdm. These are the two oldest entries in that file.

There are *three* different PATH values set, apparently:

tglase@tglase:~ $ fgrep 'setting PATH=' .xsession-errors | sort | uniq -c
      1 dbus-update-activation-environment: setting PATH=/home/tglase/.etc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
     27 dbus-update-activation-environment: setting PATH=/sbin:/bin:/usr/bin:/usr/local/bin
      1 dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

The middle one is the one causing me trouble.

The first and the last one are okay and differ only by the first one
having one entry prepended, which my shell startup file (not .profile
but the actual interactive(!) shell startup file) sets. This was one
session in June I have no idea how I started it, looks like Xorg, not
xrdp+xorgxrdp though. (Normally, when starting services (such as a
login manager) I use a wrapper script around /etc/init.d/* that clears
all environment variables.)

So the questions are, (a) where does this bad environment variable
come from, and (b) why is it also set in my user X session, when
dbus-update-activation-environment runs as a separate thing, although
in the X session start process?

I would have expected a user X11 session to use this:
/etc/environment:PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"

Instead we're getting a PATH set that nowhere even is configured:

$ sudo fgrep -r /sbin:/bin:/usr/bin:/usr/local/bin /etc
/etc/init.d/edac:PATH=/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/local/bin

Specifically, the presence of /sbin without /usr/sbin in the "bad"
PATH causes questions; as far as I know, this is not used anywhere
in Debian like that: either you get both sbins (admin account) or
(almost everywhere) neither, but not just one of them.

-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages dbus-x11 depends on:
ii  dbus         1.12.20-2
ii  libc6        2.31-13+deb11u2
ii  libdbus-1-3  1.12.20-2
ii  libx11-6     2:1.7.2-1

dbus-x11 recommends no packages.

dbus-x11 suggests no packages.

-- no debconf information

--- 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 996418@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: