X starts, and then :
> X connection to :0.0 broken (explicit kill or server shutdown).
> X connection to :0.0 broken (explicit kill or server shutdown).
and the forked child exits.
I think it is an authorization problem.
[You tried startx, of course ?]
Hmmm... it looks like the best thing to do would be to submit this to
[EMAIL PROTECTED]
in order to reach kdm's maintainer.
Another strange thing is the number of bytes it's reading from /dev/urandom,
no idea what for... But it might be normal.
--
David Faure
[EMAIL PROTECTED] - KDE developer
[EMAIL PROTECTED] - Mandrake
[EMAIL PROTECTED] - Cramer Systems
