1

There are two issues here:

a) It is not intuitive how to run KDE over vnc.

It used to be, in KDE 3.5, that we add startkde& in xstartup. Today, there seems to be like 20 steps to get this to work.

Look at post number 68 on this page: http://ubuntuforums.org/showthread.php?t=259448&page=7 lists the steps that people have figured out are required to get this to work.

I think it is unreasonable to expect people to have to do all those steps to get this to work. This should really work "out of the box".

b) KDE4 looks _awful_ over VNC
There are many many forum threads that state that KDE4 looks awful over VNC.

For example:
1) viewtopic.php?f=16&t=16651
2) http://ubuntuforums.org/showthread.php?t=993321
3) viewtopic.php?f=15&t=88532

Google lists many more threads on this topic.

To summarize, today we have a situation where people have to do a bunch of obscure steps to get an unusable VNC experience on KDE4.

I think KDE is losing out on a lot of (remote desktop) markets by not concentrating on getting KDE4 work over VNC. There are many development environments where operating systems are run in the cloud, and people just VNC into their sessions. KDE4 is not usable in those environments.

The main kicker here is that this used to work, and still works flawlessly in KDE3.

tia,
rouble

There are already lots of bug reports about this.