Remote access with SSH/TightVNC failed with new Kali 2.0

[kali2]

Hello,

I have a problem since the new Kali 2.0 with getting access to an installed TightVNC Server.
It seems to crash Gnome?

Description of working steps until Kali 1.1.0
# Connect to Kali with SSH
# Install TightVNC
sudo apt-get install tightvncserver
# Run VNC Server only localhost on Kali
sudo tightvncserver -localhost
# Set password before for remote access
# Tunnel a ThightVNC viewer over SSH to Kali and open i.e. 127.0.0.1:5901
It worked perfect until Kali 1.1.0 to get a "X Windows" which really helps sometimes for remote access.

If I am doing the same steps on Kali 2.0 and connect with the TightVNC viewer
I get a password prompt and then the TightVNC viewer opens with an error message
> Oh no! Something has gone wrong.

I have no idea why and how I can fix it.
Maybe a setting in /etc/init.d/gdm3 ?

I would really appreciate every help
or for an other solution to get access to the X.

Kind regards,
Sabi

[altkdub]

Same issue here - are we the only two running into this problem or the only two using vnc to get to a kali host?

[JKAD]

Same issue here, has anyone got vnc working?

[gedsic]

Same issue here, has anyone got vnc working?

I have, but it involves installing the MATE desktop environment, which is a GNOME 2 fork.

First, you have to install MATE:

$ sudo apt-get install mate-core mate-desktop-environment-extra mate-desktop-environment-extras mate-themes

Then, you have to change a line in the ~/.vnc/xstartup, replacing

/etc/X11/Xsession

with

/usr/bin/mate-session

It is just a workaround, as MATE offers a different look and feel than GNOME.

The underlying problems with GNOME and VNC (and RDP, NX, ...) are described here:

https://bugs.debian.org/cgi-bin/bugr...cgi?bug=776746
https://bugs.launchpad.net/ubuntu/+s...n/+bug/1251281

and it looks like a fix for Debian will take some time...

[mikewitney]

great thanks the workaround is great

[slaxd]

ok just a thought guys but i recently found that mikogo works well with kali gnome - the interesting thing is mikogo seems to be based on vnc protocols so the million dollar question is why does mikogo vnc work but sana/debian does not ??