Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

Ben Armstrong synergism at gmail.com
Mon Jan 2 20:02:05 UTC 2017

On Sun, Jan 1, 2017 at 1:05 PM, Dominik George <nik at naturalnet.de> wrote:

> > I had originally similar thoughts, but after many unsuccessful attempts
> > to get the actual Xorg failure logged somewhere, I eventually gave up
> > (e.g. param lines in sesman.ini to pass -logfile and its argument). If
> > you could help me find a solution to that, I could try to get it to
> > give me an error message ...
> What happens if you add -logfile xorg.log to params (and restart
> sesman)?

sesman.ini excerpt:


after sesman is restarted and I attempted to connect (and failed):

synrg at lear:~$ ls -l .local/share/xorg/Xorg.xrdp.log
ls: cannot access '.local/share/xorg/Xorg.xrdp.log': No such file or

Here's the error output from journalctl:

Jan 02 15:56:47 lear xrdp-sesman[15215]: (15215)(-148404480)[INFO ] Xorg
:10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
-logfile .local/share/xorg/Xorg.xrdp.log
Jan 02 15:56:57 lear xrdp-sesman[15213]: (15213)(-148404480)[ERROR] X
server for display 10 startup timeout
Jan 02 15:56:57 lear xrdp-sesman[15213]: (15213)(-148404480)[INFO ]
starting xrdp-sessvc - xpid=15215 - wmpid=15214
Jan 02 15:56:57 lear xrdp-sesman[15214]: (15214)(-148404480)[ERROR] X
server for display 10 startup timeout
Jan 02 15:56:57 lear xrdp-sesman[15214]: pam_unix(gdm:session): session
opened for user synrg by (uid=0)
Jan 02 15:56:57 lear xrdp-sesman[15211]: (15211)(-148404480)[INFO ] ++
terminated session:  username synrg, display :10.0, session_pid 15213, ip - socket: 12

The very same [Xorg] session as above successfully creates
.local/share/xorg/Xorg.xrdp.log when run with the older xrdp I cited before.

> It should then create the log file either in ~/.local/shared/xorg.log or
> ~/xorg.log or /var/log/xorg.log.
> If it doesn't, I'm somewhat surprised…

So am I. Frustrating. It must find something about the parameters passed
objectionable and therefore fails to even start the Xorg instance, let
alone log its output. I'd love to see stderr from the command, but I don't
know how to do that. I think I'd have to replace param=Xorg with a wrapper
script that did the logging ... Maybe I'll try this next.

> Some random questions:
>  * Is your Xorg binary suid root?


synrg at lear:~$ ls -la /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Dec 16 14:39 /usr/bin/Xorg

>  * Do you have policykit?


synrg at lear:~$ ps auxw |grep -i polkit
root       592  0.0  0.1  39488  4840 ?        Ssl   2016   0:03
/usr/lib/policykit-1/polkitd --no-debug

>  * What's in /etc/X11/Xwrapper.config ?

synrg at lear:~$ sudo cat /etc/X11/Xwrapper.config
# Xwrapper.config (Debian X Window System server wrapper configuration file)
# This file was generated by the post-installation script of the x11-common
# package using values from the debconf database.
# See the Xwrapper.config(5) manual page for more information.
# This file is automatically updated on upgrades of the x11-common package
# *only* if it has not been modified since the last upgrade of that package.
# If you have edited this file but would like it to be automatically updated
# again, run the following command as root:
#   dpkg-reconfigure x11-common

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-remote-team/attachments/20170102/4ac5254d/attachment.html>

More information about the pkg-remote-team mailing list