Re: Still more X trouble from the install, but some progress!
On Tue, Jan 13, 2004 at 01:43:35PM -0000, Jim Higson wrote:
> On Mon, 12 Jan 2004 23:27:40 -0600, Kent West <westk@acu.edu> wrote:
> >Jim Higson wrote:
> >>but after a few seconds moment there is a fatal server error: caught
> >>signal 11. Server aborting.
> >>
> >>I rebooted. This time I get the login screen, I type my
> >>username/pasword (mouse still working), KDE starts loading but about
> >>halfway through takes me back to the login screen. After a few tries I
> >>try signing in as root, but this time it throws me out to the comand
> >>line!
> >>
> >>I've noticed there are a few errors reported in the syslog relating to
> >>fonts, plus one towards the end of XFree86.0.log. Get newly uploaded
> >>versions here again: http://users.aber.ac.uk/jqh1/x/
> >
> >I don't see anything obvious; the font errors should be ignorable for
> >now. I suspect a problem with KDE; I'd suggest you try something simpler
> >for now, like icewm (apt-get install icewm, and then choose icewm from
> >the menu in your login screen if it exists, or create a file in your
> >home directory with the name .xinitrc with the single line "icewm" in
> >it).
>
> I'm familiar with KDE though, and really like using it. In face, it
> was KDE that persuaded me to move my main computer over to linux.
>
> Now I've got one thing sorted out, another presents itself. I can't
> even find what this singal 11 means!
"Signal 11" is a segmentation fault: it means that a process accessed
memory that didn't belong to it. It's always either a hardware problem
or a software bug.
That said, it may be possible to work around the bug with a
configuration change.
> From the pov of a new user these problems look like bugs in debian
> stable!
They probably are, yes.
> Should I stick with debian, or is switching to another distro a better
> idea?
You could play distribution whack-a-mole :-), but I don't think there's
any particular reason why the X server crash you're seeing would be
Debian-specific. You could try a newer X server, which might be a good
option; various people have produced backports of newer versions of the
xserver-xfree86 package to stable. I don't know enough about X to debug
the real problem here, though.
I'd also report a bug.
Cheers,
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: