meld crashed with TypeError in <lambda>(): <HistoryFileEntry object at 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed

[Anders Kaseorg]

meld crashed with TypeError in <lambda>(): <HistoryFileEntry object at 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: meld 1.6.1-1
ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Tue Jan 22 15:57:30 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/meld
InstallationDate: Installed on 2010-12-05 (779 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/meld barnowl-1.10dev barnowl-1.9dev-127-g0b4c4c8-src
PythonArgs: ['/usr/bin/meld', 'barnowl-1.10dev', 'barnowl-1.9dev-127-g0b4c4c8-src']
SourcePackage: meld
Title: meld crashed with TypeError in <lambda>(): <HistoryFileEntry object at 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed
Traceback:
 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 0x1e58960 (HistoryFileEntry at 0x1f08540)>: unknown signal name: changed
UpgradeStatus: Upgraded to raring on 2012-11-15 (68 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sudo wireshark

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Anders Kaseorg (andersk)]

This seems to happen every time I start meld.

[Marc Deslauriers (mdeslaur)]

Here's my complete stacktrace:

/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):
  File "/usr/lib/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2babc30 (HistoryFileEntry at 0x2bbcab0)>: unknown signal name: 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/

[Marc Deslauriers (mdeslaur)]

This is actually an issue with pygtk and recent glib versions:

https://bugs.launchpad.net/pygtk/+bug/1129309

Leaving this bug open for now, as a possible solution is to port meld to gtk3