Something changes in pygobject 2.27.0+git20110131 that causes this.
Downgrading to 2.27.0+git20110108 makes it work again.
** Also affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Reproducible from a clean install without configuration.
** Changed in: pygobject (Ubuntu)
Importance: Undecided = High
** Changed in: pygobject (Ubuntu)
Status: New = Triaged
** Changed in: pygobject (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Also affects:
The crash is triggered by this commit:
http://git.gnome.org/browse/pygobject/commit/?id=f0a0b6c2eda89622de2b1e5ebb6a48103ad72a42
That patch is really correct, as it fixes previously uncleaned
references, i. e. fixes tons of memory leaks. The problem is that this
uncovered a lot of bugs in GTK
** Package changed: virt-manager (Ubuntu Natty) = pygtk (Ubuntu Natty)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in ubuntu.
https://bugs.launchpad.net/bugs/713115
Title:
[natty] virt-manager no longer starts with
As this is the sort of master bug, bug #713135 and bug #713172 describe
different issues with the new pygobject (in hamster-applet and meld).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in ubuntu.
For the record, this seems to be a reasonably small reproducer which
doesn't cause the segfault (yet), but at least reproduces the invalid
references:
$ python -c 'import gtk; r=gtk.ImageMenuItem(foo);
i=gtk.image_new_from_icon_name(gtk-ok, gtk.ICON_SIZE_MENU); r.set_image(i)'
-c:1: Warning:
I uploaded a workaround to limit the impact of this for now, to
essentially bring it back to the old memleak state:
pygobject (2.27.0+git20110131-0ubuntu6) natty; urgency=low
* Add revert-refleak.patch: Revert upstream commit f0a0b6c2eda for now.
Fixing the reference leaks uncovered a few
