Linked by Thom Holwerda on Thu 13th Oct 2011 21:33 UTC, submitted by mahmudinashar
Permalink for comment 493224
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2007-02-17
I can't think what you are doing wrong, it is beyond me. GNOME does include a number of work-arounds for parts of the kernel/driver stack that are supposed to work (but don't always). I don't believe that KDE does include kludges and work-arounds of this nature.
I, for example, have had no such trouble when running .x versions of KDE4 where x=2,4,6 or 7 (minor trouble with x=2 and 5), all on various different hardware configurations, using various different drivers, using various different distributions.
The minor trouble I did have with some versions of KDE4 was avoided either by disabling desktop effects, or using Xrender with desktop effects. Perhaps that may help in your case, but from your tone I doubt if you would think it worth your while to try. Such a pity, because KDE4 really does work very well indeed if the underlying kernel and drivers work.
I suppose this just re-enforces the point that in order for people to be able to use and enjoy an operating system on commodity hardware, it really must come pre-installed by the hardware vendor (as it is for Windows and OSX). Self-installed operating systems may fail in obscure ways (for any OS).
Edited 2011-10-16 22:28 UTC