From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/4.0; Linux) KHTML/4.0.5 (like Gecko) Fedora/4.0.5-2.fc9
Description of problem:
sonata gives traceback when run
see: "actual results" for the traceback.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run sonata
Traceback (most recent call last):
File "/usr/bin/sonata", line 48, in <module>
app = main.Base()
File "/usr/lib/python2.5/site-packages/sonata/main.py", line 1065, in __init__
File "/usr/lib/python2.5/site-packages/sonata/main.py", line 1654, in
File "/usr/lib/python2.5/site-packages/sonata/main.py", line 1611, in iterate
File "/usr/lib/python2.5/site-packages/sonata/main.py", line 3517, in
File "/usr/lib/python2.5/site-packages/sonata/main.py", line 2389, in
for item in lsinfo:
TypeError: 'NoneType' object is not iterable
Unhandled exception in thread started by
Error in sys.excepthook:
Original exception was:
Sonata should have started
Same crash has been seen on fedora 8 when trying to connect to mpd on fedora 9
-> bug is most probably related to mpd in some way.
This seems to happen while mpd is indexing music directories.
When mpd is done, sonata starts as it should.
Still, I don't think that should crash when mpd is indexing.
I am not sure when it happens because I don't have this problem myself (or at
last, I wasn't able to reproduce it myself).
You mean that you're doing "mpd --create-db" and then sonata crashes? Or sonata
crashes during every run?
Looks like it works now.
When we saw the crashes, mpd was generating the database (rather large one, so
it takes time) for the very first time (new, clean install). So the database was
empty or possibly partly generated (I don't know how mpd does that) when we
tried to start sonata.
I don't know how to purge mpd's base, so I can't retest the theory (and I'd
rather not reinstall again).
Karl, to try to reproduce with a clean base, you could try just renaming the config files.
e.g. all my mpd config files are in ~/.mpd
mv ~/.mpd ~/.mpd~
That might give you an idea.
Then to get back to original config by deleting ~/.mpd & moving ~/.mpd~ back to ~/.mpd
I might try this myself when I get the chance.
This was a while ago.
I'm afraid I am on F10 now, and I don't really use sonata anymore.
I might try sonata here sometime later, but currently there seem to be a problem with the sound output (crackling sound) via mpd.
(Probably a regression; I have had it a while back, then it went away then it came back. All with new kernel releases) Anyway, it is not related to this sonata issue anyway.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. 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 '9'.
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 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.
Thank you for reporting this bug and we are sorry it could not be fixed.