Fedora Account System
Red Hat Associate
Red Hat Customer
abrt 1.0.6 detected a crash. architecture: x86_64 cmdline: python /usr/lib/python2.6/site-packages/whaawmp/whaawmp.py component: whaawmp executable: /usr/lib/python2.6/site-packages/whaawmp/whaawmp.py kernel: 2.6.31.12-174.2.22.fc12.x86_64 package: whaawmp-0.2.12.1-3.fc12 release: Fedora release 12 (Constantine) backtrace ----- Summary: TB4a5893e9 gstTagger.py:61:getDispTitle:TypeError: cannot concatenate 'str' and 'list' objects Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/whaawmp/common/gstTagger.py", line 116, in onMessage func(uri, message.parse_tag(), *args) File "/usr/lib/python2.6/site-packages/whaawmp/gui/queue.py", line 100, in setItmTags dispTitle = tagger.getDispTitle(tags) File "/usr/lib/python2.6/site-packages/whaawmp/common/gstTagger.py", line 61, in getDispTitle winTitle += nStr TypeError: cannot concatenate 'str' and 'list' objects Local variables in innermost frame: winTitle: '' x: (True, 'artist') nStr: [u'Dire Straits', u'Dire Straits'] tags: <GstTagList at 0x7f3a6c001260> noneAdded: False
Created attachment 395469 [details] File: backtrace
How can you reproduce this bug? It's pretty unsure, whats in the variable tags in the backtrace above. It's strange, that in tags is a list "nStr = tags[x[1]]", but it should be a string... So I don't want to blindly fix this issue in this snippet without knowing, where the bug comes from and if this always safe to fix (like I intend atm). Maybe you played 2 differend files with exactly the same artist/song name in the playlist?
Dear Thomas, i am not sure i am able to reproduce this bug, i migth have two different players working at the same time, it was in a try to get some audio player to work, unfortunable i have not get this whaawmp to work yet, and i think i disable the program.
(In reply to comment #3) > Dear Thomas, i am not sure i am able to reproduce this bug, i migth have two > different players working at the same time, it was in a try to get some audio > player to work, unfortunable i have not get this whaawmp to work yet, and i > think i disable the program. In that case, it would not be easy possible to fix that bug. If nStr is a list, pick the first one, is hard to tell, if this is always a proper fix... I just mailed the author about this, waiting for an answer.
The author fixed this in the git repository and this will be fixed in the next version of whaawmp. See: http://gitorious.org/whaawmp/mainline/commit/6e055985a33bdc828c1cd1bb80639419e25883bc Because this bug is unlikely to happen more often and there is no easy possibility to say 'How to reproduce', I consider this bug as 'fixed upstream'. Thanks for reporting. Feel free to reopen, if you can tell how to reproduce or if this happens more often, so a git snapshot might be needed.