Bug 1319511 - Vino displays random previous screen images to the cconnecting client
Summary: Vino displays random previous screen images to the cconnecting client
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: vino
Version: 23
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-20 20:05 UTC by Jerry LeVan
Modified: 2016-12-20 19:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 19:32:14 UTC
Type: Bug


Attachments (Terms of Use)

Description Jerry LeVan 2016-03-20 20:05:30 UTC
Description of problem:
Connecting to vino-server on port 5900 via MacOSX, iOS, Fedora 23 (a VM on my Mac) causes older screens from the target Fedora System to be randomly displayed
on the connecting machine.

Version-Release number of selected component (if applicable):
vino-3.18.1-1.fc23.x86_64

How reproducible:
Every time I connect to the Fedora 23 machine from my Mac, iOS, or FedoraVM
using a variety of clients I get the bad behavior

Steps to Reproduce:
1.Start a VNC connection from any of my machines ( Mac Screen Sharing, RealVNc,
  Chicken of the VNC....
2.
3.

Actual results: 
Older screen images from the target Fedora box randomly start appearing
on the client machine, It is not possible to do work via the connection.



Expected results:
A stable connection displaying the screen on the target machine and the
ability to do work on the target machine,


Additional info:
The tiger vnc-server does not have this problem but one does not get the
active desktop.

Here is a part of the vino-server log:
[jerry@bigbox ~]$ /usr/libexec/vino-server
20/03/2016 02:36:40 PM Autoprobing TCP port in (all) network interface
20/03/2016 02:36:40 PM Listening IPv6://[::]:5900
20/03/2016 02:36:40 PM Listening IPv4://0.0.0.0:5900
20/03/2016 02:36:40 PM Autoprobing selected port 5900
20/03/2016 02:36:40 PM Advertising security type: 'TLS' (18)
20/03/2016 02:36:40 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
20/03/2016 02:36:40 PM Listening IPv6://[::]:5900
20/03/2016 02:36:40 PM Listening IPv4://0.0.0.0:5900
20/03/2016 02:36:40 PM Clearing securityTypes
20/03/2016 02:36:40 PM Advertising security type: 'TLS' (18)
20/03/2016 02:36:40 PM Clearing securityTypes
20/03/2016 02:36:40 PM Advertising security type: 'TLS' (18)
20/03/2016 02:36:40 PM Advertising authentication type: 'No Authentication' (1)
20/03/2016 02:36:40 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface
20/03/2016 02:36:40 PM Listening IPv6://[::]:5900
20/03/2016 02:36:40 PM Listening IPv4://0.0.0.0:5900
20/03/2016 02:36:40 PM Clearing securityTypes
20/03/2016 02:36:40 PM Clearing authTypes
20/03/2016 02:36:40 PM Advertising security type: 'TLS' (18)
20/03/2016 02:36:40 PM Advertising authentication type: 'VNC Authentication' (2)
20/03/2016 02:36:40 PM Clearing securityTypes
20/03/2016 02:36:40 PM Clearing authTypes
20/03/2016 02:36:40 PM Advertising security type: 'TLS' (18)
20/03/2016 02:36:40 PM Advertising authentication type: 'VNC Authentication' (2)
20/03/2016 02:36:40 PM Advertising security type: 'VNC Authentication' (2)
20/03/2016 02:36:48 PM [IPv4] Got connection from client eagle.skynet
20/03/2016 02:36:48 PM   other clients:
20/03/2016 02:36:48 PM Client Protocol Version 3.7
20/03/2016 02:36:48 PM Advertising security type 18
20/03/2016 02:36:48 PM Advertising security type 2
20/03/2016 02:36:48 PM Client returned security type 2
20/03/2016 02:36:58 PM rfbProcessClientNormalMessage: ignoring unknown encoding type 22
20/03/2016 02:36:58 PM rfbProcessClientNormalMessage: ignoring unknown encoding type 21
20/03/2016 02:36:58 PM rfbProcessClientNormalMessage: ignoring unknown encoding type 15
20/03/2016 02:36:58 PM rfbProcessClientNormalMessage: ignoring unknown encoding type -314
20/03/2016 02:36:58 PM Enabling NewFBSize protocol extension for client eagle.skynet
20/03/2016 02:36:58 PM Pixel format for client eagle.skynet:
20/03/2016 02:36:58 PM   32 bpp, depth 24, little endian
20/03/2016 02:36:58 PM   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
20/03/2016 02:36:58 PM no translation needed
20/03/2016 02:36:59 PM rfbProcessClientNormalMessage: ignoring unknown encoding type 15
20/03/2016 02:36:59 PM rfbProcessClientNormalMessage: ignoring unknown encoding type 22
20/03/2016 02:36:59 PM rfbProcessClientNormalMessage: ignoring unknown encoding type 21
20/03/2016 02:36:59 PM rfbProcessClientNormalMessage: ignoring unknown encoding type -314
20/03/2016 02:36:59 PM Enabling NewFBSize protocol extension for client eagle.skynet

Comment 1 Fedora End Of Life 2016-11-24 16:09:21 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2016-12-20 19:32:14 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.