Bug 927416 - [abrt] meld-1.7.0-6.fc18: filediff.py:424:on_current_diff_changed:TypeError: 'NoneType' object has no attribute '__getitem__'
Summary: [abrt] meld-1.7.0-6.fc18: filediff.py:424:on_current_diff_changed:TypeError: ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: meld
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:73aa4a0c47e35c503217d399bbf...
Depends On:
Blocks: 962431
TreeView+ depends on / blocked
 
Reported: 2013-03-25 21:03 UTC by Alexander Bisogiannis
Modified: 2015-09-01 03:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 20:17:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (765 bytes, text/plain)
2013-03-25 21:03 UTC, Alexander Bisogiannis
no flags Details
File: environ (2.66 KB, text/plain)
2013-03-25 21:03 UTC, Alexander Bisogiannis
no flags Details

Description Alexander Bisogiannis 2013-03-25 21:03:21 UTC
Description of problem:
I updated mysystem, kernelonly, and after I reboted, on the first log I was presented with an error about meld.

Version-Release number of selected component:
meld-1.7.0-6.fc18

Additional info:
cmdline:        python /usr/bin/meld
core_backtrace: 24dbc2bf4d38d1b06594bdeb0fb2c474c0a8a4b1 0x1a8 on_current_diff_changed /usr/share/meld/meld/filediff.py -
executable:     /usr/bin/meld
kernel:         3.8.3-203.fc18.x86_64
uid:            1000

Truncated backtrace:
filediff.py:424:on_current_diff_changed:TypeError: 'NoneType' object has no attribute '__getitem__'

Traceback (most recent call last):
  File "/usr/share/meld/meld/filediff.py", line 424, in on_current_diff_changed
    insert_chunk = chunk[1] == chunk[2]
TypeError: 'NoneType' object has no attribute '__getitem__'

Local variables in innermost frame:
editable_left: True
pull_left: True
editable_right: False
chunk: None
args: (<gtk.gdk.Event at 0x7f28771e6490: GDK_FOCUS_CHANGE>,)
editable: True
widget: <MeldSourceView object at 0x29e1820 (MeldSourceView at 0x2cb0010)>
self: <FileDiff object at 0x29dba00 (meld+filediff+FileDiff at 0x2cbc900)>
chunk_id: 0
pane: 2
copy_left: True
push_right: True
pull_right: True
push_left: True
copy_right: True
delete: True

Comment 1 Alexander Bisogiannis 2013-03-25 21:03:24 UTC
Created attachment 716204 [details]
File: backtrace

Comment 2 Alexander Bisogiannis 2013-03-25 21:03:27 UTC
Created attachment 716205 [details]
File: environ

Comment 3 Fedora End Of Life 2013-12-21 12:28:29 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 4 Fedora End Of Life 2014-02-05 20:17:28 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


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