GNOME Bugzilla – Bug 693812
crash in HistoryFileEntry
Last modified: 2013-02-19 13:33:22 UTC
meld crashed with TypeError in <lambda>(): <HistoryFileEntry object at 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed See downstream bug report: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1103170
Unfortunately the downstream report doesn't make a lot of sense. HistoryEntry definitely has a changed signal, as it's a gtk.ComboBoxEntry, as does HistoryFileEntry, as it's a gtk.Editable. This code hasn't changed in any recent release, so either something weird has broken in Ubuntu's pygtk package, or there's a lot of missing backtrace. I'm sorry, but I'm going to need more to go on here.
Here's what I see when running meld from the command line: /usr/lib/python2.7/dist-packages/gobject/__init__.py:115: Warning: attempting to add an interface (GtkEditable) to class (HistoryFileEntry) after class_init type_register(cls, namespace.get('__gtype_name__')) Traceback (most recent call last):
+ Trace 231530
entry.connect("changed", lambda *args: self.emit("changed"))
Traceback (most recent call last): File "/usr/lib/meld/meld/ui/historyentry.py", line 277, in <lambda> entry.connect("changed", lambda *args: self.emit("changed")) TypeError: <HistoryFileEntry object at 0x2babaf0 (HistoryFileEntry at 0x2b6a450)>: unknown signal name: changed The first warning looks suspicious, and seems related to: http://blogs.gnome.org/desrt/2012/11/05/a-warning-about-glib/
This is because pygtk doesn't currently get along with glib 2.35.x, duping. *** This bug has been marked as a duplicate of bug 694108 ***
Aside from that, pygtk has been obsolete for many years now -- it's really high time to port programs to GTK3 and GI!