You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

wombat53

Beginner

  • "wombat53" started this thread

Posts: 2

Location: NY

Occupation: Database Management Specialist

  • Send private message

1

Sunday, June 5th 2005, 6:31pm

Upgrade to current KDE, and cascading woes ..

Hi Group,
I have gotten self into a bit of a mess, and would greatly appreciate some help. I am finding that small upgrades can lead to spending dozens of hours, and ending up in a worse spot that by doing nothing. Right now, I have no windowing functionality in Linux at all.

Anyway, I decided to upgrade my KDE to the current release (3.4.1) on my Slackware 9.1 system. This seemed innocent enough; I d/loaded the .tgz files and installed with upgradepkg.
The install messages were fine, but startx failed, could not start kdeinit, and the reason was inability to load shared file libidn.so.11. Seeking help on the web (from another machine's browser), others had encountered this, and recommended install of another package libidn (GNU Int. Domain Name lib), and that is what I did.
New message from startx : couldn’t find libXerama.so.1. More help on the web advised to upgrade X itself. I dutifully downloaded the XFree86 4.5.0 binaries, ensuring that I had right binary distribution: it comes with an aid “Xinstall.sh -check” which I ran, and was told I must download Linux-ix86-glibc23 . Again, I did this, installing all 11 mandatory files (and a few of the optional ones (of which there are 13).
Again the install messages (from X) were fine, but startx failed, could not start kdeinit, and the reasons appear in two categories
a) /lib/libc.so.6 version ‘GLIBC_2.3.4’ not found, (required by /opt/kde/lib/libkdecore.so.4), and a second category
b)couldn’t find init font path element /usr/X11R6/lib/X11/fonts, removing from list, and later:
xset: bad path element (#96), removing from list; possible causes are
i) Dir doesn’t exist or wrong permission
ii) Missing fonts.dir
iii) Incorrect font server address or syntax
usr/X11R6/lib/X11/fonts does exist rw- r--r--, and has a fonts.dir of 2 bytes with a value of 0 therein.

So that is where I am at. Clearly I need to do something with glibc, but I would appreciate guidance. I don’t want to keep endlessly installing and endlessly failing, and getting into ever deeper waters.

And I am mystified by the fonts business, whether it is even from an optional X package (like Xfsrv, in which case perhaps it can be uninstalled)), or a mandatory one.
I realize I have to attack this piece by piece, and appreciate any help I can get. Right now, I have no windowing environment at all
Regards,
George Peters
Strategic Database Systems Inc.
Proudly celebrating 25 years in Database and Data Management

toyg

Beginner

Posts: 5

Location: Manchester, UK

  • Send private message

2

Tuesday, June 7th 2005, 6:00pm

RE: Upgrade to current KDE, and cascading woes ..

First, try to fix your XFree, testing it with another windowmanager (fluxbox, fvwm...).
To do it, you need to find the init script that X uses (might be ~/.xinitrc or /etc/X11/xinit/xinitrc or something else, do a "locate" search for xinitrc), comment "startkde" and put in something else to start the other WM (say, "fluxbox"); fluxbox should be in your installation cd. This should limit your range of problems.

Once that is fixed, then "attack" KDE. I would recommend to
A) use only Slack-sanctioned package; no linuxpackages, swaret or other crap;
OR
B) compile from source (long and painful, I know) and then use checkinstall to easily remove it if something goes wrong.

If the problem really lies with the glibc, you are definately better off backing up your /home directory and then wiping/reinstalling a brand new more recent Slack -- there are so many dependencies with glibc, it really is not worth the hassle to manually track and fix everything.

Slackware is a very nice distro to learn Linux "the hard way" and build hardened servers, but it can be a pain to do multimedia/desktop stuff with it. You might consider a switch to Debian (new version out today), whose APT system is absolute magic.
Giacomo L.

wombat53

Beginner

  • "wombat53" started this thread

Posts: 2

Location: NY

Occupation: Database Management Specialist

  • Send private message

3

Tuesday, June 7th 2005, 6:10pm

toyg
Many thanks
What I did was "back out" - uninstall - the new KDE - and re-install from Slackware 9.1 CD's. Perhaps the new glibc was a documented pre-req for KDE, but I did not see that.

After a couple of hiccups (rebuiling of desktop references.shortcuts), the most current X remains in place, it works, with the "old" KDE. Perhaps in future, I will either look more carefully for pre-requisites, and/or upgrade the entire system, altho' it seems to me that an upgrade of the desktop should not require such a major thing.
Thanks
George
Regards,
George Peters
Strategic Database Systems Inc.
Proudly celebrating 25 years in Database and Data Management

toyg

Beginner

Posts: 5

Location: Manchester, UK

  • Send private message

4

Tuesday, June 7th 2005, 6:41pm

most probably, the KDE binary package that you donwloaded was compiled against a newer glibc. You might try compiling KDE yourself straight from source (there's a tool, called Konstruct, that might help you); if your glibc really is unsupported, the configuration script will make it clear, otherwise it should work fine.

Differently from the Windows world, Linux window/desktop managers are distribution-indipendent and it's then up to the various organizations to check that their KDE binary packages are ok. If those don't work, the only alternative is to try compiling by yourself... but hey, with Windows you couldn't even do that ;)
Giacomo L.

Lethe

Beginner

Posts: 41

Location: Pompey, England

Occupation: IT network/sysadmin

  • Send private message

5

Tuesday, June 7th 2005, 7:39pm

Quoted

Originally posted by toyg
most probably, the KDE binary package that you donwloaded was compiled against a newer glibc. You might try compiling KDE yourself straight from source (there's a tool, called Konstruct, that might help you); if your glibc really is unsupported, the configuration script will make it clear, otherwise it should work fine.


That is indeed the problem - AFAIK the only KDE 3.4.1 packages around are for Slackware 10.1 - a whole new environment.

I used Konstruct to update my Slackware 10 here.

Nick