fine until a certain moment when the connection is used over serveral days (also using KDE programs). Then suddenly the server crashes and I have to delete some temporary files from /tmp: ".X101-lock" and ".X11-unix". then the server has to be restarted. Is this a known problem ? Has anyone got an idea how to fix this? Does the vnc process have too little memory assigned? Fresh install of Ubuntu 10.04 - first thing I did was install tightvncserver as above (great piece, thank you). Logging in with TightVNC I was surprised to see the user was "root". Scared the crap out of me. Best guess is the first time I ran the script (that creates the .vnc directory and password file) I must have typed "sudo". Reasoning: ownership of ~/.vnc and ~/.Xauthority was root:root. Fixed it by changing the permissions of ~/.vnc and ~/.vnc/passwd, deleting the .Xauthority files, deleting the ~/.vnc/server:1.log and server:1.pid files; stopped the service, then reran the startup script. Still confused on the difference between running "/etc/init.d/vncserver start" and simply "vncserver". Everything mentioned here also works on Ubuntu 10.04. Knowing little about bash scripting I got my set up with multiple VNC servers for multiple users working by using the last script on the page here . with just one small change. Changed /bin/sh to /bin/bash. This is because in ubuntu the default shell is not bash thus requiring you to be expllicit. My guess would be that the VNC session is started, but no programs