Bug 1013224 - [abrt] meld-1.7.3-1.fc19: gnomeglade.py:61:__getattr__:AttributeError: on_file_changed
[abrt] meld-1.7.3-1.fc19: gnomeglade.py:61:__getattr__:AttributeError: on_fil...
Product: Fedora
Classification: Fedora
Component: meld (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dominic Hopf
Fedora Extras Quality Assurance
: 1040942 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2013-09-28 09:39 EDT by matti aarnio
Modified: 2015-02-17 12:23 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 12:23:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (478 bytes, text/plain)
2013-09-28 09:39 EDT, matti aarnio
no flags Details
File: environ (3.73 KB, text/plain)
2013-09-28 09:39 EDT, matti aarnio
no flags Details

  None (edit)
Description matti aarnio 2013-09-28 09:39:28 EDT
Description of problem:
Running some git-gui thing (gitk?), which in turn offered to run meld to merge multiple diffs together.

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.7
cmdline:        python /bin/meld ./core/src/main/java/org/bouncycastle/asn1/DLSequence.java.LOCAL.java core/src/main/java/org/bouncycastle/asn1/DLSequence.java ./core/src/main/java/org/bouncycastle/asn1/DLSequence.java.REMOTE.java
executable:     /bin/meld
kernel:         3.10.9-200.fc19.x86_64
runlevel:       N 3
type:           Python
uid:            500

Truncated backtrace:
gnomeglade.py:61:__getattr__:AttributeError: on_file_changed

Traceback (most recent call last):
  File "/usr/share/meld/meld/meldwindow.py", line 638, in on_file_changed
  File "/usr/share/meld/meld/ui/gnomeglade.py", line 61, in __getattr__
    raise AttributeError(key)
AttributeError: on_file_changed

Local variables in innermost frame:
widget: None
self: <NewDiffTab object at 0x1cbedc0 (NewDiffTab at 0x1a57e40)>
key: 'on_file_changed'
Comment 1 matti aarnio 2013-09-28 09:39:32 EDT
Created attachment 804420 [details]
File: backtrace
Comment 2 matti aarnio 2013-09-28 09:39:35 EDT
Created attachment 804421 [details]
File: environ
Comment 3 Dominic Hopf 2014-07-02 20:46:28 EDT
*** Bug 1040942 has been marked as a duplicate of this bug. ***
Comment 4 Fedora End Of Life 2015-01-09 15:01:06 EST
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.
Comment 5 Fedora End Of Life 2015-02-17 12:23:39 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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

Thank you for reporting this bug and we are sorry it could not be fixed.

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