Troubleshooting VNC
From FarmShare
Contents |
Quota conditions
vncserver may not start if you are over your AFS quota.
Authentication
Likewise, vncserver may not start if you do not have a valid Kerberos ticket and AFS tokens. Try re-authenticating before starting VNC.
kinit && aklog
Resetting the shell configuration
Some kinds of changes to ~/.cshrc and ~/.login (or other shell configuration files) may break VNC; in particular, setting up the environment for certain applications (e.g., Cadence) according to instructions is known to cause problems. You can restore the default shell configuration by running updaterc.
/usr/pubsw/bin/updaterc
Resetting VNC state and configuration
A common troubleshooting method is to reset the VNC configuration by deleting the ~/.vnc application directory.
rm -rf ~/.vnc mkdir ~/.vnc vncpasswd
Suggested default ~/.vnc/xstartup
If the default configuration is not working, try replacing the contents of ~/.vnc/xstartup with the following:
#!/bin/sh [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources vncconfig -iconic & /usr/bin/gnome-session & /usr/bin/gnome-terminal &
This configuration should provide something like the standard Ubuntu desktop with a single running instance of GNOME Terminal.
Search the farmshare-discuss archives for posts about VNC.
