Questions[tightvncserver](ubuntu)

I have been trying to get any vnc setup to work for me.. that issue is posted elsewhere.. but one issue in particular now has come up..

I installed and removed tigervnc, but now tightvncserver complains it cannot startup... how do I create a new xvnc-session?

inside myxvncserver:1.log

13/05/20 10:46:40 Xvnc version TightVNC-1.3.10
13/05/20 10:46:40 Copyright (C) 2000-2009 TightVNC Group
13/05/20 10:46:40 Copyright (C) 1999 AT&T Laboratories Cambridge
13/05/20 10:46:40 All Rights Reserved.
13/05/20 10:46:40 See http://www.tightvnc.com/ for information on TightVNC
13/05/20 10:46:40 Desktop name 'X' (2600k:1)
13/05/20 10:46:40 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
13/05/20 10:46:40 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
/etc/X11/Xvnc-session: 6: vncconfig: not found
Killing Xtightvnc process ID 17651
~                                                                                                                                                               
~                                                                                                                                                               
~ 

I searched elsewhere and someone states "oh just get a new xvnc-session" since tigervnc apparently deletes it (thanks tigervnc)

how do I fix this, so I can connect to ubuntu 20.04 via my mac?

I've been struggling with the gray screen problem of tightvncserver on ubuntu 18.04 and gnome

• The problem is the same with both aws ec2 as well as my local machine.
• I've verified that xfcestartup4 works well with tightvnc

Can somebody please clarify once and for all how to make tightvnc work with gnome on ubuntu 18.04?

This is my ~/.vnc/xstartup

#!/bin/bash
export XKL_XMODMAP_DISABLE=1
# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
#exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
#startxfce4 &
#x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#x-window-manager &
gnome-session &
gnome-panel &
gnome-settings-daemon &
metacity &
nautilus &
gnome-terminal &

I've tried a lot of things but none of them work:

• uncommenting #exec /etc/X11/xinit/xinitrc
• using sh after exec
• using only gnome-session &
• tried without the ampersand

Please help. Most of the tutorial seems to imply it should work out of the box, but this is utterly not true? Is tightvncserver broken with gnome3?

I have successfully installed WLS (ubuntu 18) on windows 10 machine. I want to access its UI features using TightVnc. With default settings the .vnc/xstartup contains the following lines

xrdb $HOME/.Xresources
xsetroot -solid grey
#x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#x-window-manager &
# Fix to make GNOME work
export XKL_XMODMAP_DISABLE=1
/etc/X11/Xsession

and I can connect to it using Tight vnc viewer from windows but the UI looks like But, I want to use the default desktop that ships with Ubuntu 18. I installed gnome and changed xstartup file to the following (suggested by someone on the web)

#!/bin/sh

#Uncommment this line if using Gnome and your keyboard mappings are incorrect.
#export XKL_XMODMAP_DISABLE=1

# Load X resources (if any)
if [ -r "$HOME/.Xresources" ]
then
        xrdb "$HOME/.Xresources"
fi

gnome-session --disable-acceleration-check --session=ubuntu &

But when I start vncserver after making these changes, I am able to connect but it shows a grey screen with no visual controls like Please note that I had no .Xresources file on my machine so I created an empty one manually but it made no difference. Below is the output of ls /usr/share/xsessions

ubuntu-communitheme-snap.desktop  ubuntu.desktop  xfce.desktop

I can see some errors in .vnc/CS-63341DT:5.log file. Below are the contents of this file

05/04/19 12:49:17 Xvnc version TightVNC-1.3.10
05/04/19 12:49:17 Copyright (C) 2000-2009 TightVNC Group
05/04/19 12:49:17 Copyright (C) 1999 AT&T Laboratories Cambridge
05/04/19 12:49:17 All Rights Reserved.
05/04/19 12:49:17 See http://www.tightvnc.com/ for information on TightVNC
05/04/19 12:49:17 Desktop name 'X' (CS-63341DT:5)
05/04/19 12:49:17 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
05/04/19 12:49:17 Listening for VNC connections on TCP port 5905
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
gnome-session-binary[1645]: WARNING: Using null backend for session tracking
_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
GNOME_KEYRING_CONTROL=/home/adeel/.cache/keyring-FKBRZZ
GNOME_KEYRING_CONTROL=/home/adeel/.cache/keyring-FKBRZZ
GNOME_KEYRING_CONTROL=/home/adeel/.cache/keyring-FKBRZZ
SSH_AUTH_SOCK=/home/adeel/.cache/keyring-FKBRZZ/ssh
Window manager warning: Unsupported session type
gnome-session-binary[1645]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Window manager warning: Unsupported session type
gnome-session-binary[1645]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
gnome-session-binary[1645]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
gnome-session-binary[1645]: CRITICAL: We failed, but the fail whale is dead. Sorry....

