Roger Leigh <rle...@codelibre.net> writes: > This is because when you remove the fork you competely replace the > schroot program with your program, and schroot never gets to run its > cleanup code (which is what kills your session). > If you run the unpatched schroot with --verbose --debug=notice, you > should see your session gets killed when the 15killprocs setup > script is run. Is this the case?
According to strace in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584831#15 no cleanup code is run in my case. > How are you starting X using schroot? Could I see your script > or command-line? Hmm, gdm.conf is listed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584831#15 also. Maybe you lost the mail? > One thing to look at is how X gets started. Does the X server > start gdm as a child process? In this situation, is gdm actually > visible inside the chroot? No, gdm spawns X or whatever the command= line reads, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584831#15 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
