Bug 1122692 - TypeError: <HistoryFileEntry object at 0x2a8f7d0 (HistoryFileEntry at 0x2b12040)>: unknown signal name: changed
Summary: TypeError: <HistoryFileEntry object at 0x2a8f7d0 (HistoryFileEntry at 0x2b120...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pygobject2
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-23 19:24 UTC by John Conroy
Modified: 2019-07-01 17:47 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
CentOS 9656 None None None Never

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


Note You need to log in before you can comment on or make changes to this bug.