VNC doesn't work after KDE 3.4 upgrade
 

Hi,

I have upgraded to 3.4 of KDE. When I try to connect to my machine in a web page like:

http://192.168.10.56:5801, I get a logon screen (before the KDE screen) from the VNC process. I go to login, it validates and instead of pulling up a KDE screen, I get a blank what appears like an X screen. I tried it on another system configuration and get the same results:

my hardware is:

PCX5750 albatron card
AMD 3000+ processor
1 gig memory

Like I say, it works in KDE 3.3, but fails after the upgrade. Any help would be appreciated.

Regards,

Randy.

Check your /home/xxxx/.vnc/xstartup file

There isn't one! Maybe this is the problem. In 3.3 it was all automatic. I would go into Yast and enable remote adminstration and it would work (I assume that was just opening up ports 5901, and 5801).

Which VNC product is Suse using (tightVNC, realVNC?).

Thank you for the help.

I'm not sure which vnc SuSE uses I'm on Mandrake and that uses tightvnc, you can create an xstartup by opening a console and typing: vncserver -geometry 800x600 (or whatever display size you want to use) then press enter, you will be notified which display vnc will use 1 or 2. Try again with your web browser or alternatively use Remote Desktop Connection.

Your suggestion worked. I did have to go into the startup file and take out:

xsetroot - sold grey

I also had to replace twm & with startkde &

The original 9.2 distribution must run this from root at leve 3 and instead of using startkde they somehow start the login splash screen for KDE. This would be a better solution then you don't have to login to start a process, it gets started in the startup sequence. I haven't figured out what to start yet for the login screen, or where to put it.

Randy.