What can I do to make default ubuntu 18 deskto work with TightVnc viewer from windows?

On Ubuntu 18.04 I ran sudo apt-get install tightvncserver. I then run vncserver which gives

New 'X' desktop is user:1

Starting applications specified in /etc/X11/Xvnc-session
Log file is /home/user/.vnc/user:1.log

as output. When I run more /home/user/.vnc/user:1.log I get

23/10/18 00:27:27 Xvnc version TightVNC-1.3.10
23/10/18 00:27:27 Copyright (C) 2000-2009 TightVNC Group
23/10/18 00:27:27 Copyright (C) 1999 AT&T Laboratories Cambridge
23/10/18 00:27:27 All Rights Reserved.
23/10/18 00:27:27 See http://www.tightvnc.com/ for information on TightVNC
23/10/18 00:27:27 Desktop name 'X' (user:1)
23/10/18 00:27:27 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
23/10/18 00:27:27 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
No VNC extension on display :1
Killing Xtightvnc process ID 5196

I have no idea on how to resolve this issue and cannot find anything on No VNC extension on display :1.

I've been using VNC for many years but I don't know why this happens sometimes. With a new Ubuntu 16.04 machine, I first tried using Vino. It worked well, but I decided it is rather slow, so I decided to use TightVNC with the Xfce4 window manger. However I get this "grey screen" (I have experienced it before couple of times..) again.
My xstartup is :

#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
startxfce4 &

and the log file is :

24/08/18 09:47:09 Xvnc version TightVNC-1.3.10
24/08/18 09:47:09 Copyright (C) 2000-2009 TightVNC Group
24/08/18 09:47:09 Copyright (C) 1999 AT&T Laboratories Cambridge
24/08/18 09:47:09 All Rights Reserved.
24/08/18 09:47:09 See http://www.tightvnc.com/ for information on TightVNC
24/08/18 09:47:09 Desktop name 'X' (kimchan:1)
24/08/18 09:47:09 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
24/08/18 09:47:09 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
/usr/bin/startxfce4: X server already running on display :1
Xlib:  extension "RANDR" missing on display ":1".
xfce4-session: Another session manager is already running

24/08/18 09:48:08 Got connection from client 129.254.132.39
24/08/18 09:48:08 Using protocol version 3.8
24/08/18 09:48:12 Full-control authentication passed by 129.254.132.39
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 16
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 22
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 21
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 15
24/08/18 09:48:12 Using zlib encoding for client 129.254.132.39
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding -314
24/08/18 09:48:12 Enabling full-color cursor updates for client 129.254.132.39
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding -223
24/08/18 09:48:12 Pixel format for client 129.254.132.39:
24/08/18 09:48:12   32 bpp, depth 24, little endian
24/08/18 09:48:12   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
24/08/18 09:48:12   no translation needed
24/08/18 09:48:12 Using raw encoding for client 129.254.132.39
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 22
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 21
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 16
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 15
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding -314
24/08/18 09:48:12 Enabling full-color cursor updates for client 129.254.132.39
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding -223
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 16
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 22
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 21
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding 15
24/08/18 09:48:12 Using zlib encoding for client 129.254.132.39
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding -314
24/08/18 09:48:12 Enabling full-color cursor updates for client 129.254.132.39
24/08/18 09:48:12 rfbProcessClientNormalMessage: ignoring unknown encoding -223

What is wrong here? Is X server already running on display :1 an error? And how about "RANDR" missing on display:1? And what are those many ignoring unknown encoding messages?