[TAG] startx problem

[J.Bakshi]

On Tuesday 07 Oct 2008 11:44:16 pm Ben Okopnik wrote:
> On Tue, Oct 07, 2008 at 05:41:22PM +0530, J.Bakshi wrote:
> > On Tuesday 07 Oct 2008 1:19:55 am Ben Okopnik wrote:
> > > On Mon, Oct 06, 2008 at 09:30:41PM +0530, J.Bakshi wrote:
> > > > On Monday 06 Oct 2008 11:38:50 am Karl-Heinz Herrmann wrote:
> > > > > You could try starting X manually, then start some windowmanager
> > > > > after to get winodw handling. Remember to redirect the stdout and
> > > > > stderr to a file to get all the log.
> > > >
> > > > I have done "startx 2> log" and then read the file "log" but there is
> > > > nothing new. It just provided the same FPE font path error which I
> > > > have emailed befor. Hence I have not mentioned the same here.
> > >
> > > Try launching X directly - i.e., rather than using 'startx' or 'xinit'
> > > (both of which use your private startup files, and thus add another
> > > layer of complication), just type 'X', or perhaps 'X :1' to start it on
> > > a second display (i.e., VT8.) If you want detailed error logging, you
> > > can use the '-logverbose 255' as the first option.
> > >
> > > Incidentally, I've noted in the past that the "refcount is 2, should be
> > > 1" message normally does not happen until X exits; i.e., by the time
> > > you see it, X has already crashed. When X is launched via 'startx',
> > > crashes like this, and there are no errors, I usually suspect the
> > > private config files - i.e., either '~/.xinitrc' or '~/.xsession'. As
> > > Karl-Heinz has mentioned, you need to launch something - some kind of a
> > > window manager, or at the very least an xterm - to keep it open.
> >
> > Hello Ben and Karl,
> >
> > Thanks a lot. Your debugging skill are awsome. Ben you have discussed
> > briefly what Karl suggested. With all these knowledge and suggestion I
> > have fixed the proble. I first started x manually with "X" command and
> > The xwindow came up. I checked the ps too and got Xorg was running. Then
> > I focused on the .xinitrc file and got the culprit . There was only
> > #startkde !! I deleted the comment symbol and startx command works :-) In
> > these whole debugging process your suggestion always backed me up. When
> > the problem was solved it were Ben and Karl whose name first came in my
> > mind. Thanks a lot
>
> Excellent! Glad to help, and thanks for letting us know what the
> solution was.

Thanks for helping and being with me to fix it.