From FarmShare

Revision as of 15:34, 17 September 2014 (view source) Epoch (Talk | contribs) (→Resetting the shell configuration) ← Older edit		Revision as of 15:35, 17 September 2014 (view source) Epoch (Talk | contribs) (→Suggested default ~/.vnc/xstartup) Newer edit →
Line 18:		Line 18:
	mkdir ~/.vnc		mkdir ~/.vnc
	vncpasswd</pre>		vncpasswd</pre>
-
-	== Suggested default ~/.vnc/xstartup ==
-
-	If the default configuration is not working, try replacing the contents of ~/.vnc/xstartup with the following:
-	<pre>#!/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 &</pre>
-
-	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 [https://mailman.stanford.edu/mailman/swish?query=VNC&submit=Search+farmshare-discuss%21&metaname=swishdefault&sort=unixdate&listname=farmshare-discuss VNC].

---

Revision as of 15:35, 17 September 2014

Contents 1 Quota conditions 2 Authentication 3 Resetting the shell configuration 4 Resetting VNC state and configuration

Quota conditions

farmvnc may not start if you are over your AFS quota.

Authentication

Likewise, farmvnc may not start if you do not have a valid Kerberos ticket and AFS tokens. Try re-authenticating before running the command.

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. The default configuration for various shells is documented in Dotfiles.

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