Bug 180346 - Amarok Version 2.0-SVN-Neon - Using KDE 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)) - Scanning collection fails and leads to freeze
Summary: Amarok Version 2.0-SVN-Neon - Using KDE 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)) -...
Status: RESOLVED DUPLICATE of bug 180248
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-11 17:36 UTC by mathesis
Modified: 2009-01-11 17:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description mathesis 2009-01-11 17:36:57 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

I'm a Kubuntu 8.10 user.
My system is updated according to the following depositories:
- deb http://ppa.launchpad.net/project-neon/ubuntu intrepid main
- deb-src http://ppa.launchpad.net/project-neon/ubuntu intrepid main
- deb http://ppa.launchpad.net/kubuntu-experimental/ubuntu intrepid main

I'm talking about nightlies. Version is Amarok Version 2.0-SVN-Neon - Using KDE 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)).

Trouble is:
By scanning my collection, process stops to around 85% and amarok freezes.
Looking at the log file, one mp3 is indicated.
I remove it from my collection, I rescan, new freeze with the file just above/before in the folder (alphabetically speaking).

I have around 4000 files, mainly in 2 folders. I have no problem with my collection and amarok 1.4.10.
Comment 1 Nicos Gollan 2009-01-11 17:40:00 UTC 
Did you try removing the file directly *after* the last file in the log?
Comment 2 mathesis 2009-01-11 17:42:21 UTC 
Good point:
The file with which amarok seems to always have an issue is the last file of the last folder of my collection (alphabetically speaking for folders & files).
Comment 3 Mark Kretschmann 2009-01-11 17:54:55 UTC 

*** This bug has been marked as a duplicate of bug 180248 ***