Bug 1122692

Summary: TypeError: <HistoryFileEntry object at 0x2a8f7d0 (HistoryFileEntry at 0x2b12040)>: unknown signal name: changed
Product: Red Hat Enterprise Linux 7 Reporter: John Conroy <jconroy>
Component: pygobject2Assignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.0   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-25 14:59:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Conroy 2014-07-23 19:24:06 UTC
Description of problem:
Same issue as in BZ #888290, but for EL7.


Version-Release number of selected component (if applicable):
pygobject2-2.28.6-11.el7.x86_64


How reproducible:
Always


Steps to Reproduce:
1.  Build meld-1.8.5 (http://koji.fedoraproject.org/koji/buildinfo?buildID=536969)
2.  Install and run meld-1.8.5


Actual results:
/usr/lib64/python2.7/site-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/share/meld/meld/ui/historyentry.py", line 365, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2a8f7d0 (HistoryFileEntry at 0x2b12040)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/share/meld/meld/ui/historyentry.py", line 365, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2a8fa50 (HistoryFileEntry at 0x2b12160)>: unknown signal name: changed


Expected results:
No warnings/errors.


Additional info:
Simply building and installing the Fedora release of pygobject2-2.28.6-11.fc20 (which has the patch from Comment #5 of BZ #888290) took care of the issue for me.

https://bugzilla.redhat.com/show_bug.cgi?id=888290#c5