Bug#865653: xrdp: X server timeout
Found a solution: after changing to "allowed_users=anybody" in
/etc/X11/Xwrapper.config , XRDP works as expected. So, the default
value ("console") supplied by xserver-xorg-legacy is not compatible
with XRDP, and needs to be adapted.
Bug#865653: xrdp: X server timeout
Now I upgraded xrdp and xorgxrdp to experimental, and the problem still persists: # dpkg -l | grep xrdp ii xorgxrdp0.9.2~20170325-1~exp1 amd64Remote Desktop Protocol (RDP) modules for X.org ii xrdp0.9.2~20170325-1~exp1 amd64Remote Desktop Protocol (RDP) server
Bug#865653: xrdp: X server timeout
Package: xrdp Version: 0.9.1-9 Severity: grave Justification: renders package unusable Dear Maintainer, xrdp 0.9.1-9 was running fine while the machine was under Debian Testing. After upgrading to Stretch, I cannot start the RDP session any more. The problem is reproduced on a fresh Debian 9.0 machine, by installing xrdp and creating a user. I'm using the Windows 8.1 RDP client. After logging in, the screen is blank blue background for 10 seconds, and then a window with "Connection problem, giving up" appears. The following is the content of /var/log/xrdp-sesman.log: [20170623-13:48:27] [DEBUG] libscp initialized [20170623-13:48:27] [INFO ] starting xrdp-sesman with pid 13780 [20170623-13:48:27] [INFO ] listening to port 3350 on 127.0.0.1 [20170623-13:50:49] [INFO ] A connection received from ::1 port 44638 [20170623-13:50:49] [INFO ] ++ created session (access granted): username ssinyagin, ip 0.0.0.0:62500 - socket: 12 [20170623-13:50:49] [INFO ] starting Xorg session... [20170623-13:50:49] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910) [20170623-13:50:49] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010) [20170623-13:50:49] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210) [20170623-13:50:49] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350) [20170623-13:50:49] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350) [20170623-13:50:49] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp [20170623-13:50:59] [ERROR] X server for display 10 startup timeout [20170623-13:50:59] [INFO ] starting xrdp-sessvc - xpid=16987 - wmpid=16986 [20170623-13:50:59] [ERROR] X server for display 10 startup timeout [20170623-13:50:59] [ERROR] another Xserver might already be active on display 10 - see log [20170623-13:50:59] [DEBUG] aborting connection... [20170623-13:50:59] [INFO ] ++ terminated session: username ssinyagin, display :10.0, session_pid 16985, ip 0.0.0.0:62500 - socket: 12 -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.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.115 ii init-system-helpers 1.48 ii libc62.24-11 ii libfuse2 2.9.7-1 ii libjpeg62-turbo 1:1.5.1-2 ii libopus0 1.2~alpha2-1 ii libpam0g 1.1.8-3.6 ii libssl1.11.1.0f-3 ii libx11-6 2:1.6.4-3 ii libxfixes3 1:5.0.3-1 ii libxrandr2 2:1.5.1-1 ii lsb-base 9.20161125 ii ssl-cert 1.0.39 Versions of packages xrdp recommends: ii fuse 2.9.7-1 ii xorgxrdp 0.9.1-9 Versions of packages xrdp suggests: pn guacamole Versions of packages xorgxrdp depends on: ii libc6 2.24-11 pn xorg-input-abi-24 ii xserver-xorg-core [xorg-video-abi-23] 2:1.19.2-1 Versions of packages xorgxrdp recommends: ii xorg 1:7.7+19 Versions of packages xrdp is related to: pn vnc-server ii xserver-xorg-legacy 2:1.19.2-1 -- no debconf information
Bug#571139: torrus-apache2 must not depend on apache2-mpm-worker --- causing crashes
hi Christoph,
On Fri, Mar 5, 2010 at 9:32 AM, Christoph Berg m...@debian.org wrote:
--- trunk/debian/control 2010-03-05 08:11:05 UTC (rev 131)
+++ trunk/debian/control 2010-03-05 08:13:39 UTC (rev 132)
-Depends: torrus-common (= ${source:Version}), apache2-mpm-worker | apache2,
libapache2-mod-perl2 (= 2.0.0), libapache2-request-perl (= 2.05-dev-6)
+Depends: torrus-common (= ${source:Version}), apache2-mpm-prefork |
apache2, libapache2-mod-perl2 (= 2.0.0), libapache2-request-perl (=
2.05-dev-6)
+Conflicts: apache2-mpm-worker
is that the right fix? There are two other MPMs, namely
apache2-mpm-event and apache2-mpm-itk in Debian. If Torrus is only
incompatible with -worker, I agree, but what about the others?
according to the MPM documentation, mpm-itk should work fine, but
mpm-event will most probably conflict in the same way as worker.
I would set it to conflict with mpm-event as well, until someone tests it.
I'm also thinking of implementing a new application handler, probably
it will be lighttpd+fastcgi.
thanks,
stan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571139: torrus-apache2 must not depend on apache2-mpm-worker --- causing crashes
not only thinks so, but also tested :) On Fri, Mar 5, 2010 at 8:23 AM, Marc Haber mh+debian-packa...@zugschlus.de wrote: severity #571139 serious thanks justification: maintainer thinks so -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571139: torrus-apache2 must not depend on apache2-mpm-worker --- causing crashes
Package: torrus-apache2 Version: 1.0.8-1 Hi, here's the upstream software maintainer. Torrus is incompatible with apache2-mpm-worker: Multithreading in Apache causes Torrus database corruption. The package must depend on apache2-mpm-prefork The fix has been tested, and the system runs stable since two weeks. cheers, -- Stanislav Sinyagin Senior Consulting Engineer CCIE #5478 ssinya...@k-open.com +41 79 407 0224 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
