Somebody actually made VNC work with the Nano?

Hi have tried different VNC servers, and different procedures I have found searching on-line, and best I got was a black screen where I could open terminals, but dock and top bar were missing.

Does somebody have a link at hand to a procedure that s/he tried and that worked? Whether it uses the Gnome desktop, or a different one.

Try this. Install “x11vnc”:

$ sudo apt-get install x11vnc

Manually start the vnc server by:

$ x11vnc -forever -shared

By default, the server listens to port 5900.

x11vnc turned out to be better than all I tried before. Thank you.

I added

/usr/bin/x11vnc -shared -forever -ncache 10 -rfbauth /home/jetbot/.vnc/passwd -display WAIT: -o /home/jetbot/.vnc/stderr.txt

to the Startup Applications Preferences.

It is not completely satisfactory, as it is less responsive than REALVNC on a Raspberry Pi 4 (in spite of the Jetbot being connected via Ethernet, and the Pi 4 via WiFi), even in MAXN power mode (4 cores).

Also, “Paste” in the right-click menu is always disabled, and trying to select “Copy” from the same may end the VNC server itself. Finally, if there is no display connected, VNC starts at a lower and fixed resolution. To solve the latter quickly, I have plugged a 10 EUR dongle in the HDMI port, which pretends to be a display. It will have to make do for the time being.

with this command I get this output

###############################################################
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@ @#
#@ ** WARNING ** WARNING ** WARNING ** WARNING ** @#
#@ @#
#@ YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!! @#
#@ @#
#@ This means anyone with network access to this computer @#
#@ may be able to view and control your desktop. @#
#@ @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@ @#
#@ You can create an x11vnc password file by running: @#
#@ @#
#@ x11vnc -storepasswd password /path/to/passfile @#
#@ or x11vnc -storepasswd /path/to/passfile @#
#@ or x11vnc -storepasswd @#
#@ @#
#@ (the last one will use ~/.vnc/passwd) @#
#@ @#
#@ and then starting x11vnc via: @#
#@ @#
#@ x11vnc -rfbauth /path/to/passfile @#
#@ @#
#@ an existing ~/.vnc/passwd file from another VNC @#
#@ application will work fine too. @#
#@ @#
#@ You can also use the -passwdfile or -passwd options. @#
#@ (note -passwd is unsafe if local users are not trusted) @#
#@ @#
#@ Make sure any -rfbauth and -passwdfile password files @#
#@ cannot be read by untrusted users. @#
#@ @#
#@ Use x11vnc -usepw to automatically use your @#
#@ ~/.vnc/passwd or ~/.vnc/passwdfile password files. @#
#@ (and prompt you to create ~/.vnc/passwd if neither @#
#@ file exists.) Under -usepw, x11vnc will exit if it @#
#@ cannot find a password to use. @#
#@ @#
#@ @#
#@ Even with a password, the subsequent VNC traffic is @#
#@ sent in the clear. Consider tunnelling via ssh(1): @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/#tunnelling @#
#@ @#
#@ Or using the x11vnc SSL options: -ssl and -stunnel @#
#@ @#
#@ Please Read the documention for more info about @#
#@ passwords, security, and encryption. @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/faq.html#faq-passwd @#
#@ @#
#@ To disable this warning use the -nopw option, or put @#
#@ ‘nopw’ on a line in your ~/.x11vncrc file. @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
###############################################################
21/07/2020 02:07:08 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 13133
21/07/2020 02:07:08 XOpenDisplay("") failed.
21/07/2020 02:07:08 Trying again with XAUTHLOCALHOSTNAME=localhost …
21/07/2020 02:07:08
21/07/2020 02:07:08 *** XOpenDisplay failed. No -display or DISPLAY.
21/07/2020 02:07:08 *** Trying “:0” in 4 seconds. Press Ctrl-C to abort.
21/07/2020 02:07:08 *** 1 2 3 4
No protocol specified
21/07/2020 02:07:12 XOpenDisplay(":0") failed.
21/07/2020 02:07:12 Trying again with XAUTHLOCALHOSTNAME=localhost …
No protocol specified
21/07/2020 02:07:12 XOpenDisplay(":0") failed.
21/07/2020 02:07:12 Trying again with unset XAUTHLOCALHOSTNAME …
No protocol specified
21/07/2020 02:07:12

21/07/2020 02:07:12 ***************************************
21/07/2020 02:07:12 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: “:0”, it cannot continue.
*** There may be “Xlib:” error messages above with details about the failure.

Some tips and guidelines:

** An X server (the one you wish to view) must be running before x11vnc is
started: x11vnc does not start the X server. (however, see the -create
option if that is what you really want).

** You must use -display , -OR- set and export your $DISPLAY
environment variable to refer to the display of the desired X server.

  • Usually the display is simply “:0” (in fact x11vnc uses this if you forget
    to specify it), but in some multi-user situations it could be “:1”, “:2”,
    or even “:137”. Ask your administrator or a guru if you are having
    difficulty determining what your X DISPLAY is.

** Next, you need to have sufficient permissions (Xauthority)
to connect to the X DISPLAY. Here are some Tips:

  • Often, you just need to run x11vnc as the user logged into the X session.
    So make sure to be that user when you type x11vnc.
  • Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
    file may be accessed. The cookie file contains the secret key that
    allows x11vnc to connect to the desired X DISPLAY.
  • You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
    by the -auth option, e.g.:
    x11vnc -auth /home/someuser/.Xauthority -display :0
    x11vnc -auth /tmp/.gdmzndVlR -display :0
    you must have read permission for the auth file.
    See also ‘-auth guess’ and ‘-findauth’ discussed below.

** If NO ONE is logged into an X session yet, but there is a greeter login
program like “gdm”, “kdm”, “xdm”, or “dtlogin” running, you will need
to find and use the raw display manager MIT-MAGIC-COOKIE file.
Some examples for various display managers:

 gdm:     -auth /var/gdm/:0.Xauth
          -auth /var/lib/gdm/:0.Xauth
 kdm:     -auth /var/lib/kdm/A:0-crWk72
          -auth /var/run/xauth/A:0-crWk72
 xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
 dtlogin: -auth /var/dt/A:0-UgaaXa

Sometimes the command “ps wwwwaux | grep auth” can reveal the file location.

Starting with x11vnc 0.9.9 you can have it try to guess by using:

          -auth guess

(see also the x11vnc -findauth option.)

Only root will have read permission for the file, and so x11vnc must be run
as root (or copy it). The random characters in the filenames will of course
change and the directory the cookie file resides in is system dependent.

See also: http://www.karlrunge.com/x11vnc/faq.html