I had forgotten to make xstartup excecutable. Doh.
Incidentally, vino looks like a better solution.
In normal situations, the use of "vino" to provide vnc access to the main desktop should be sufficient, and how to set this up is mentioned at the top of the kbase referenced at http://kbase.redhat.com/faq/docs/DOC-7097
Implementation of VNC control in Red Hat Enterprise Linux 5 has been greatly simplified with the introduction of vino, which is a VNC server for GNOME.
Installing the vino RPM creates a Remote Desktop menu item which is used to configure VNC access properties. It can be found in Red Hat Enterprise Linux 5 at System, Preferences, Remote Desktop. If vino is not installed on your system, you can install it with the command "yum install vino" (Red Hat Enterprise Linux 5) after registering the system with the Red Hat Network (http://rhn.redhat.com).
To enable remote desktop control, enable the "Allow other users to view your desktop" and "Allow other uses to control your desktop" items in Remote Desktop. We recommend using the "Require the user to enter this password" item as well to prevent unauthorized access to the X session. If you will be controlling unattended systems, be sure to remove the check from the "Ask you for confirmation" checkbox. Make a note of the vncviewer command that should be used to connect to this system, then click the Close button to save the settings and enable VNC.
The dialog box for vino also confirms the correct port to connect to, ie, 'server:1' is the same as server:5901.
Use of vino does -not- require the 'vncserver' service to be running, as it is handled by the 'vino-server' daemon, so you should disable the 'vncserver' service whilst trying to configure vino.
Lance Dryden wrote:
> Conor Wynne wrote:
>> Hi lads,
>>>> Poxy twm starts and I need gnome to work.
>> Surely this should work as is, what have I done wrong?
>>>> And no, I never use VNC :-)
>> Put "the right stuff" in an executable file "$VNCROOT/xstartup". For
> a typical user, $VNCROOT is probably == "$HOME/.vnc"
>> As an example, "the right stuff" in my case looks like:
>> --- BEGIN xstartup ---
>> xrdb /home/$USER/.Xdefaults
> # this line should be changed to something more appropriate
> # the following line, if uncommented, would kick kde on a Gentoo box
>> # the following line permits the entire Xvnc instance to terminate
> # properly after the WM dies
> vncserver -kill $DISPLAY
> --- END xstartup ---
>> Caveat: this is, as you might guess, from a Gentoo system running its
> build of VNC. I believe the standard realvnc source will honor the
> "xstartup" file but be watchful in case your distro does something
> unusual, or you are using a different VNC build.
>> Ath mhaith duit,
> Lance Dryden
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!