kstartupconfig4 error

[Jim Bevier]

I did an i386 upgrade from F11 -> F12 on two different systems using the install 
DVD.  They both use gnome and kde desktops.  After the upgrade, I try to log in 
using kde and I get the error: "kstartupconfig4 does not exist or fails.  The 
error code is 127.  Check your installation".  After some searching, I found 
this same error was present in F10->F11 upgrade.  It seems during the upgrade, 
libssl.so.8 and libcrypto.so.8 links are removed and kstartupconfig4 can no 
longer start.  In /usr/lib I did "ln -s libssl.so libssl.so.8" and "ln -s 
libcrypto.so libcrypto.so.8".  This then allowed kstartupconfig4 to run and kde 
worked again.  I did not see any mention of this problem on the rawhide list 
during beta & RC testing, so I guess nobody did this type of upgrade.  Hope this 
helps someone.

Jim

[potat0]

YEBO Jim,

you rock man.

thank you. been searching the web for this from Thursday. I could log on to gnome but I am a kde fan, when I got this error I assumed I have upgraded incorrectly and I think fedora guys can do better with this one. I mean symbolic links should have been done simply during upgrade. I was and i am still disappointed by this.

thanx once again it worked.
Lefu :-)

[Rex Dieter]

lefu wrote:
> YEBO Jim,
>
> you rock man.
>
> thank you. been searching the web for this from Thursday. I could log on
> to gnome but I am a kde fan, when I got this error I assumed I have
> upgraded incorrectly and I think fedora guys can do better with this one.
> I mean symbolic links should have been done simply during upgrade.

Symlinks are the wrong solution.  The likely root cause here is a handful of 
f11 packages didn't upgrade properly.  The correct way out is finding out 
exactly what they were, and resolving why they got held back.

-- Rex

[potat0]

> Rex Dieter wrote:
> lefu wrote:
> > YEBO Jim,
> >
> > you rock man.
> >
> > thank you. been searching the web for this from Thursday. I could log on
> > to gnome but I am a kde fan, when I got this error I assumed I have
> > upgraded incorrectly and I think fedora guys can do better with this one.
> > I mean symbolic links should have been done simply during upgrade.
>
> Symlinks are the wrong solution.  The likely root cause here is a handful of
> f11 packages didn't upgrade properly.  The correct way out is finding out
> exactly what they were, and resolving why they got held back.

I had this exact same problem.

kdeworkspace-libs was linked against the older stable openssl, 0.9.8k I think.  F12 ships 1.0.0 beta.

yum update fixes the problem nicely, kdeworkspace-libs is now compiled against the newest libraries and all works nicely.  (updated this thread since it's top 5 in google for this problem.)