Kdm problem at boot

[Shawn P. Garbett]

On Friday 16 August 2002 03:50 pm, James Richard Tyrer wrote:
> Shawn P. Garbett wrote:
> > Okay so I dinked with it and I get what I deserve...
> >
> > With that in mind here's what happened
> >
> > I installed the Linux Progress Patch, and life was fine. I decided to try
> > different boot screens. Loaded one and went to compile it into the kernel
> > when the compile choked. Looked into it and the contributed lpp images
> > didn't work with the newer kernel layout. Found copies of the original
> > files before the change and put them back in. Recompiled kernel with no
> > trouble. Now kdm fails at boot time. I can start it normally as root
> > after boot.
> >
> > Any help is appreciated, Here's the syslog with full debug on kdm:
> >
> > --snip--
>
> <SNIP>
>
> > Aug 15 08:19:04 localhost kdm[926]: Found new display: :0  local at tty1
> > /usr/X11R6/bin/X -dpi 100 vt7
> > Aug 15 08:19:04 localhost kdm[926]: StartDisplay :0, try 1
> > Aug 15 08:19:04 localhost kdm[926]: startConfig
> > Aug 15 08:19:04 localhost kdm[926]: Getter ready
> > Aug 15 08:19:04 localhost kdm[926]: requesting config 4
> > Aug 15 08:19:04 localhost kdm[926]: Sending int 2 (0x2) to helper
> > Aug 15 08:19:04 localhost kdm[926]: Cannot write to helper
> > Aug 15 08:19:04 localhost kdm[926]: Wait4(913) failed
> > Aug 15 08:19:04 localhost kdm[926]: Unable to read configuration for
> > display
> >
> > :0; stopping it.
>
> The above is the actual error.
>
> This is somewhat of a puzzle since it first reports what it read from:
> "Xservers" and then says that it cant read the configuration for the
> display.  This could be: "Xsetup" -- do you have such a file?
>
> I note that I think that the line in: "Xservers" should be:
> :0 local at tty1 /usr/X11R6/bin/X vt7 -dpi 100
>
> and I don't know if that matters at all, and you probably haven't
> changed this lately.
>
> So, I really don't know.  Specifically, I'm not sure which configuration
> file it can't read.

I'm getting closer to figuring this out. Just fought a battle with filesystem 
corruption due to a block that went bad. Guess where the bad block was-- 
right in the middle of the kde setup files.

The other thing to note, is that it works if I start kdm as root. During 
boot, what user is running the init.d scripts? If it's not root then this 
could be a simple permission problem on one of the setup files. Could have 
gotten changed by the block going bad. mmmmm. Still poking at it.

Shawn
___________________________________________________
This message is from the kde mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.