I have installed vnc server via the following command, following from this online guide

sudo apt-get install xfce4 xfce4-goodies tightvncserver

It seems that vnc server installation expects the file ~/.Xresources, which does not exist on my Ubuntu 16.04. The vnc log file says (observe the last log line):

> 17/08/17 21:24:15 Xvnc version TightVNC-1.3.10 17/08/17 21:24:15
> Copyright (C) 2000-2009 TightVNC Group 17/08/17 21:24:15 Copyright (C)
> 1999 AT&T Laboratories Cambridge 17/08/17 21:24:15 All Rights
> Reserved. 17/08/17 21:24:15 See http://www.tightvnc.com/ for
> information on TightVNC 17/08/17 21:24:15 Desktop name 'X' (matan:1)
> 17/08/17 21:24:15 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t,
> 3.8t 17/08/17 21:24:15 Listening for VNC connections on TCP port 5901 Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring Font
> directory '/usr/share/fonts/X11/100dpi/' not found - ignoring xrdb: No
> such file or directory xrdb: can't open file '/home/user/.Xresources'

The installation does leave a vnc process running (Xtightvnc), but I am unable to connect from a remote client. Is the above a real error/problem? or should I interpret that my vnc server is installed and running correctly?

My vnc clients (a local RealVNC client, and an iPad VNC app) fail to connect so I am unsettled on what my actual status is. They complain about authentication, but may probably fail for other reasons, I'd not trust their error messaging too much, given the vnc server log under .vnc doesn't show any signs of connection attempts!

Perhaps you'd also recommend a good procedure for confirming the server is properly working, for 16.04? maybe a vnc client that should work against the above vnc server out of the box?

People have suggested plainly using vino instead. Here is my vino configuration, and I've fiddled different ones too; my VNC clients over the same LAN fail to connect, and I'm unsure how to determine if vino is really operable on my Ubuntu desktop. Going down the path of enabling vino logging seems way too hacky to my taste.

enter image description here

  • I'd rather use Vino server (askubuntu.com/questions/4474/…). – Redbob Aug 17 '17 at 18:52
  • 2
    They have different purposes: if you are trying to relay an existing physical display (i.e. share your local desktop) then use vino (or x11vnc); if you're trying to run a separate remote X session, use xtightvnc. AFAIK the message about .Xresources is just informational. – steeldriver Aug 17 '17 at 18:59
  • 1
    Yeah, I'm using it in 16.04 and 17.04 too. It works the same way. There is another link: (askubuntu.com/questions/693634/…) – Redbob Aug 17 '17 at 18:59
  • 2
    I don't recommend connecting a VNC client to a desktop-sharing VNC server on the same machine to "locally verify" it - it will get very confusing ;) – steeldriver Aug 17 '17 at 19:16
  • 2
    Ideally you would attempt to connect from another machine on the same NAT'ed LAN - ideally you would not expose an unfiltered VNC port to the public internet. – steeldriver Aug 17 '17 at 19:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.