Cannot configure the vino-server "security type" control

Bug #1412066 reported by Istimsak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vino (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I was setting up a testcase for gnome's vino server. Vino had to be tested to confirm it works at the basic level of vnc connection.

Packages installed: vino, xvnc4viewer

After installing vino and xvnc4viewer, in lubuntu, (xubuntu with lubuntu-desktop installed). The vino-server was started in Lubuntu 14.04 using this following command: /usr/lib/vino/vino-server &. This is the output of the following command.

(vino-server:16269): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-3lXPtqLo8q: Connection refused

(vino-server:16269): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion 'global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
17/01/2015 04:39:40 PM WARNING: Width (1366) is not a multiple of 4. VncViewer has problems with that.
17/01/2015 04:39:42 PM Autoprobing TCP port in (all) network interface
17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
17/01/2015 04:39:42 PM Autoprobing selected port 5900
17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
17/01/2015 04:39:42 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
17/01/2015 04:39:42 PM Clearing securityTypes
17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
17/01/2015 04:39:42 PM Clearing securityTypes
17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
17/01/2015 04:39:42 PM Advertising authentication type: 'No Authentication' (1)
17/01/2015 04:39:42 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900

I have read multiple tutorials outlining procedures to enable and connect to a vino-server. In all instructions, "ssh" was used to establish the connection. This is the form of the command to connect to a vino-server.

"ssh -L 12345:localhost:5900 username@ipaddress".

I tried testing vino on my own laptop by connecting to itself.

Whenever I performed the connection with or without ssh, I always get this output from the server:

17/01/2015 04:19:08 PM [IPv4] Got connection from client localhost
17/01/2015 04:19:08 PM other clients:
17/01/2015 04:19:09 PM WARNING: New width (1366) is not a multiple of 4.
17/01/2015 04:19:09 PM Client Protocol Version 3.7
17/01/2015 04:19:09 PM Advertising security type 18
17/01/2015 04:19:09 PM Client localhost gone
17/01/2015 04:19:09 PM Statistics:
17/01/2015 04:19:09 PM framebuffer updates 0, rectangles 0, bytes 0

This was after I used the command, ssh -L 12345:localhost:5900 username@ipaddress

I get this output after I typed xvnc4viewer from my local terminal:

 CConn: connected to host 172.29.24.129 port 5900
 CConnection: Server supports RFB protocol version 3.7
 CConnection: Using RFB protocol version 3.7
 CConnection: No matching security types
 main: No matching security types

It seems the problem is that I cannot establish a successful connection unless I am using the same security type. I could not find a way to configure the vino-server to change or remove the security type. There was no manpage for the vino-server. A manpage for the vino-server is needed, updated setup howto for all variants of ubuntu and an advanced configuration file for the vino-server to modify how it runs and behaves.

