Hey all,

I have this slight problem. While I was updating my GLIBC-libraries to the -current libraries, everything went wrong. I couldn't do anything anymore (lots of long errors).

I used my 2nd Slack CD, manually mounted my HD and reïnstalled the original GLIBC-packages.

Now all works fine (exept for my Apache2, but that's related to this problem I think, and not my primary concern). When I give my box an 'ldconfig' or when I install / upgrade a slackware package (using installpkg or upgradepkg) my bash gives me a 'Segmentation error' on every command I give in.

The only way I can resolve this is if I reïnstall my original glibc-solibs-package.


Anyone have an idea, other than reïnstalling my box ??



Thanks !!

Lennard

Youch.
This looks sticky.

Depending on how much customization you've done already, I'd try doing an
upgradpkg --reinstall *.tgz from the /slackware/l/ directory to reinstall all of your important libraries.

You might have to do that from a chrooted position, so you're not actually running commands dependant on your currently installed libraries. A live CD, second partition, or slackware rescue disc would work quite well for this.

That's the first thing I would try...

Also, run fsck.<filesystem name> on the partition and see if it can find any corruption.
The next thing to look for would be buggy kernel drivers. Are you running anything out of the ordinary? A wireless card via ndiswrapper perhaps?

--Shade
--Shade

Hey Shade,

Thanks for the great advice!! It however didn't work out for me
I think I'll just make another clean installation (yet again :-S) and make a ghost image of it when it is to my likings


Thanks again !!
Cheers !!

To drag this one back up from yesteryear...

Same scenario as lennard mentions above; tried Shade's suggestions to no avail.

The only thing I have to add, is that re-installing either glibc-solibs-2.3.2 or glibc-2.3.2 will kill the Segmentation Fault. Back-leveling pkgtools as far back as 9.x doesn't solve it either, so it would appear that this isn't something loopy with the 10.0 pkgtools themselves.

What puzzles me, is why would re-installing the 2.3.2 glibc libraries solve the problem when the last-installed package which presumably triggered the error, doesn't over-write or alter any of the libraries?

Something's screwey here, but I can't put my finger on it. Any ideas?

Anyone?

There has got to be a way to correct this without a wipe & re-install. Re-installing is for Windows.

When upgrading glibc you have to follow similar procedure as when upgrading to a new release - see UPGRADE.TXT for more. Almost every executable depends on glibc so after a change you have to upgrade all remaining packages provided by the same release too.

I'd suggest to reinstall/upgrade to current glibc-solibs, pkgtools, sed, libtermcap and bash first, check if content of /etc/ld.so.conf is not somehow messed up and then try to rerun ldconfig. Ldconfig is staticaly linked so it don't depend on libc.so.
Use of rescue/boot CD is a good idea.

I get the "segmentation error" sometimes when I try to use gtkpod. Sometimes it works fine and sometimes it crashes and I see the "segmentation error" in the console. I'm running Slackware 10.2 with 2.6.13. I did upgrade the kernel a while back and while I didn't use gtkpod before the upgrade so I can't say if the upgraded kernel is the problem. Not trying to hijack the thread just thought I'd share my segmentation error problem.

It has something to do with whether the ipod is mounted before gtkpod reads it or who has ownership. If i mount the ipod as root and run gtkpod as user then I get the error. At least that's what I'm thinking..

The above seems to have sorted it out. Much appreciated!