i have not used vino before, but if you want to connect using VNC only, i've written a tutorial on how to set up such a configuration in Ubuntu 12.04 and Linut MINT 13:http://www.matrix44.net/blog/?p=1106
Essentially, you have to run x11vnc with a few parameters from your /etc/mdm/Init/Default script. Put the following line at the end (before exit 0) of the mentioned file:
- Code: Select all
nohup x11vnc -shared -no6 -forever -nolookup -auth /var/lib/mdm/:0.Xauth --passwd 'Test123!' 2>/dev/null 1>&2 &
(You'll need to install the x11vnc package)
This is a major improvement over vino-server. I used the code you suggested with two changes:
- Code: Select all
nohup x11vnc -repeat -shared -no6 -forever -nolookup -auth /var/lib/mdm/:0.Xauth --passwdfile '/home/martywd/.vncpass' 2> /dev/null 1>&2 &
The '-repeat' switch because after reboot and remote VNC login, the server machine's keyboard autorepeat key functionality nolonger worked until I was able to physically sit at the machine and log off and log back on again. Adding the '-repeat' switch seems to have solved this issue.
Replacing the '--passwd' switch and cleartext password (easily seen by other local users by running 'ps' from terminal) with: '--passwdfile' , creating a file containing the VNC password with owner access only (rw) permissions (chmod 600) helps to prevent other users on the machine from viewing the password used in the VNC login.
Lot's of help available via 'man x11vnc'.
vino-server was a fight from the start to get working on my LM13 MATE (32-bit) machine. And after a remote reboot, none of the other suggestions posted on the LM forum and on the U...forum worked for me to get vino-server running again until I could physically sit at the machine and login. Again, this 'x11vnc' server config option is a vast improvement.