Bug 1017862 - Cannot connect to VMs on RHEL5 host
Summary: Cannot connect to VMs on RHEL5 host
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice-gtk
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Christophe Fergeau
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1017860 1017864 1109397
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-10 15:58 UTC by Christophe Fergeau
Modified: 2015-03-05 13:40 UTC (History)
6 users (show)

Fixed In Version: spice-gtk-0.22-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1017860
Environment:
Last Closed: 2015-03-05 13:40:39 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0297 0 normal SHIPPED_LIVE spice-gtk bug fix and enhancement update 2015-03-05 17:33:27 UTC

Description Christophe Fergeau 2013-10-10 15:58:02 UTC
+++ This bug was initially created as a clone of Bug #1017860 +++

Trying to connect to a RHEL5 VM causes a warning in the console '(remote-viewer:9644): GSpice-WARNING **: major mismatch (got 1, expected 2)' and an error message that it couldn't connect to the remote VM.
Tested with spice-gtk.x86_64 0:0.20-9.el6

This is fixed by http://lists.freedesktop.org/archives/spice-devel/2013-October/014897.html, scratch build with these 2 patches available from http://brewweb.devel.redhat.com/brew/taskinfo?taskID=6398063

Comment 3 Marc-Andre Lureau 2014-07-08 15:45:51 UTC
why not QA ack? this is included in 0.22 rebase anyway

Comment 7 errata-xmlrpc 2015-03-05 13:40:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0297.html


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