Hide Forgot
Version-Release number of selected component: meld-1.7.5-1.fc19 Additional info: reporter: libreport-2.1.7 cmdline: python /usr/bin/meld CONTRIBUTING.md /tmp/WUqCOe_CONTRIBUTING.md executable: /usr/bin/meld kernel: 3.10.11-200.fc19.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: historyentry.py:365:<lambda>:TypeError: <HistoryFileEntry object at 0x2cedb40 (HistoryFileEntry at 0x25a31e0)>: 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 0x2cedb40 (HistoryFileEntry at 0x25a31e0)>: unknown signal name: changed Local variables in innermost frame: self: <HistoryFileEntry object at 0x2cedb40 (HistoryFileEntry at 0x25a31e0)> args: (<gtk.Entry object at 0x2d1f460 (GtkEntry at 0x28e6390)>,)
Created attachment 797864 [details] File: backtrace
Created attachment 797865 [details] File: environ
I have Fedora 20 and upper version of meld (meld.noarch 0:1.8.0-1.fc20) Problem still exists and happening.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.