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:
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.
>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.
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.
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?