And yet you still refuse to admit that the lockups you are having are due to a bug in the X server or driver and insist on blaming KDE4. KDE4 certainly has its issues, but it is not responsible for locking up your machine.

Adam

Heeeeyy! Win98 was VERY stable...As a two-legged chair.

Are you sure about that? I'm not having any problems in Xfce. It would be interesting to hear from someone who has installed KDE 3.5.10 in Slackware 13.

Again, if the X server is locking up, there is a bug in the X server or driver. Period. No matter how stupid an application is, the X server should never, ever, lock up.

And, as I said above, it is quite possible that KDE4 is doing something to trigger the lockup, but there's still a bug in the X server or driver (and given that you are likely using fglrx, I'd wager that the problem is with the driver).

Adam

write a program that captures the mouse and keyboard input and that loops senseless forever.
you may think that X hangs, but...
so it could be possible that X is not the problem...

This is among the reasons I asked the questions that I asked in my first reponse to the OP (such as if he can remotely access the machine from another computer). Even in the case described above, control+alt+backspace should still kill the X server, though (at least on Slackware 13 where that key combination is not disabled by default).

Adam

My computer runs 24/7. I am using KDE-4.2.4. I have never had a completely frozen state as of yet, but I am using the latest nvidia driver. I have had apps hang that I simply killed with no other problems.

That said, I have had to resort to alternatives for a few things I used to do exclusively from within KDE or a KDE app. Like burning an iso, or using kdesu dolphin since there is now no file manager superuser available.

All in all, I like KDE4x, and am looking forward to KDE-4.3.1. I'll bet it hits current as soon as the team is back from R&R.

You know what they say about assuming?
I'm using the generic radeon driver.

Ah the Generic Radeon driver works crap for me, if you have an HD2400+ use the latest fglrx or if you have an older card use 9.3. I'd be interested to know if you still get crashes after because I sure don't as soon as I apply the fglrx driver.

I said it was likely, not that it was definite :-) There was no assumption there.

What GPU, exactly? And, seriously, are you using KDE's desktop effects and have you tried disabling them?

Adam

I have an "older" card and the 9.3 drivers are the last ATi made that will work with it. However, with Slackware 12.2, DRI support was not possible with the 9.3 drivers, at least not with my card.

I can't speak for the original poster or others, but I empathize with the general feelings about KDE 4.2.4. I'm using 13.0 32-bit and 4.2.4 with my new HTPC. I'm not running a heavy desktop. A few widgets and XBMC or Xine. Typically Konqueror and Kate or KWrite to edit config files. I'm hardly taxing the system. Yet KDE freezes. Or Konqueror freezes. Or I'll press a keyboard shortcut to start Konsole and the app fails to open for about 45 seconds. XKill often does not work or takes a long time to finally zap an app. Sometimes the mouse pointer disappears and then reappears. I've had KRunner crash while typing the app I want to run. Most of the time I just press Ctrl-Alt-Backspace and restart X/KDE. I'm using a 2.6.30.5 kernel and Nvidia 185.18.31.

The problem is not hardware as I have 12.2/3.5.10 on the same hard drive and never experience the same problems. For a while I adopted the attitude that the problem likely was me trying to adapt the some of the new ways KDE 4 functions. But there is just too much freezing all the time.

I notice a few suggestions in this thread and I hope to try some of them. Although the new X is not supposed to need much of an xorg.conf with the proprietary Nvidia drivers, perhaps I need to add some options. I have not dedicated serious time to troubleshooting but something definitely is not right. Hence, I'm not going to argue against the original poster.

Woodsman, try disabling nepomuk... That seems to be a huge consumer of resources and known to slow KDE4 down drastically on many machines.

Adam

The best way to disable necromonger (aka nepomuk) is to use another desktop.

This just illustrates the KDE4 problems - a thing known to eat resources, and with no actual use at this time, enabled by default and with no obvious user choice... call it KDE-Ballmer...

Fluxbox or XFCE is the best solution for disabling it, IMO.

You need to compile your Kernel with MSI Support in 12.2, this is not a problem in Slackware 13.