Bug 203875

Summary: Rescanning the collection results in duplicate showings in both the CollectionBrowser and the PlayistBrowser
Product: [Applications] amarok Reporter: Myriam Schweingruber <myriam>
Component: Collections/LocalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED DUPLICATE    
Severity: minor CC: bart.cerneels, mitchell
Priority: NOR    
Version: 2.3-GIT   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Screenshot with double entries in the collection browser

Description Myriam Schweingruber 2009-08-14 20:18:26 UTC
When doing a rescan of the collection with an already existing database, both the PlaylistBrowser and the CollectionBrowser show random double entries.

After a restart both browsers show a correct display again. Still quite disturbing and could be misunderstood by the user to be a database corruption.
Comment 1 Myriam Schweingruber 2009-08-14 20:20:06 UTC
Created attachment 36153 [details]
Screenshot with double entries in the collection browser
Comment 2 Jeff Mitchell 2009-08-14 20:52:50 UTC
Yeah, I know. This isn't database corruption, but I don't know what it is -- I'm not really experienced with Model/View and TBH can't really follow the Collection Browser code, at least when I've looked at it so far. So not sure what the issue is. Someone more experienced with Model/View should probably be browbeaten into looking at it.
Comment 3 Bart Cerneels 2009-08-14 22:03:04 UTC
The double entries in the "Saved Playlists" are normal if they were imported into the database before, now they are imported to the PlaylistFileProvider (i.e. loaded directly).
The way to solve this for you is deleting all of them and doing a rescan.
Comment 4 Jeff Mitchell 2009-08-14 22:17:20 UTC
Unfortunately this doubling also happens a lot with normal tracks/albums.

In some cases I believe some also disappear when they shouldn't, and Amarok has to be restarted for them to come back.
Comment 5 Myriam Schweingruber 2009-08-17 11:22:42 UTC

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