Version-Release number of selected component: meld-1.7.1-3.fc19 Additional info: cmdline: python /usr/bin/meld core_backtrace: ee9fef0ac2f836aa0bfbb3e91dc438097c5fcba6 0x118 <lambda> /usr/share/meld/meld/ui/historyentry.py - executable: /usr/bin/meld kernel: 3.9.0-301.fc19.i686.PAE runlevel: N 5 uid: 1000 ureports_counter: 1 Truncated backtrace: historyentry.py:280:<lambda>:TypeError: <HistoryFileEntry object at 0xb50d943c (HistoryFileEntry at 0xa0f0c68)>: unknown signal name: changed Traceback (most recent call last): File "/usr/share/meld/meld/ui/historyentry.py", line 280, in <lambda> entry.connect("changed", lambda *args: self.emit("changed")) TypeError: <HistoryFileEntry object at 0xb50d943c (HistoryFileEntry at 0xa0f0c68)>: unknown signal name: changed Local variables in innermost frame: self: <HistoryFileEntry object at 0xb50d943c (HistoryFileEntry at 0xa0f0c68)> args: (<gtk.Entry object at 0xb50daeb4 (GtkEntry at 0xa0bedf0)>,)
Created attachment 742655 [details] File: backtrace
Created attachment 742657 [details] File: environ
Same as https://bugzilla.redhat.com/show_bug.cgi?id=888290
*** This bug has been marked as a duplicate of bug 888290 ***