Summary: | Information on several tracks lost after deleting some music | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Frederik Schwarzer <schwarzer> |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mitchell, ralf-engels |
Priority: | VHI | Keywords: | release_blocker |
Version: | 2.4-GIT | ||
Target Milestone: | 2.4.0 | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.4 | |
Sentry Crash Report: |
Description
Frederik Schwarzer
2011-01-07 22:29:03 UTC
commit 137de448c030cbfeb9de3bc21969f259a7291eca branch master Author: Mark Kretschmann <kretschmann@kde.org> Date: Sat Jan 8 19:08:55 2011 +0100 Fix major issue with the Collection missing whole albums, and mixing up artists. Big thanks to Ralf Engels, who came up with this fix! :) BUG: 262459 CCMAIL: amarok-devel@kde.org diff --git a/src/core-impl/collections/db/sql/SqlScanResultProcessor.cpp b/src/core-impl/collections/db/sql/SqlScanResultProcessor.cpp index d861da8..4a2b1ab 100644 --- a/src/core-impl/collections/db/sql/SqlScanResultProcessor.cpp +++ b/src/core-impl/collections/db/sql/SqlScanResultProcessor.cpp @@ -161,6 +161,7 @@ SqlScanResultProcessor::commitTrack( CollectionScanner::Track *track, if( m_foundTracks.contains( uid ) ) { warning() << "track"<<track->path()<<"with uid"<<uid<<"already committed. There seems to be a duplicate uid."; + return; } m_foundTracks.insert( uid ); I hope that solves the problem. If not can you give more information. Which tracks got emptied? Is there some relation to the deleted tracks (same directory e.g.) What happens if you "touch" the directory with the emptied tracks and do a rescan? What happens with the collection (the tab on the left side). Is the collection updated? Do the tracks disappear from there too? As far as I see it now, only the entries of the deleted folders are emptied in the playlist. On further testing however, Amarok crashed without a backtrace. I will open another report for that. Thanks for the quick fix. :) |