How can I connect to Gnome 3 with a Windows VNC client?
This is actually a known and currently open bug. However, there is a very easy workaround; just issue the following command:
gsettings set org.gnome.Vino require-encryption false
You will now be able to connect with most vnc viewers.
Here are some other possible solutions:
- Disable Vino encryption, and then setup an SSH tunnel
- Use a VNC client compatible with Vino's encryption (TLC): Android: bVNC Free, Windows: Java Turbo VNC client, Linux: vinagre
- Use a different VNC server, such as tigervnc or x11vnc
- Use a different VNC server, such as tightvnc, with a different desktop manager, such as MATE, Xfce, LXDE, etc.
Even 2.5 years later, this is still an issue with Fedora, Redhat, and Debian systems... Basically, Gnome 3 does a 3D graphics driver check when starting up gnome-session, which causes it to crash vncserver when NOT using Vino; so, use a different desktop manager. Alternatively, you use Vino, and then are required to either use Type 18 TLS and a handful of compatible VNC viewers, or turn off encryption and have all you traffic be easily sniffed; so, turn off encryption and use an SSH tunnel.
It's a convoluted problem that requires the coordination of multiple groups of developers to solve, and very little progress has been made.