Try the syntax I gave you, which I in turn was given some time back. The output
is more comprehensive. If it's not very current, you can be sure the cpu
resources are getting hogged by something. The other one to check is the
xinitrc file. That at least is in the obvious place - NOT!
/usr/X11R6/lib/X11/xinit/
--
Regards,
Declan Moriarty
> Declan Moriarty wrote:
> > Have you tried piping the output from X to a file to see what the system
> > thinks it's doing? If you're starting X from a console, I think the line is
> >
> > startx >xerrors 2>&1.
>
> That might be a solution. Cheers.
>
> > There's a standard output hidden (like everything in Unix) in some obscure
> > file anyhow. It would be interesting to know what problem the system sees
>
> I started to look for one, but at 3 o'clock in the morning I decided to get some
> sleep before another working day.
>
>
> Any help still appreciated.
> Thanks for the suggestions already sent.
>
> Darek
