Difference between revisions of "Vino"

From ArchWiki
Jump to: navigation, search
(update link(s) (avoid redirect))
(update link(s) (avoid redirect))
Line 18: Line 18:
 
  $ gsettings set org.gnome.Vino require-encryption false
 
  $ gsettings set org.gnome.Vino require-encryption false
  
If you use a standalone [[Window Manager|window manager]] like [[Openbox]] and it doesn't work, you can start {{ic|vino-server}} manually or add the command to the window manager's autostart script
+
If you use a standalone [[Window manager|window manager]] like [[Openbox]] and it doesn't work, you can start {{ic|vino-server}} manually or add the command to the window manager's autostart script
 
   
 
   
 
  # /usr/lib/vino/vino-server &
 
  # /usr/lib/vino/vino-server &

Revision as of 11:17, 24 February 2014

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Vino#)

Vino is a VNC (Virtual Network Computing) server allowing remote connection to your actual desktop. It is a default component of the GNOME Desktop environment.

Installation

Install the package vino, which is available in the official repositories.

If you are running GNOME, you need to restart GNOME so that vino-server is started automatically when enabling the remote desktop feature.

Configuration

You can configure vino via gnome-control-center.

Now you can connect remotely to your desktop via a VNC viewer like TightVNC or Remmina. Remember to forward port 5900 if you are behind a NAT device and to allow the connection through iptables.

If you are having problems regarding security and encryption you could try:

$ gsettings set org.gnome.Vino require-encryption false

If you use a standalone window manager like Openbox and it doesn't work, you can start vino-server manually or add the command to the window manager's autostart script

# /usr/lib/vino/vino-server &