RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1320806 - Spice-password guest can't be connected by virt-viewer
Summary: Spice-password guest can't be connected by virt-viewer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice-gtk
Version: 7.3
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Grunt
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-24 03:08 UTC by mxie@redhat.com
Modified: 2016-11-04 01:15 UTC (History)
10 users (show)

Fixed In Version: spice-gtk-0.26-8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 01:15:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (14.00 KB, image/png)
2016-03-24 03:08 UTC, mxie@redhat.com
no flags Details
virt-viewer-log (10.34 KB, text/plain)
2016-03-24 03:09 UTC, mxie@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2229 0 normal SHIPPED_LIVE virt-viewer, libgovirt, spice-gtk, and usbredir bug fix and enhancement update 2016-11-03 13:26:58 UTC

Description mxie@redhat.com 2016-03-24 03:08:35 UTC
Created attachment 1139821 [details]
screenshot

Description of problem:
Spice-password guest can't be connected by virt-viewer  

Version-Release number of selected component (if applicable):
virt-viewer-2.0-7.el7.x86_64
spice-gtk-0.26-7.el7.x86_64
usbredir-0.6-8.el7.x86_64
libvirt-1.3.2-1.el7.x86_64
libgovirt-0.3.3-1.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
 
1.Preprare the guest which has display spice and password
|
2.Using virt-viewer to connect the guest
#virt-viewer rhel6.6 --debug --spice-debug
(virt-viewer:29952): virt-viewer-DEBUG: main channel: auth failure (wrong username/password?)
(virt-viewer:29952): GSpice-DEBUG: spice-channel.c:2658 main-1:0: channel disconnect 0
(virt-viewer:29952): GSpice-DEBUG: spice-session.c:1486 no migration in progress
(virt-viewer:29952): GSpice-DEBUG: spice-channel.c:2433 main-1:0: Coroutine exit main-1:0
(virt-viewer:29952): GSpice-DEBUG: channel-main.c:1499 agent connected: no
(virt-viewer:29952): GSpice-DEBUG: spice-channel.c:2181 main-1:0: Delayed unref channel 0x1f61c10
(virt-viewer:29952): virt-viewer-DEBUG: Dispatch timeout 0x1f4fe30 0x7f98568824b0 2 0x1dfee90
(virt-viewer:29952): virt-viewer-DEBUG: Update timeout 0x1f4fe30 2 5000
(virt-viewer:29952): virt-viewer-DEBUG: Update timeout 0x1f4fe30 2 5000
(virt-viewer:29952): virt-viewer-DEBUG: Dispatch handler 8 1 0x1ef3f20
(virt-viewer:29952): virt-viewer-DEBUG: Update timeout 0x1f4fe30 2 5000
(virt-viewer:29952): virt-viewer-DEBUG: Dispatch handler 8 3 0x1ef3f20
(virt-viewer:29952): virt-viewer-DEBUG: Update timeout 0x1f4fe30 2 5000
(virt-viewer:29952): virt-viewer-DEBUG: Window closed
(virt-viewer:29952): virt-viewer-DEBUG: Unable to get comment from key file: Key file does not have group '05bf4df1-852f-40c0-a287-a96a8acdcf15'
(virt-viewer:29952): GSpice-DEBUG: spice-session.c:1665 session: disconnecting 0
(virt-viewer:29952): GSpice-DEBUG: spice-session.c:160 New session (compiled from package spice-gtk 0.26)
(virt-viewer:29952): GSpice-DEBUG: spice-session.c:164 Supported channels: main, display, inputs, cursor, playback, record, smartcard, usbredir
(virt-viewer:29952): GSpice-DEBUG: usb-device-manager.c:874 device added 0x1fda250

3.Input the password in authentication required dialog, it shows connecting at console for a long long time, pls refer to screenshot and log at attachment

 
Actual results:
As description

Expected results:
Spice-password guest could be connected by virt-viewer normally
 
Addtional info:
1.VNC-password guest has no this problem
2.spice guest which has no password could be connected by virt-viewer normally
3.This problem can't be reproduced on rhel7.2.z
the builds as below:
virt-viewer-2.0-6.el7.x86_64
libvirt-1.2.17-13.el7_2.4.x86_64
usbredir-0.6-7.el7.x86_64
spice-gtk-0.26-5.el7.x86_64
libgovirt-0.3.3-1.el7_2.1.x86_64

Comment 1 mxie@redhat.com 2016-03-24 03:09:46 UTC
Created attachment 1139822 [details]
virt-viewer-log

Comment 3 Pavel Grunt 2016-03-24 09:11:50 UTC
Fixed in spice-gtk by
61f70b689044ea53f4103e79a128af640c003f48

Comment 4 Mike McCune 2016-03-28 23:16:15 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Han Han 2016-04-08 07:48:51 UTC
It can be reproduced with spice-gtk-0.26-6 when use virt-viewer -c option.

Comment 10 errata-xmlrpc 2016-11-04 01:15:30 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-2016-2229.html


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