Bug 131114 - Deleting a track whilst building collection destroys database
Summary: Deleting a track whilst building collection destroys database
Status: RESOLVED UNMAINTAINED
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 1.4.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-20 15:32 UTC by Matt Howe
Modified: 2008-12-05 01:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Howe 2006-07-20 15:32:37 UTC
Version:           1.4.1 (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
OS:                Linux

Whilst my collection was being rebuilt I tried to delete a file from the collection, when the collection building progress bar had finished my database had been corrupted (tracks on wrong albums, most of them missing, etc.)
Comment 1 Fry 2007-07-31 23:57:59 UTC
I had the same or possibly a similar problem:

I deleted some files while I was transkoding some other files. Now most of my collection is missing, and the rest is filed under "Various Artists" and will not go out of Various Artists even if I tell it to stop filing it there.

Attempting to rescan the collection in full resulted in an amarok freeze (probably infinite loop) that requires killall. Wiping the collection directory and adding to it for piecemeal rescan does not restore the collection. The same 50 or so tracks on 16 albums are still the only ones listed.
Comment 2 Myriam Schweingruber 2008-12-05 01:57:32 UTC
Thank you for your report. Amarok 1.4.x is not maintained anymore. Feel free to report any bug you might come across in Amarok 2.