Re: Konsole segfault and core dump

Erik Farnsworth wrote:
> (FYI--mdk 9.0 on an i686) 
>
> I have had problems with Konsole after upgrading to the full Qt
> (Qt3, in my case).  Someone on a mandrake list said he also had the same
> problem with Konsole and Kmail after building and installing Qt2.  I
> don't use kmail, so that one isn't an issue for me. (It is a hassle
> shutting down and restarting artsd after booting to have system sounds,
> though.)  Right now, I can do everything I need to do in Konsole with a
> virtual console, so I can get along while figuring this out and fixing
> it.
>
> When I try to open Konsole, I get a segfault and core dump from
> libc.so.6   Tracking down the problem, I've found that in /lib/i686/ and
> /lib/, libc.so.6 it is symlinked to libc-2.2.5.so but in /lib/lsb/ it is
> symlinked to libc-2.2.90.so  Looks like a good setup for a
> conflict...and if I try to list the contents of /lib/lsb/ from _inside_
> the directory,I get a core dump...from _outside_ the directory, with a
> full path, I get the list.
>
> My first inclination is to change the symlink in /lib/lsb/ for lib.so.6
> to point to the libc-2.2.5.so  to match the other two and allow
> libc-2.2.90.so live there, too, in case something needs it.
>
> Before I start changing symlinks, does anyone have an educated guess if
> this is the correct change...or if there is something else I need to fix
> instead?  Also--can changes be made while  running kde, do I need to use
> a window manager other than kde or will I need to boot the install
> CD1/rescue to make the changes without the filesystem mounted?

You could get into REAL trouble here.  You could wind up with a system 
that won't boot.  So, the first question is, do you have a rescue disk, 
not just a boot disk?

If at all possible, DO NOT just remove the files or change the links by 
hand.

First, I would simply run [as root]:

        ldconfig

and see if that fixes the problem.

Then open an Xterm in your usr account's home (~/) and execute:

        konsole

What error message do you get?

Then you should see if RPM knows about both of them.

        rpm -q glibc

Post the results.

Also, AFAIK, there is no: "libc-2.2.90.so" would you please double check 
that?  Such a designation might have been applied to a CVS snapshot.  Do 
you remember installing this from COOKER????  And aren't Mandrake RPMs 
usually i586?

This complicates matters since the non-standard version RPM may not work 
correctly.

What I would do is from the console [as root]:

        init 1

        cd <directory that the RPM is in>

        rpm -Uvh glibc-2.2.5*i586.rpm --force

        reboot

If you do this, be certain that you are reinstalling the CORRECT RPM -- 
the one that came with your system or the correct upgrade, not something 
from cooker!!

This should fix the problem if RPM knows about both of them.  Or, it 
could break your system.

Now the question of how you managed to get two versions of GLibC on your 
system.  They didn't get there because you installed Qt.  You must have 
installed it (the second one).  And the problem is probably that you 
INSTALLED it instead of UPGRADING.  Please RTFM page for RPM to see the 
difference between installing (-i) and upgrading (-U).

--
JRT


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