Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I spent much of the weekend upgrading my KDE to current on Skackware 9.1, then force to upgrade X (also to current), but was unable to proceed further due to certain GLIBC requirements not being met (kdeinit could not start for this reason), thereby losing all windowing and the desktop.
To cut a painful story short, I backed out the current KDE, and re-installed it (3.1.4, I presume) from the Slackware 9.1 CD's. (The curent X, at 4.5.0. binaries, remains in place).
So, I now have a desktop back, but none of the important desktop icons work. Many basic desktop functions fail:
example, clicking Konqueror web browser yields: Could not find Service: Internet/konqbrowser.desktop. Other icons produce similar. Even a terminal/shell couldn't find Service: System/konsole.desktop. And so on.
I am sure these settings/associations are maintained in a file which has been lost/corrupted in the process.
My researches lead me to /home/myusername/.kde/share/applnk as a like suspect, but after 24 hours non-stop, I have no further energy for this.
Is there a (preferably simple) way to get the Desktop icons and references functioning again? To "rebuild" them, so to speak? A setup program, a configuration utility. Can it be pasted here , mailed to me?
My guess is that you should remove all the configuration files related to KDE under your home directory (.kde and others).
Then try again, things should be recreated with the version you're using, of course you'll have to configure KDE again.
Most software provides configuration compatibility with older version but not with newer
gobonvehi - many thanks. Yes, the settings did seem to "re-build themselves" after reboot! I remain surprised that I needed GLIBC_2.3.4 to get the new KDE working (or else, I had erred somewhere else).
I wonder what level of GLIBC other upgraders to current KDE have had?
You could use the new KDE if you compiled it yourself so it could match the libraries you've in your system.
Most users update all the software (Slackware) to current, so KDE will have the libraries it was built against.
Again, thanks. Yes, it makes sense to compile the KDE and so have it in synch with what is currently installed. But I am simply not at that point. Perhaps it was just not a good idea to install more recent binaries (for KDE), but to be honest, I don't see why. Unless, the KDE upgrade doco specifically stated that that is pre-reqs/dependecies required that version of GLICB. To be honest I, I don't know...as they say..Read the Fine Manual ...<g> Intuitively, it seems that install of a more recent user app , (which is all KDE is), over a stable OS should be fine, unless the dependecies and pre-reqs are very clearly stated; like installing MSWORD 2002 over MSWORD 97, should still work on WIN 2000, if you know what I mean...). The requirement may have been stated, and perhaps I simply was unaware....don't know..
Let me add that SLACKWARE 10.1 does appear to include an upgraded GLIBC., and perhaps one should do the upgrade all at once? (aka "big bang" implmentation). OTOH, in the world I come from (a vanishing world, perhaps), one doesn't t make multiple system software configuration changes at the same time.....as I said , making a change to the Desktop UI seems harmless, in itself. Looks like I was wrong. Perhaps there are different change management philosophies in place.
What is being said here, is that if I want to upgrade a user app, I must upgrade the entire OS and perpheral products? Dependencies and pre-reqs I understand, and agree with, but the whole shebang? That seems excesive, IMHO.
From SLACKWARE 10 Notes (below): we can see the supplied GLIBC upgrade to 2.3.4
Also interesting is that , when all was said and done, XFree86 DOES run on the earlier GLIBC, and is still in place on my box, working fine. I have to assume that KDE doco says "you must have GLIBC 2.3.4 as a pre-req for KDE 3.4.1" and that I missed that...If its does not say that , then that would be a problem, a documentation error (at best). I will look tomorrow. It's late now!
Fri Jan 28 20:24:09 PST 2005
a/glibc-solibs-2.3.4-i486-1.tgz: Upgraded to glibc-2.3.4.
a/glibc-zoneinfo-2.3.4-noarch-1.tgz: Upgraded to glibc-2.3.4.
l/glibc-2.3.4-i486-1.tgz: Upgraded to glibc-2.3.4.
l/glibc-i18n-2.3.4-noarch-1.tgz: Upgraded to glibc-2.3.4.
l/glibc-profile-2.3.4-i486-1.tgz: Upgraded to glibc-2.3.4.