[copy for the list minus the trace]
On Mon, Jun 28, 2010 at 08:47:17AM +0300, Timo Lindfors wrote:
Roger Leigh rle...@codelibre.net writes:
Is this with or without your fork patch?
Without. With the patch it exec()s Xorg and of course does not execute
any schroot code after that.
Right.
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
Roger Leigh rle...@codelibre.net writes:
Is this with or without your fork patch?
Without. With the patch it exec()s Xorg and of course does not execute
any schroot code after that.
Right. From the console, I can start X with
schroot -c sid -p -q -- X :1
or
schroot -c sid -p -q --
Roger Leigh rle...@codelibre.net writes:
What command are you using to run gdm?
gdm is started by init normally. I am only running Xorg from the chroot.
What are you using for command= ?
/etc/gdm/gdm.conf has
[server-Standard]
command=/usr/local/bin/sid-X
where /usr/local/bin/sid-X contains
On Mon, Jun 07, 2010 at 01:45:47AM +0300, Timo Lindfors wrote:
Some background info: I was trying to help a friend get his new laptop
work with debian lenny:
When I tried to trick gdm into running Xorg from an unstable chroot I
noticed X would just die with Caught signal terminated right
5 matches
Mail list logo
