Bug 692361

Summary: Error importing spice: No module named SpiceClientGtk
Product: Red Hat Enterprise Linux 6 Reporter: Nan Zhang <nzhang>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.1CC: dyuan, llim, vbian
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-31 07:13:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nan Zhang 2011-03-31 06:51:24 UTC 
Description of problem:
Found an error posted in virt-manager debug info.

2011-03-31 14:41:10,185 (config:34): Error importing spice: No module named
SpiceClientGtk

Version-Release number of selected component (if applicable):
virt-manager-0.8.6-3.el6.noarch

How reproducible:
always

Steps to Reproduce:
# virt-manager --debug
  
Actual results:
2011-03-31 14:41:10,109 (virt-manager:175): Application startup
2011-03-31 14:41:10,109 (virt-manager:352): Launched as:
/usr/share/virt-manager/virt-manager.py --debug
2011-03-31 14:41:10,185 (config:34): Error importing spice: No module named
SpiceClientGtk
2011-03-31 14:41:10,287 (engine:335): About to connect to uris
['qemu:///system']
2011-03-31 14:41:10,326 (engine:461): window counter incremented to 1
2011-03-31 14:41:10,367 (connection:872): Scheduling background open thread for
qemu:///system
2011-03-31 14:41:10,368 (connection:1032): Background thread is running
2011-03-31 14:41:10,382 (connection:1060): Background open thread complete,
scheduling notify
2011-03-31 14:41:10,406 (connection:1065): Notifying open result
2011-03-31 14:41:10,588 (connection:1072): qemu:///system capabilities:
(...)

Expected results:


Additional info:
Comment 1 Nan Zhang 2011-03-31 07:13:31 UTC 

*** This bug has been marked as a duplicate of bug 680060 ***