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 bugs in PyGTK which need to be
fixed first. (See LP #713115, #713172, #713135)
-- Martin Pitt <[email protected]> Fri, 04 Feb 2011 18:18:51
+0100
I forwarded the pygtk bug upstream with the small reproducer; I'll still
look into this a bit further, though.
** Bug watch added: GNOME Bug Tracker #641525
https://bugzilla.gnome.org/show_bug.cgi?id=641525
** Also affects: pygtk via
https://bugzilla.gnome.org/show_bug.cgi?id=641525
Importance: Unknown
Status: Unknown
** Changed in: pygobject (Ubuntu Natty)
Status: In Progress => Invalid
** Changed in: pygtk (Ubuntu Natty)
Importance: Undecided => High
** Changed in: pygtk (Ubuntu Natty)
Status: New => Triaged
** Summary changed:
- [natty] virt-manager no longer starts with recent updates
+ pygobject reference leak fix causes a lot of PyGTK apps to fail
--
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:
pygobject reference leak fix causes a lot of PyGTK apps to fail
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
