Version-Release number of selected component: meld-1.7.3-1.fc19 Additional info: reporter: libreport-2.1.4 cmdline: python /usr/bin/meld core_backtrace: ab49178196614ef2e7ffdcb5c91d0d82b0b177a0 0x166 <lambda> /usr/share/meld/meld/ui/historyentry.py - executable: /usr/bin/meld kernel: 3.9.4-301.fc19.i686.PAE runlevel: N 5 uid: 1000 Truncated backtrace: historyentry.py:358:<lambda>:TypeError: <HistoryFileEntry object at 0x93db6e4 (HistoryFileEntry at 0x94d3810)>: unknown signal name: changed Traceback (most recent call last): File "/usr/share/meld/meld/ui/historyentry.py", line 358, in <lambda> entry.connect("changed", lambda *args: self.emit("changed")) TypeError: <HistoryFileEntry object at 0x93db6e4 (HistoryFileEntry at 0x94d3810)>: unknown signal name: changed Local variables in innermost frame: self: <HistoryFileEntry object at 0x93db6e4 (HistoryFileEntry at 0x94d3810)> args: (<gtk.Entry object at 0x93de0f4 (GtkEntry at 0x94a1da0)>,)
Created attachment 758231 [details] File: backtrace
Created attachment 758232 [details] File: environ
Created attachment 775640 [details] Error logs This is still a problem. Just compared two files. Devon
Upstream: https://bugzilla.gnome.org/show_bug.cgi?id=701620
Occured when running in `su root` environment with two file descriptors
Occurs consistently when doing "git mergetool" when quitting. Does not seem to matter whether I'm doing a save-during-quit or not.
Created attachment 783214 [details] Move property and signal creation into _class_init() This is a backport of commit efcb0f9fd for 2.28.x. This allows old pygtk applications to work with pygobject 2.28.x and glib 2.35.x. Reference: http://archive.ubuntu.com/ubuntu/pool/main/p/pygobject-2/pygobject-2_2.28.6.orig.tar.bz2 //debian/patches/00git_class_init.patch
Aforementioned patch applied to pygobject2-2.28.6-9 fixes the issue for me.
(In reply to Damian Wrobel from comment #8) > Aforementioned patch applied to pygobject2-2.28.6-9 fixes the issue for me. I’m afraid I’m still experiencing the issue after that update.
Same issue when comparing two ASCII files. F19 system, 'yum update'd yesterday.
Mine is still throwing an error as well, no changes.
Created attachment 787549 [details] Error logs New errror logs encase the error has changed from time. Thanks, Devon
(In reply to Pablo Rodríguez from comment #9) > (In reply to Damian Wrobel from comment #8) > > Aforementioned patch applied to pygobject2-2.28.6-9 fixes the issue for me. > > I’m afraid I’m still experiencing the issue after that update. The pygobject2-2.28.6-9 package doesn't contain any fixes for that issue, you need to manually apply the patch mentioned in the comment #7 and rebuild the package to get rid of this issue.
*** This bug has been marked as a duplicate of bug 888290 ***