Bug 896202

Summary: [abrt] exaile-3.3.0-1.fc18: util.py:109:sort_tracks:TypeError: 'NoneType' object is not iterable
Product: [Fedora] Fedora Reporter: chrys87
Component: exaileAssignee: Deji Akingunola <dakingun>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dakingun
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:71637d3b01d9b16412d572c324f49b95b3305bd4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:57:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: environ
none
File: smolt_data none

Description chrys87 2013-01-16 20:20:02 UTC
Description of problem:
i try to appent an soundfile to que

Version-Release number of selected component:
exaile-3.3.0-1.fc18

Additional info:
cmdline:        /usr/bin/python /usr/share/exaile/exaile.py --datadir=/usr/share/exaile/data --startgui
executable:     /usr/share/exaile/exaile.py
kernel:         3.7.2-201.fc18.i686
uid:            1000

Truncated backtrace:
util.py:109:sort_tracks:TypeError: 'NoneType' object is not iterable

Traceback (most recent call last):
  File "/usr/share/exaile/xlgui/widgets/menuitems.py", line 108, in _append_cb
    tracks = trax.sort_tracks(sort_by, tracks, reverse=reverse)
  File "/usr/share/exaile/xl/trax/util.py", line 109, in sort_tracks
    return sorted(iter, key=keyfunc, reverse=reverse)
TypeError: 'NoneType' object is not iterable

Local variables in innermost frame:
reverse: False
fields: ['artist', 'date', 'album', 'discnumber', 'tracknumber', 'title']
iter: None
trackfunc: <function <lambda> at 0xa5c74a74>
keyfunc: <function <lambda> at 0xa5c74aac>
artist_compilations: True

Comment 1 chrys87 2013-01-16 20:20:05 UTC
Created attachment 679786 [details]
File: backtrace

Comment 2 chrys87 2013-01-16 20:20:07 UTC
Created attachment 679787 [details]
File: core_backtrace

Comment 3 chrys87 2013-01-16 20:20:10 UTC
Created attachment 679789 [details]
File: environ

Comment 4 chrys87 2013-01-16 20:20:12 UTC
Created attachment 679790 [details]
File: smolt_data

Comment 5 Fedora End Of Life 2013-12-21 10:26:07 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 6 Fedora End Of Life 2014-02-05 14:57:30 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.