Bug 692361 - Error importing spice: No module named SpiceClientGtk
Summary: Error importing spice: No module named SpiceClientGtk
Keywords:
Status: CLOSED DUPLICATE of bug 680060
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.1
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 06:51 UTC by Nan Zhang
Modified: 2011-04-15 11:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-31 07:13:31 UTC
Target Upstream Version:


Attachments (Terms of Use)

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 ***


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