Problem Starting Yast On 64bit Suse 10.2

My systems been performing fine for months but recently my gfx card died in the machine taking it down hard. i had to strip it down and rebuild it and replace the card (after finding out it was that which had gone pop!). Annoying thing is the GFX card is used so rarely its untrue as this is a dedicated server...:s

I put it back together and my raid was a bit screwy but on boot it seemed to put itself back together. My mail server / web server / file server etc all came back and seemed to be in good condition.

However i logged into the box to do some routine maintenance recently and found that /etc/manpath.config had been mangled

as soon as i noticed that i tried to fire up yast to see if there'd been some damange done to the file system but it wont start..

I'm currently getting the following error:

/usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/YaST2/plugin/libpy2scr.so.2: undefined symbol: _ZNK18Y2ComponentCreator13createInLevelEPKcii

however previously i was getting a similar error that pertained to the boot_Dynaloader for perl :s.....

I have a sneaky suspicion that something with the ld.conf.cache of ld.conf in general has been wickedly mangled.

I'm a little stuck at the minute as I can't think of a way to resolve this its not as if I can run yast2 repair from the command line as yast wont start...

any ideas as whats the best approach here?

My systems been performing fine for months but recently my gfx card died in the machine taking it down hard. i had to strip it down and rebuild it and replace the card (after finding out it was that which had gone pop!). Annoying thing is the GFX card is used so rarely its untrue as this is a dedicated server...:s

I put it back together and my raid was a bit screwy but on boot it seemed to put itself back together. My mail server / web server / file server etc all came back and seemed to be in good condition.

However i logged into the box to do some routine maintenance recently and found that /etc/manpath.config had been mangled

as soon as i noticed that i tried to fire up yast to see if there'd been some damange done to the file system but it wont start..

I'm currently getting the following error:

/usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/YaST2/plugin/libpy2scr.so.2: undefined symbol: _ZNK18Y2ComponentCreator13createInLevelEPKcii

however previously i was getting a similar error that pertained to the boot_Dynaloader for perl :s.....

I have a sneaky suspicion that something with the ld.conf.cache of ld.conf in general has been wickedly mangled.

I'm a little stuck at the minute as I can't think of a way to resolve this its not as if I can run yast2 repair from the command line as yast wont start...

any ideas as whats the best approach here?
[/b]

HA usual case you post and then you work it out...the yast2-core had been corrupted , looks like a few other libs bought the farm but i'm working it out..

i fixed this by using wget to download the yast2-core package again and rpm --replacepkgs -i yast-core-2.14.4-9.x86_64.rpm

yast2 fired up straight away...

now to fix the other shafted files