Same problem here, but even if the init.d script is modified to clear the pid files, the server doesn't start properly on its own. After clearing sesman.log, after a reboot, the contents of sesman.log are [20090530-00:59:49] [INFO ] starting signal handling thread... [20090530-00:59:49] [INFO ] signal handler thread started successfully [20090530-00:59:49] [CORE ] starting sesman with pid 2353 [20090530-00:59:49] [INFO ] listening...
Also, the relevant processes are $ ps -A | grep sesman 2353 ? 00:00:00 sesman $ ps -A | grep xrdp $ So it appears xrdp is not starting (or is shutting down), but sesman is running ok. Not surprisingly, xrdp does not work - connection refused. If xrdp is then restarted manually: $ ps -A | grep sesman 3303 pts/0 00:00:00 sesman $ ps -A | grep xrdp 3301 pts/0 00:00:00 xrdp $ cat /var/log/sesman.log [20090530-00:59:49] [INFO ] starting signal handling thread... [20090530-00:59:49] [INFO ] signal handler thread started successfully [20090530-00:59:49] [CORE ] starting sesman with pid 2353 [20090530-00:59:49] [INFO ] listening... [20090530-01:05:52] [INFO ] shutting down sesman 1 [20090530-01:05:52] [INFO ] starting signal handling thread... [20090530-01:05:52] [INFO ] signal handler thread started successfully [20090530-01:05:52] [CORE ] starting sesman with pid 3303 [20090530-01:05:52] [INFO ] listening... xrdp works - I can login remotely. -- xrdp dies when starting at boot time https://bugs.launchpad.net/bugs/339032 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
