bug in kde2 kills vnc

[gring00]

There is a known bug in kde 2.1.1 that means one cannot connect to your desktop using vnc (in mandrake at least), either the mandrake rpm or the gzipped source (afaik).
Solution for the moment is to use another window manager/desktop . I've gone with gnome. You can get this to work by editing your ~./vnc/xstartup file and replacing (the default) last line with exec gnome-session&

This worked for me at least.

And now, finally for some tribes.

:)

[Slime]

Is VNC any good ?

[Skunk]

VNC is great - I've just started using it as work to allow me to use one monitor for my linux and windows boxes and it works a treat :)

[Slime]

Skunk,

I've been playing around with VNC today...and it looks very handy (previously only used Timbuktu which is similair but not as multi-platform).

Only problem i found was that i ended up with the default tvm windows manager. I (naively) expected to see the KDE desktop. I found the config file that starts when you run VNC (which referenced tvm as the wm to start), but didn't seem to have a lot of luck changing it.

Ideally i'd like to be prompted with my nice graphical login screen that i get when i boot into Mandrake (i.e. which user do you want ot login as and what Window manager would you like to use). Or (probably even better) just be put into the Windows Manager currently in use on the box (i.e. share the desktop with the actual box - just liike you have to do if you conneect to a Windows box).

Can i set it up so that the VNC user effectively has a windows manager to himself and/or what happens when you initiially connect into your box via VNC ?

Cheers
Slime

[Skunk]

I've had the same problem, in that the session I set up for myself just logged into my currently sactive desktop, but when I tried to spawn a session for someone else's account it loaded X-Windows but didn't load any windows manager at all!

Still haven't figured that one out yet :|

[Slime]

Ta anyways - i'll keep playing with it and post back if i get any further.

Cheers
Slime

[Slime]

Aha - to answer 1 part of my original question :-

Q22 Can I remote the normal X display of my workstation (display :0) in the same way as the Windows server does?

It is possible to add VNC support to a standard X server, but we have no plans to do so at the moment. We've been told that Jens Wagner has done this - see x0rfbserver. We tend to run all our X sessions as VNC sessions and only use the local X server to run the viewer. It's very fast when on the same machine as the server! If you feel that it's overkill to run two X servers on the same machine, you might consider Ganesh Varadarajan's svgalib-based viewer.

This is from the VNC FAQ. (http://www.uk.research.att.com/vnc/faq.html#q12)

So - you can't normally just connect to the "in-use" desktop displayed when you're sitting on the server - but you actually run another instance of X. Which is better anyway :)

However, i'm still struggling to make my damn connection default into a KDE desktop :(

Cheers
Slime

[gring00]

Slime, what problems are you having changing the .xvncserver (I think thats the config file) ? The last line by default reads:
tvm&

Just remove this line (dd in vi : ) ) and insert startkde& , and then save the file.
exec gnome-session& uses gnome istead btw.

Note, you must be logged on as the user that created the file, so if you were root when you first ran vncserver :1 (this being the display you want to run vnc on) then you will need to edit the file as root, as that is the user that owns the config file. Once you've written the file you'll need to use vncserver to kill vnc and then restart it to use the new settings.
vncserver -kill :1 (kills is, strangely enough)
vncserver :1 (restarts it with new settings).

Then reconnect using the vncviewer , and Bobs your aunties live in lover!

hth

[Slime]

:rolleyes: thanks mate - i'll start playing with 'me penguin again.

Cheers
Slime