I did an update to Kde 3.5.2. I followed the instructions from this page.
He said to grab the latest Kde packages out of the KDE directory at the Slackware mirror sites. I got the packages from the slackware current directory (which probably wasn't a good idea).
After I did the update Kde wouldn't start. So I started Gnome and tried to run gwenview and it wouldn't run. So I installed cxxlibs-6.0.3 and gwenview ran. Now, when I try to start KDE I see my splash screen with a black background. I goes back to my login manager after it hangs about halfway though.
Please Help.

please post your error messages. There could be many reasons for this. WHen I updated KDE I had to also update some dependencies. The error message will tell you which ones you need.

regards,
...drkstr

I'm not getting any error messages.
Is there a way to run KDE so I can get some error messages?

How are you starting kde? try 'echo startkde > ~/.xinitrc' as the user you want to run kde, then start with 'startx'. If it still fails, copy the text that get's dumped to the terminal. It will say something even if it doesn't look like an error.

regards,
...drkstr

I use runlevel 4.
I changed to 3 and tried:
All I get is my splash then a black screen. I have to turn off my computer after that happens.
I do see some text come up for just a second but it goes away before I can copy it.
Thanks for your help!
Are their any crash logs somewhere?

change your /etc/inittab to boot into run level three. This makes debugging X problems easier. Once you have booted to run level three, type 'startx' If you get a blank screen that you can't get out of, hit 'ctrl+alt+backspace' to crash X and take you back to the terminal. You should now be able to read any errors that were dumped to the console.

regards,
...drkstr

I changed my /etc/inittab to level 3. When kde crashed 'ctrl+alt+backspace' didn't do anything.

since you said you are booting to runlevel 3 now, another option to see error messages is CTRL+ALT+F1 (do this when kde appears to crash after the splash screen)

may not work if it's hard crashing the system but that really shouldn't happen

This is why we don't install developmental software on machines that we mind if they crap out

I would try checking the log files, maybe they have some good info.

~/.xsession-errors (or something along those lines, I'm typing from memory)

and

/var/log/Xorg.0.log

If you see anything that might be interesting, please post.

regards,
...drkstr

**edit**
it might be easier to just uninstall KDE packages and install the latest ones from Slack 10.2, but I will continue to try and help if you are determained to get the current version working.
**edit**

I can't seem to find anything in the log files.

I did forget that when I use run level 3 I can't log out of Gnome or Kde. When I first installed Slackware I would try to log out and I would just get a black screen. I changed runlevel to 4 and it seemed to fix my problem. I guess thats why 'ctrl+alt+backspace' doesn't work.

Should I just remove the packages I installed and replace them with the ones from 10.2?

No, I'm just ready to get it working again. I do kind of like Gnome after using it for a while though.

did you use -stable or -current packages? I usually get all the -current packages, so it works for me, since KDE 3.5.2 is also in -current tree. Perhaps you will need to update some of your packages with packages in -current.

btw, what was your previous KDE version? i jumped from 3.4.2 into 3.5.0 and now i'm using 3.5.2. I'm having a problem also after i upgrade some packages in -current recently, but the packages was not related to KDE (that confuses me). It won't load KDM when i boot into graphical mode, but when i boot into text mode and run startx, it will go to my desktop with KDE instead.

So, try to boot into text mode and run startx and see if it works.

i upgraded to 3.5.1 when i wrote that article and for 3.5.2, it seems that it will need more information, mostly if you follow the current tree, since there has been a lot of changes there.

I just remembered something, you need to upgrade glibc to the latest version in Slack-current use the latest version of KDE. You will also need a few other packages but I do not remember what they are. After you have upgraded glibc, run startx again. X will start to load then fail back to the console with an error. Look for the portion of the error that says "file not found" then search for that file with the "search by file name" option in the slackware package site. Keep installing the packages for the files it needs until you no longer get any errors ( I think there are 2 or 3 packages to install )

regards,
...drkstr

Current

3.4.2

I don't use KDM. I use GDM (if that makes a difference). I tried to boot with startx but I get the black screen.

I seem to have a problem that keeps me from doing that. If I run level 4 KDE locks up and then goes back to my login manager. If I run level 3, KDE locks up and stays there and I have to turn off my box. If I run level 3 I can't log out to the login screen.
Maybe I will see some errors with run level 4 after I install glibc?

Is this the glibc package I need?
glibc-solibs-2.3.6-i486-3.tgz

Thanks for both of your replies!

installing the current glibc should fix your "lock up" problems, but will not get it to work entirely just yet. You will need to boot into run level 3 after the glibc update and fix any errors you get from running 'startx'. Should work fine after that.

regards,
...drkstr

**edit**
no, I belive it is glibc-2.3.6-i486-2. It probably wouldnt hurt to install them both though. I can't remember if I did both or not when I updated my KDE.
**edit**