Bug 4609

Summary:	Virt-Manager shows: "Cannot display graphical console" type 'spice': no module named SpiceClientGtk
Product:	Mageia	Reporter:	Uli Selle <uli.effer>
Component:	RPM Packages	Assignee:	Olav Vitters <olav>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, nic
Version:	Cauldron	Keywords:	PATCH, Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	MGA2TOO
Source RPM:	spice, spice-gtk 0.9-1.mga2	CVE:
Status comment:
Attachments:	Patch to build with gtk+2 and ship python module

Description Uli Selle 2012-02-21 06:47:10 CET

Description of problem:

When starting a WindowsXP guest machine via virt-manager, using "spice" as Display and "qxl" as vga-card in the machine, only the text ""Cannot display graphical console" type 'spice': no module named SpiceClientGtk" is shown.

Also tried to use "spicec -h localhost -p 5900" from shell without success.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. install the following packages:
spice-client 0.10.0-2.mga2
spice-gtk 0.9-1.mga2
spice-protocol 0.10.1-1.mga2
lib64spice-server1 0.10.0-2.mga2
lib64spice-controller0 0.9-1.mga2
lib64spice-client-gtk3.0_1 0.9-1.mga2
lib64spice-client-gtk-gir3.0 0.9-1.mga2
lib64spice-client-glib2.0_1 0.9-1.mga2
lib64spice-client-glib-gir2.0 0.9-1.mga2
qemu 0.15.1-2.mga2
virt-manager 0.9.0-1.mga2
2. start "virtual machine manager" from menue
3. use Display "spice" and vga-card "qxl" for this client
4. start the vm-guest windows xp

Thanks, Uli

Comment 1 Manuel Hiebel 2012-02-21 16:21:21 CET

Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => olav
Source RPM: spice-client 0.10.0-2.mga2, spice-gtk 0.9-1.mga2 => spice, spice-gtk 0.9-1.mga2

Comment 2 Olav Vitters 2012-02-21 16:38:56 CET

virt-manager wants the gtk 2.0 spice-gtk-python package. I packaged spice-gtk only for gtk 3.0 (for gnome-boxes). Thus no python package.

I don't want to make the spec file really complicated just to add a gtk 2.0 python module. IMO, upstream should use gtk 3.0.

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 3 Marja Van Waes 2012-05-26 13:02:14 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 Buchan Milne 2012-06-29 16:10:15 CEST

Created attachment 2507 [details]
Patch to build with gtk+2 and ship python module

This bug is valid on mga2.

IMHO, spice-gtk should be built against GTK+2 until the python binding supports GTK+3.

I built a local copy of spice-gtk with attached patch against mga2's spice-gtk, and after installing that, virt-manager now supports spice.

(There are probably some other issues, such as leaving orphaned GTK+3 versions behind, but no conflicts etc.).

(I have some problems with spice display with a windows guest, the screen goes black after some time and can't be recovered, VM has to be reset, but those appeared with spicy built against GTK+3 as well - I must still test with a linux VM).

Manuel Hiebel 2012-06-29 17:30:18 CEST

Keywords: NEEDINFO => PATCH
Whiteboard: (none) => /

Manuel Hiebel 2012-06-29 17:30:42 CEST

Whiteboard: / => MGA2TOO

Manuel Hiebel 2012-06-29 17:31:31 CEST

Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1

Comment 5 Olav Vitters 2012-06-30 13:31:33 CEST

That patch would break GNOME boxes AFAIK.

Comment 6 Nic Baxter 2015-02-12 00:52:32 CET

Should this stay opn?

CC: (none) => nic

Comment 7 Marja Van Waes 2015-03-28 18:50:39 CET

(In reply to Nic Baxter from comment #6)
> Should this stay opn?

6 weeks later, and no one thinks it should, so closing as OLD

Feel free to reopen if needed.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD