upgrade removes "encryption required" but doesn't update config

Bug #369181 reported by Shahar Or
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
vino (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

-- UPDATED DESCRIPTION --
If a user had the "Require encryption" set in intrepid and he upgraded to jaunty he couldn't set it back off without gconf-editor.

This is because the option is no longer there.

This makes it impossible in this case to connect to Vino using anything but Vinagre.
-- END UPDATED DESCRIPTION --

Binary package hint: vino

Dear friends,

I can't seem to connect to Vino using xvnc4viewer. Please look:

--- snip ---
dawn@dawn-desktop:~$ xvnc4viewer -log *:stdout:100 localhost

VNC Viewer Free Edition 4.1.1 for X - built Apr 16 2008 13:02:40
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Wed Apr 29 14:30:40 2009
 CConn: connected to host localhost port 5900
 CConnection: reading protocol version
 CConnection: Server supports RFB protocol version 3.7
 CConnection: Using RFB protocol version 3.7

Wed Apr 29 14:30:41 2009
 CConnection: processing security types message
 CConnection: Server offers security type [unknown secType](18)
 CConnection: No matching security types
 main: No matching security types
dawn@dawn-desktop:~$
--- snip ---

Attached are the Vino settings.

Many blessings.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: vino 2.26.1-0ubuntu1
ProcEnviron:
 LANG=he_IL.UTF-8
 SHELL=/bin/bash
SourcePackage: vino
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
Shahar Or (mightyiam) wrote :
Revision history for this message
Shahar Or (mightyiam) wrote :

Dear friends,

xtightvncviewer also can't connect to Vino for the same reason.

--- snip ---
dawn@dawn-desktop:~$ xtightvncviewer localhost
Connected to RFB server, using protocol version 3.7
Server did not offer supported security type
dawn@dawn-desktop:~$
---snip ---

Many blessings.

summary: - xvnc4viewer can't connect to Vino
+ Clients other than Vinagre can't connect to Vino
Revision history for this message
Shahar Or (mightyiam) wrote : Re: Clients other than Vinagre can't connect to Vino

When I try with grdc it gives me "Unknown authentication scheme from VNC server: -1215770256"

Revision history for this message
tinahouse (tinahouse) wrote :

Seems I can't connect only when Vino encryption is set to require. Not sure what this encryption mean, maybe a special extension that only work between vinagre and vino?

Revision history for this message
Shahar Or (mightyiam) wrote :

Dear tinahouse,

You're right. That's the problem.

So there's a little bug here. I'm changing the description.

Many blessings.

Shahar Or (mightyiam)
description: updated
summary: - Clients other than Vinagre can't connect to Vino
+ upgrade removes "encryption required" but doesn't update config
Revision history for this message
Nikolay Botev (nikolaybotevb) wrote :

Here is the workaround for this bug:

For those who are stuck in the same problem as me (encryption enabled in Gutsy/Intrepid, and cannot disable after Jaunty upgrade), here are the steps:

1. Open a Terminal (Applications -> Accessories -> Terminal)
2. Type gconf-editor and press Enter
3. Navigate in the tree pane of the Configuration Editor to:

/desktop/gnome/remote_access

4. Uncheck the "require_encryption" option.
5. Logout and log back in or restart.

That's it. Hope that helps somebody

Changed in vino (Ubuntu):
importance: Undecided → Low
Revision history for this message
tinahouse (tinahouse) wrote :

The latest Grdc, now called Remmina, can connect to vino, even require_encryption is set to true.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in vino (Ubuntu):
status: New → Confirmed
Revision history for this message
sacarde (sacarde) wrote :

con you show me how set "require_encryption" to false
in ubuntu-1404 ?

thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.