My memento: exactly at this time after exiting from KDE 4 screen goes blank! What happened? I don't know. Luckily I was able to halt system via ssh login form other computer. The problem is that KDE 4 developers don't listen to those who complain about KDE 4. They seem to be satisfied that it works for 70% of users. But notice this is much serious. Say I cannot honestly advice other person - new to Linux - to use a KDE based distribution like eg. Slackware. Only what I can say is: it may work but it may doesn't work. One has 1/3 chances that KDE 4.x.x won't work. But notice it is the KDe 4.x.x which may be one of the reason to install Linux. It looks so nice

Let me say: to advice to use other a window manager or a 'lite' desktop is not a solution. What is expected is a full-featured desktop. It is rather misunderstanding to compare say KDE and blackbox of fluxbox or window maker. Why not with twm? Yes, Xfce may be well featured but is not out of box - one has to do some work.

I never had any real problems with KDE 4, except a few crashes a while back, and then and still, recently, a big gap in the panel when doing certain things. I don't know what causes that (I think it has to do with the window selector). It'll stay there until a window's closed. Strange, and it's been happening for a long time...
I'm sick and tired of KDE (3 and 4), and I'm going to stick with GNOME. I like it much more.

Slowly moving machines to KDE4. Currently have a laptop and a home server running KDE4 (although server only runs a graphical environment occasionally when it doubles as the home cinema machine). Soon to convert main home desktop machine to KDE4. Overall I think that the version of KDE4 that is supplied with Slack 13.1 is 90% ready and what is missing / buggy is not so bad as to make me rush of for the latest packages. I do play with XFCE more and more and might make this the default desktop for the server / home cinema PC, but KDE still seems better for a general purpose desktop with a lot of features well integrated.

Gnome uses inner format to save configuration information - it resembles me well-known HKEY_LOCAL_MACHINE - access for these data is similar difficult.

Strictly KDE4. I've been using it since 4.2. It's to the point where it's hands down the nicest looking desktop, it's easy to configure, and works well.

If I were still using KDE, I'd have to use KDE 3 right now, because I'm using Debian... but it probably won't be too long before Squeeze is released with 4.

I really liked KDE3. I've used KDE4 in 13.1 and it is excellent. However, I prefer using a WM/DE that runs a bit lighter. I've settled on XFce for most of my Slackware boxes, and Fluxbox for my oldest unit.

Yes, I get that "bleed through" in KDE 4.5.1. It can happen anywhere on the screen, but usually happens in the lower right-hand corner when a
"message box" pops up announcing whatever has just happened. The blank spot will stay until the box/window behind the bleed through is closed and re-opened.

@ midori webbrowser

Wow, I might as well be using links. At least then I wouldn't have to spend 10+ hours either setting up a virtual machine and compiling 32bit midori on my 64bit slackware or compiling it directly on the old computer. But if you have that kind of time to replace your webbrowser, then you have the time to compile KDE3.

@ KDE3 runs better on old hardware and updating your hardware every 6 months because of OS Changes.

Well KDE4 is rather new to Slackware and Slackware doesn't require hardware updates that often... I would say use 12.2 on all older hardware that's less than a 1gig ram and an i686. Anything that's 13+ should think of updating the hardware for another 3 to 5 years of solid Slacking with out updating any hardware.

@ Ranting
Not to mention. Slackware is so stable that you shouldn't need to worry about updating your OS anyway. The older laptop I have is intended only for text base documenting and minor web browsing. Honestly "links -g" from console works quite well. You can be quite productive with only console apps. Either way, I don't/never use(d) KDE. However, I thought the new plasma features were nice and would be extremely frustrated without k3b.

Wow, you could have grabbed webkit from AlienBOB's place.

I only grab VLC from there. Everything else deserves to be compiled, especially when webkit is still under heavy development. Either way, Midori is still not up to the task of every day browser. I've had problems with it doing 'submit' actions under Mantis and Egroupware which would lead me to believe that it has problems elsewhere. Hrmm either way, I only see webkitgtk on his repository which is 3mb bigger than compiled webkit. What if I want webkit from the source without the gtk bindings?

KDE4 is a big embarrassment for free open source software
I never thought slackware would sink to the level of windoze 95 but boy did it ever by including KDE 4.xx alpha over KDE 3.5 production

the one and only thing KDE 4.xx has over win95 is it dose not lock up the computer

I agree . . . the answer is "laziness." Code developers have always been lazy, but in the past ten years developers have given the word a new definition. Why? Because the extreme relative power of present-day systems allows them to be.

Heck . . . there are (thousands) of people out there who call themselves "computer programmers" who don't even know C, C++, or assembly. WOW.

There is no such thing as a streamlined, memory-efficient program or application written in C#, Java, or languages like that. They are, by their very nature, bloated, leaky hogs.

The KDE team develops in low-level languages, but they have always been fans writing resource-intensive programs. I remember running KDE 3 on a Pentium machine with 128 megs of RAM and deciding that it was just too hungry, then switching to Blackbox. As the power of my machine became greater, KDE 3 became manageable, but then KDE 4 came out and I'm using XFCE.

I'll tell you what, though, I'll never go back to KDE this time. It runs on my machine, and pretty well at that, but XFCE running with compiz looks almost just as good and runs easily twice as fast, using about 1/3 as much memory.

If this keeps happening, then try uncommenting the TerminateServer=true line in /etc/kde/kdm/kdmrc.

KDE3.5 is no longer maintained -- it has been abandoned by the KDE devs in favour of KDE4.x. For Slackware to include it would be foolish, as it is unlikely that it will be compilable in the future (due to changes in accompanying software), and if there are any bugs or security vulnerabilities discovered, they will not be fixed. There is the relatively new Trinity project that may show promise eventually, but it certainly doesn't have the backing of KDE4.x. KDE3.5 was compiled for Slackware 13.0 and lives on in unsupported (though I am not very confident that it would work in Slackware 13.1 or -current, and I'm not even confident that you could use the SlackBuilds to build it on 13.1 or -current).

I can understand frustration with KDE4.x, but to suggest that Pat should have continued to include an unmaintained KDE3.5 over an actively maintained KDE4.x (which represents the future of KDE) is foolish. Pat held off much longer than most other distros and stuck with KDE3.5 (when people were crying foul about Slackware not including KDE4.x), and I don't see any other options. I abandoned KDE when I upgraded from 12.2 to 13.0 (I liked KDE3.5, and though I don't despise KDE4.x, I don't particularly like it either). However, I am not silly enough to suggest any other possible options that just aren't practical. If you have a beef it should be with the KDE devs and not Pat in this instance...

1 members found this post helpful.