virt-manager will no longer start

After the ‘zypper dup’ to gnome3, virt-manager complains as follows:

virt-manager

Traceback (most recent call last):
File “/usr/share/virt-manager/virt-manager.py”, line 467, in <module>
main()
File “/usr/share/virt-manager/virt-manager.py”, line 360, in main
raise gtk_error
ImportError: could not import gobject (could not find _PyGObject_API object)

My virt-manager package is this:

virt-manager-0.8.7-53.1.x86_64

Anyone else seeing this - or have a solution? I have the following gobject packages installed:

rpm -qa | grep gobj

libcairo-gobject2-1.10.2-6.11.1.x86_64
python-gobject-cairo-2.28.4-2.1.x86_64
python-gobject-devel-2.28.4-2.1.x86_64
libgobject-2_0-0-32bit-2.28.7-3.1.x86_64
libgobject-2_0-0-2.28.7-3.1.x86_64
libavahi-gobject0-0.6.28-4.10.1.x86_64
python-gobject-2.28.4-2.1.x86_64

On Thu, 23 Jun 2011 22:36:03 +0000, dvosburg wrote:

> After the ‘zypper dup’ to gnome3, virt-manager complains as follows:

What does this have to do with the tumbleweed repo?

Don’t use the GNOME 3 tumbleweed repos, if you do, you really are on your
own as they aren’t updated and are not guaranteed to work at all.

If you want GNOME 3, use the “real” GNOME 3 repo and not tumbleweed.

GNOME 3 will get to Tumbleweed, but it is taking a while as I want to
make sure it all works properly. Right now, if you mix the two, you
don’t know what you might get, but usually it means a system that doesn’t
work so well.

sorry,

greg k-h

[QUOTE=gregkh;2358825]On Thu, 23 Jun 2011 22:36:03 +0000, dvosburg wrote:

> After the ‘zypper dup’ to gnome3, virt-manager complains as follows:

>What does this have to do with the tumbleweed repo?

>Don’t use the GNOME 3 tumbleweed repos, if you do, you really are on your
>own as they aren’t updated and are not guaranteed to work at all.

I did in fact use the Tumbleweed GNOME3 repo. With this one exception, I have found it to be quite stable.

http://download.opensuse.org/repositories/openSUSE:/Tumbleweed:/GNOME/openSUSE_Tumbleweed

>GNOME 3 will get to Tumbleweed, but it is taking a while as I want to
>make sure it all works properly. Right now, if you mix the two, you
>don’t know what you might get, but usually it means a system that doesn’t
>work so well.

Will there be an announcement?

Yep, seeing it here to. Not running tumbleweed but installed GNOME from from the GNOME.org site using the 1.3.1 64bit install offered there (GNOME 3 - Made of Easy).
The repository used is the GNOME:STABLE.

Packages on my system:

oSu114G3:~ # rpm -qa | grep gobj
python-gobject-2.28.4-1.2.x86_64
python-gobject-cairo-2.28.4-1.2.x86_64
libgobject-2_0-0-32bit-2.28.8-1.1.x86_64
libgobject-2_0-0-2.28.8-1.1.x86_64
libcairo-gobject2-1.10.2-6.11.1.x86_64
libavahi-gobject0-0.6.30-1.1.x86_64

oSu114G3:~ # rpm -qa | grep virt
virt-manager-0.8.5-8.1.x86_64
libvirt-python-0.8.8-0.10.1.x86_64
virt-viewer-0.2.1-5.2.x86_64
python-virtkey-0.50-4.1.x86_64
libvirt-client-0.8.8-0.10.1.x86_64
libvirt-0.8.8-0.10.1.x86_64
virt-utils-1.1.5-1.2.1.x86_64

oSu114G3:~ # rpm -qa | grep python-go
python-gobject-2.28.4-1.2.x86_64
python-gobject-cairo-2.28.4-1.2.x86_64

This bug might be a lead : Bug #713115 “pygobject reference leak fix causes a lot of PyGTK ...” : Bugs : PyGTK

Tried downgrading the python-goobject & python-gobject-cairo to the stock openSUSE 11.4 2.26 version, but no luck there (&it will probably brake other things).

Does seem changes in the python-goobject are causing the issues with virt-manager?

Cheers,
Willem