Linux Mint Forums

I installed a clean installation of Mint 17, with all suggested updates.
I am able to set under Preferences-Desktop Sharing my usual configuration settings. Sharing both are checked, Security only Required Password and Automatically config UPNP. And show notification icon only when someone is connected.

Unfortunately, when trying to remote in with Tightvnc viewer from windows 7. I get a "no security types supported".
I can see Vino-Server running using lsof -i :5900 and my fw port 5900 is open.

There is something strange going on with Mint 17 vs Mint 16. When using dconf editor on Mint 16 I can see under desktop-gnome-remote-access is listed there with options. Under Mint 17 using the dconf editor desktop-gnome-remote-access tree is completely MISSING altogether.

I can't get VNC to work. I guess I can look into installing tightvncserver.

try the following in a terminal:
gsettings set org.gnome.Vino require-encryption false

When I enter that I get the following:
dconf-WARNING **:failed to commit changes to dconf: The connection is closed

Combination of your vnc (tightvnc) and media service..
http://askubuntu.com/questions/408365/g ... pe-for-vnc
--you can check through the Tightvnc security settings, or change the programs you are using, one use on these posts had a combination that worked AOK (as stated by user post)..
X11VNC was the program the poster indicated worked OK

• I would be ignoring the Gnome nomenclature 3.xx, and only pay attention to the security support available within Tightvnc
• Also check the Vino security settings
  • --even if it happened that UPNC seemed to work at some point !
    https://help.ubuntu.com/community/VNC/Servers

Vino settings under desktop sharing are not reflective of the settings listed when performing "gsettings list-recursively org.gnome.Vino".

There is clearly something wrong with Vino. Using other vnc clients or doesn't work either.
Also if you download and install GConf configuration tool remote access is not listed under desktop/gnome/

I can't be the only one seeing this fault.

Remus 174, you are not the only one having this issue.

This is mildly disappointing. Remote desktop sharing is something that should work out of the box. I am not pointing the finger at Mint, the issue appears to lie elsewhere.

The easiest solution I have found is teamviewer (provided you are using it for personal use).

https://www.teamviewer.com/en/download/linux.aspx

This works for LMDE201403, but I see no reason why it would not work for 17:

OK, I managed to get Vino to work on LMDE201403.

vino-server is not enabled so we have to do that first:
Still, there is no easy way to configure vino, so we need to get dconf-Editor so we can configure it - install dconf-Editor with Synaptic.

Launch dconf-Editor and navigate to:

desktop.gnome.remote-access

Here you will be able apply the settings to vino like we used to see in previous versions when "vino-preferences" used to work. Password, encryption, notify on connection etc.

Finally, add to the Start Up Applications and you are done for good!

gsettings set org.gnome.Vino require-encryption false

This worked! I can now use VNC to control Mint 17 Mate.
I hope this issue will be resolved, although it may not be the fault of Mint. Being able to access Mint via VNC should happen right after installation.

Thanks!

I followed all the suggestions but turning off encryption that made vnc work for me. Many thanks. New install of 17 and vnc from 2nd 17 should work but didn't.

Thanks for the post. My VNC started accepting connections right away after the first setting suggestion above.

VNC is terrible and slow. I'm not trying to pick a fight, but if you actually want to USE remote capabilities:

Use MATE with Marco (not Compiz)

apt install xrdp tinyvncserver

init 6

Then you can remote in from another Mint with Remmina and actually have a usable desktop.