From QA member Istimsak Abdulbasir (sak)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vino 3.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CurrentDesktop: LXDE
Date: Sat Jan 17 17:01:18 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-09 (8 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
SourcePackage: vino
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Istimsak (saqman2060) wrote :
summary: - Cannot configure vino-server "security type"
+ Cannot configure the vino-server "security type" control
Istimsak (saqman2060)
affects: vino (Ubuntu) → ubuntu-manual-tests
affects: ubuntu-manual-tests → vino (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Revision history for this message
Istimsak (saqman2060) wrote : RE: [Bug 1412066] Re: Cannot configure the vino-server "security type"control
Download full text (5.3 KiB)

Should this be done for all bugs found on packages tested? How would I know if the bug is upstream and not related to the system it is installed on?

Do I keep file bugs to QA?

-----Original Message-----
From: "Sebastien Bacher" <email address hidden>
Sent: ‎1/‎22/‎2015 9:30 AM
To: "<email address hidden>" <email address hidden>
Subject: [Bug 1412066] Re: Cannot configure the vino-server "security type"control

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1412066

Title:
  Cannot configure the vino-server "security type" control

Status in vino package in Ubuntu:
  New

Bug description:
  I was setting up a testcase for gnome's vino server. Vino had to be
  tested to confirm it works at the basic level of vnc connection.

  Packages installed: vino, xvnc4viewer

  After installing vino and xvnc4viewer, in lubuntu, (xubuntu with
  lubuntu-desktop installed). The vino-server was started in Lubuntu
  14.04 using this following command: /usr/lib/vino/vino-server &. This
  is the output of the following command.

  (vino-server:16269): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-3lXPtqLo8q: Connection
  refused

  (vino-server:16269): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion 'global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
  17/01/2015 04:39:40 PM WARNING: Width (1366) is not a multiple of 4. VncViewer has problems with that.
  17/01/2015 04:39:42 PM Autoprobing TCP port in (all) network interface
  17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
  17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
  17/01/2015 04:39:42 PM Autoprobing selected port 5900
  17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
  17/01/2015 04:39:42 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
  17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
  17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
  17/01/2015 04:39:42 PM Clearing securityTypes
  17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
  17/01/2015 04:39:42 PM Clearing securityTypes
  17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
  17/01/2015 04:39:42 PM Advertising authentication type: 'No Authentication' (1)
  17/01/2015 04:39:42 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
  17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
  17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900

  I have read multiple tutorials outlining procedures to enable and
  connect to a vino-server. In all instructions, "ssh" was used to
  establish the connection. This is the form of...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Often bugs are in the upstream code and not the in distribution changes, there is no automatic way to figure where the issue is though. You are welcome to open bugs on launchpad if you prefer, it's just that e.g vino doesn't have anybody actively working on it in Ubuntu so you might have better chances to get issues resolved by talking directly to the software writers

Revision history for this message
Istimsak (saqman2060) wrote : Re: [Bug 1412066] Re: Cannot configure the vino-server "security type" control
Download full text (5.3 KiB)

Understood. I will follow your advice. I will continue to file bugs on
Launchpad sine it will make it easier for me to track them.
Thanks ;-)

On Thu, Jan 22, 2015 at 10:22 AM, Sebastien Bacher <email address hidden>
wrote:

> Often bugs are in the upstream code and not the in distribution changes,
> there is no automatic way to figure where the issue is though. You are
> welcome to open bugs on launchpad if you prefer, it's just that e.g vino
> doesn't have anybody actively working on it in Ubuntu so you might have
> better chances to get issues resolved by talking directly to the
> software writers
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1412066
>
> Title:
> Cannot configure the vino-server "security type" control
>
> Status in vino package in Ubuntu:
> New
>
> Bug description:
> I was setting up a testcase for gnome's vino server. Vino had to be
> tested to confirm it works at the basic level of vnc connection.
>
> Packages installed: vino, xvnc4viewer
>
> After installing vino and xvnc4viewer, in lubuntu, (xubuntu with
> lubuntu-desktop installed). The vino-server was started in Lubuntu
> 14.04 using this following command: /usr/lib/vino/vino-server &. This
> is the output of the following command.
>
> (vino-server:16269): WARNING **: Couldn't connect to accessibility
> bus: Failed to connect to socket /tmp/dbus-3lXPtqLo8q: Connection
> refused
>
> (vino-server:16269): EggSMClient-CRITICAL **: egg_sm_client_set_mode:
> assertion 'global_client == NULL || global_client_mode ==
> EGG_SM_CLIENT_MODE_DISABLED' failed
> 17/01/2015 04:39:40 PM WARNING: Width (1366) is not a multiple of 4.
> VncViewer has problems with that.
> 17/01/2015 04:39:42 PM Autoprobing TCP port in (all) network interface
> 17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
> 17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
> 17/01/2015 04:39:42 PM Autoprobing selected port 5900
> 17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
> 17/01/2015 04:39:42 PM Re-binding socket to listen for VNC connections
> on TCP port 5900 in (all) interface
> 17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
> 17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
> 17/01/2015 04:39:42 PM Clearing securityTypes
> 17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
> 17/01/2015 04:39:42 PM Clearing securityTypes
> 17/01/2015 04:39:42 PM Advertising security type: 'TLS' (18)
> 17/01/2015 04:39:42 PM Advertising authentication type: 'No
> Authentication' (1)
> 17/01/2015 04:39:42 PM Re-binding socket to listen for VNC connections
> on TCP port 5900 in (all) interface
> 17/01/2015 04:39:42 PM Listening IPv6://[::]:5900
> 17/01/2015 04:39:42 PM Listening IPv4://0.0.0.0:5900
>
> I have read multiple tutorials outlining procedures to enable and
> connect to a vino-server. In all instructions, "ssh" was used to
> establish the connection. This is the form of the command to connect
> to a vino-server.
>
> "ssh -L 12345:localhost:5900 username@ipaddress".
>
> I tried testing vino on my own laptop by connecting to itself.
>
> ...

Read more...

Istimsak (saqman2060)
Changed in vino (Ubuntu):
status: New → Incomplete
Revision history for this message
Kev Bowring (flocculant) wrote :

Has this been reported upstream?

Changed in vino (Ubuntu):
status: Incomplete → New
Revision history for this message
Istimsak (saqman2060) wrote :

No, that part of bug reporting I am not trained on

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in vino (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for vino (Ubuntu) because there has been no activity for 60 days.]

Changed in vino (Ubuntu):
status: Incomplete → Expired
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.