Bug 1315796 - [abrt] meld: vcview.py:861:find_iter_by_name:TypeError: startswith first arg must be str, unicode, or tuple, not NoneType
Summary: [abrt] meld: vcview.py:861:find_iter_by_name:TypeError: startswith first arg ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: meld
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:d7653903eef7e2444853db17d1e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-08 15:32 UTC by Matej
Modified: 2016-12-20 19:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 19:19:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (811 bytes, text/plain)
2016-03-08 15:32 UTC, Matej
no flags Details
File: environ (1.55 KB, text/plain)
2016-03-08 15:32 UTC, Matej
no flags Details

Description Matej 2016-03-08 15:32:27 UTC
Version-Release number of selected component:
meld-3.14.0-2.fc23

Additional info:
reporter:       libreport-2.6.4
cmdline:        /usr/bin/python /usr/bin/meld .
executable:     /usr/bin/meld
kernel:         4.4.2-301.fc23.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
vcview.py:861:find_iter_by_name:TypeError: startswith first arg must be str, unicode, or tuple, not NoneType

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/meld/meldwindow.py", line 597, in on_file_changed
    page.on_file_changed(filename)
  File "/usr/lib/python2.7/site-packages/meld/vcview.py", line 837, in on_file_changed
    it = self.find_iter_by_name(filename)
  File "/usr/lib/python2.7/site-packages/meld/vcview.py", line 861, in find_iter_by_name
    elif name.startswith(path):
TypeError: startswith first arg must be str, unicode, or tuple, not NoneType

Local variables in innermost frame:
path: None
self: <VcView object at 0x7fea8edb5780 (VcView at 0x559e18b836a0)>
it: <GtkTreeIter at 0x559e1adb5b60>
name: '<deleted>.yaml'
child: <GtkTreeIter at 0x559e1ad99540>

Comment 1 Matej 2016-03-08 15:32:31 UTC
Created attachment 1134225 [details]
File: backtrace

Comment 2 Matej 2016-03-08 15:32:33 UTC
Created attachment 1134226 [details]
File: environ

Comment 3 Fedora End Of Life 2016-11-24 15:58:23 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 4 Fedora End Of Life 2016-12-20 19:19:00 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.