This list is being updated regularly, so, particularly as you are reading
a mirrored copy, it's worth checking the
original from time to time. The archives
of the mailing list are also available, and
they can be a good source of help - try searching them here.
- My X VNC server is working, but I don't see my normal environment. How can I change the Window manager etc?
- The window manager is started by the ~/.vnc/xstartup script. We use
twm, as this is available on almost all Unix platforms. Edit the
script if you'd rather replace it with something else. On many platforms
you can, as an alternative, just make xstartup a link to whatever script
normally starts your X environment.
If you want to be more sophisticated, you can specify the -name option
to vncserver, and then take different actions in the xstartup script based
on the name given. For example:
case "$VNCDESKTOP" in
kde)
startkde &
;;
*)
xterm -geometry 40x10+40+40 -ls -title "$VNCDESKTOP Desktop" &
twm &
;;
esac
-
Why can I only run vncserver/Xvnc as root?
- The most likely reason for this is that Xvnc can't
create the unix domain socket (the path for this unix domain socket is
usually /tmp/.X11-unix/Xn). Try making sure that users can write
to this directory by making it world-writable, i.e.
chmod 01777 /tmp/.X11-unix
An alternative is to set the Xvnc binary to have the same
permissions as your normal X server, but this may be more of a security
risk.
-
Can I remote the normal X display of my workstation (display :0) in
the same way as the Windows server does?
- It would be possible to add VNC support to a standard
X server, so that it operated this way, but we have no plans to do so.
It shouldn't be too difficult, if you have the full source code for your
X server. Xvnc is basically XFree86 with the hardware-dependent bits
taken out and VNC put in their place, so it doesn't have drivers for any
graphics cards. You could have a look at the Xvnc source code to see which
bits have been added to the standard XFree86, and make the equivalent changes
on your X server.
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, available from the contribs page.
-
What X Visual does Xvnc use?
- By default, vncserver will start Xvnc with the same
depth as the current X display, if there is one, or 8 bits deep if there
isn't. We've tried to steer clear of colour maps as much as possible
and normally use "true colour", even when there are only 8 bits per pixel.
- Unfortunately some X applications don't cope too well
with an 8 bit TrueColor visual. You can make Xvnc use the more
normal PseudoColor visual by giving a "-cc 3" option to vncserver.
-
Can I cut and paste between the viewer and the server?
- VNC supports copying and pasting of ASCII text in both
directions, provided the viewer and server allow it. When the clipboard
changes on the machine running the viewer, the changes are copied to the
server and vice versa. Some notable exceptions:
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it
- The code to do copying from the X server to
the viewer didn't make it in the original version 3.3.2. It's back
in 3.3.2R2 and later, so upgrade if you haven't already!
-
There's a memory leak in Xvnc!
- This is fixed in versions 3.3.2r3 and later. If you're using an older
distribution you can find a patch for it