OoO En ce début de soirée du jeudi 06 mars 2008, vers 21:39, je disais: >> This is the procedure: >> * Install package (and start service) >> * Install gnome >> * Login using rdesktop and the sesman-Xvnc function. >> * A gnome desktop is shown >> * Logout from the gnome desktop using the logout function there. >> Now the Vnc server terminates and rdesktop terminates as well. >> Quite as expected actually. >> * Login again using rdesktop and the sesman-Xvnc function. >> * Login is accepted bug it can no longer connect to the vnc server. >> Because it has terminated and it thinks that it is up.
>> What probably needs to be done is to add an error handler when it >> can not connect to the vnc server with old data. > There is already some code in xrdp to handle the end of a session. xrdp > clean out a user session when this session is terminated. There is a > signal handler in sig.c that will call session_kill() in session.c. > But you are right, this handler seems to not be called. I will try to > investigate this issue. Well, that is a pity. I am now unable to reproduce it while I was able to reproduce it on my laptop at work. Could you confirm that you don't get a line like this one when you log out of gnome : [20080306-21:45:15] [INFO ] session 7075 - user bernat - terminated If you don't get this line, could you look at a line like this one : [20080306-21:44:51] [CORE ] error starting sessvc - pid 7075 - xpid=7078 - wmpid=7077 Does process the process after "pid" still exists ? Maybe sessvc can help here. I don't really understand what it is for. There is the same code in sesman.c. Jay, any hint? -- COFFEE IS NOT FOR KIDS COFFEE IS NOT FOR KIDS COFFEE IS NOT FOR KIDS -+- Bart Simpson on chalkboard in episode 9F09
