Music scan partially fails on Ubuntu Jaunty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Moovida |
Fix Released
|
Critical
|
Guillaume Emont | ||
elisa-plugins-bad (Ubuntu) |
Fix Released
|
Undecided
|
Loïc Minier |
Bug Description
When I run Elisa 0.5.34 under Mandriva Linux cooker version (2009.1 pre-release) it fails to index more than half the tracks. My music collection is around 3200 tracks all in flac format. The first time I ran it I left the music scan running all night and it only reached around 30% done and appeared to have stopped with all the memory and swap space on the machine used. It took several restarts of Elisa for the scan to reach 100%. The music library shows my albums but at least half the tracks are missing, e.g an ablum will only list tracks 4,5,6 and 9. Subsequent restarts of Elisa doesn't add anymore tracks to the list (the music scan reaches 100% in a few seconds).
Even if I add one new album to the collection it shows the same symptoms, e.g. the music scan will complete and the album appears in the list but not all the tracks are there.
I also have Elisa running on another PC under the stable Mandriva 2009.0 release and music scan picks up all tracks correctly. The 2 PCs have similar hardware, Core2 Duo CPU, 2GB RAM + Nvidia graphics with the same music files. The main difference between Mandriva 2009.0 and 2009.1 that could be relevant is the upgrade from python 2.4 to 2.6
I've also noticed Elisa is 100% busy on one CPU even when idle under 2009.1 but not 2009.0.
Changed in elisa: | |
assignee: | nobody → guijemont |
milestone: | 0.6.x → 0.5.37 |
status: | Confirmed → In Progress |
Changed in elisa: | |
status: | In Progress → Fix Committed |
Changed in elisa: | |
status: | Fix Committed → Fix Released |
Thanks for investigating that issue Pete!
Most of the developers of the team use Python 2.5 so Elisa is poorly tested with Python 2.6, excepted for users like you who have the luck to have Python 2.6 on their distro ;)
Can you have a look at ~/.elisa- 0.5/elisa. log and see if there are any relevant traceback reported there? Also check the processes running, there should be elisa itself and 2 elisa gst_metadata "slave" processess running. Is that the case for you?