Ok so this isn't going to be complete (bad memory, me not the computer) but I'll go through what I've just done to get KDE upgraded from 3.5.5 to 3.5.6.

Don't know exactly what the benefit is, but I'm using Quanta+ a lot at the moment and am hoping it's going to be more stable now!

So I downloaded kdeXXX-3.5.6-i486-2.tgz packages from the main Slackware FTP site under pub/slackware-current (as my usual mirror and those I tried hadn't got the latest package ... which I didn't realise 'til I'd spent an hour downloading all the packages!! )

What I usually do now is to go into runlevel 1 ("telinit 1" as root) upgradepkg the kdelibs first, then the kdebase, move them out of the dir with all the downloads and then (then "telinit 4"). However I've used slapt-get recently and upgradepkg wouldn't remove the old packages in some instances (where they were relabelled with times when they'd been updated). So for persistent packages I had to removepkg them first, ,eg "removepkg kdeaccessbility".

So, the installation went ahead but kde no longer worked.

I eventually established that I needed to have some new packages and installed (via slapt-get) libxcb-1.0, expat-2.0.0, findutils-4.2, qt-3.3.8 (error mentioned this package), gcc-4.1.2 and cxxlibs-6.0.8 (error with libstdc++.so.6), gpgme-1.1.4 (error starting kontact about gpg issues).

I did have to remove a symlink for libstdc++.so and also manually remove the old libstdc++.so.6.0.3 - leaving me with libstdc++.so.6.0.8 .

So after all that I still couldn't just reboot and get a fresh KDE.

There's something gone on with X and kdm binaries being moved. I was getting an XDM login box and not a kdm one so I had to change "/etc/rc.d/rc.4" to point to the new kdm location (was /opt/kde/bin/kdm ... is now /usr/bin/kdm). Still didn't fix it ...

Last thing was to change kdmrc to point to the new "X" location. I found a /etc/X11/kdm/kdmrc with a pointer to where X should be which I changed to "ServerCmd=/usr/X11/bin/X -br".

Seems to be working fine now. Easy when you know how; I guess if I upgraded Xorg then the last bit wouldn't have been a problem? But, I'm using an old Nvidia card and it's a bit tricky getting the module to compile and I don't want to push my luck.

I think I'm a little closer to that Kubuntu install today!

HTH somebody.

---
Incidentally the upgraded cxxlibs seems to have fixed my inkscape problems wrt errors that again mentioned libstdc++.so.6

You do not want to run the slackware-current packages on slackware-11.0. they where compiled with a different gcc, glibc, X, ect ect. Your lucky if you can even get it to load up but it will never be stable.

You can find KDE packages compiled for slackware 11.

Cheers XGizzmo, seems stable so far ... I don't exactly have a vanilla install! This is an upgraded Slackware-8 IIRC, own kernel 2.6.16.13, some of packages (that I don't use!) will be 10, some 11, some is self-compiled, some is current. When I do "slackpkg upgrade-all" most of the packages presented (that I recognise) are older than I have.

I have a fresh Slack 11 install and all I did to get 3.5.6 up an running was to Ken's Zalewski's packages from LinuxPackages.net

http://www.linuxpackages.net/pkg_details.php?id=10117

Make sure to READ the README for dependencies needed, all can be found on LinuxPackages.net

BTW, this guys packages are reliable, I pretty much use his exclusively becasue they just work!!

Everything is working here smoothly ;- )

just install the stock Slackware build of qt, then download aRts, KDE-Libs, KDE-base, compile aRts first, KDE-Libs second, KDE-Base third, the rest of the KDE packages are optional,

the only configure parameters i only use are --prefix-opt/kde --disable-debug

I'll add a second to that. I've noticed I'm using a lot of kjz packages now too and have never had a problem with them (that I know of). My choice first is to use Slackware original packages then kjz, then others I've used in the past and then autopackage, then self-compile; I try un-heard of packagers as a last resort.

Thanks Mr. Z.