I think you'll need some more information. v0.9.7, v0.9.8, v0.9.9 have this bug. The upcoming v0.9.10 includes this fix. I know Debian hardly apply version update except unstable so I want you to consider applying this fix to the branches such as stable-bpo. The original issue #1315 is reported by a Debian user. At least a Debian user is annoyed because of our bug.
This issue is a kind of availability. New sessions cannot be started after xrdp-sesman caught SIGUP unless DefaultWindowManager in sesman.ini is specified in full path. Same with ReconnectScript. It won't be executed unless it is specified in full path. I'm not sure Debian rotates xrdp log, the major scenario that xrdp-sesman catch SIGUP is log rotation. -- meta <m...@freebsd.org>
