Bug 197044

Summary:	Rescanning after removing/adding directories breaks collection
Product:	[Applications] amarok	Reporter:	simon
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	steep86
Priority:	NOR
Version:	2.2-SVN
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description simon 2009-06-18 18:38:18 UTC

Version:           2.2-SVN (using 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.30-rc6-git3

hi,

have no idea why, but collection scanning works with quite random results:

for a testcase i deleted the whole mysqle dir + scan files + amarokrc collection setup entry and played around with just two directories, one containing a compilation and the other containing a normal album.

to reproduce: i marked the folders in the "setup collection" dialog and pressed apply (not "rescan button") to do a rescan.

- select album 1, apply, all ok
- select collection 1, apply, all ok
- deselect album 1, apply, broken: VA node with the removed albumname +cover and no children, collection trackcount shows tracknumber of compilation
- rescan (full), still broken

- restart amarok: compilation fine.
- select album 1, apply, broken: VA node gone, entry for each artist in compilation, no added album

- restart amarok: album fine, compilation still broken (cover, year+ title of album, single tracks for each artist)

- deselect album 1, apply, album ok
- select compilation , apply, all ok.

- restart amarok: back to square 1 -> album fine, collection broken ...
- deselect album, apply, even more broken ( VA node with the removed albumname +cover and no children, collection trackcount shows tracknumber of compilation, see above)


ok, at this point i just decided to drink beer.
cheers

Comment 1 Emanuele 2009-06-24 14:56:21 UTC

(In reply to comment #0)
> Version:           2.2-SVN (using 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)), Gentoo)
> Compiler:          x86_64-pc-linux-gnu-gcc
> OS:                Linux (x86_64) release 2.6.30-rc6-git3
> 
> hi,
> 
> have no idea why, but collection scanning works with quite random results:
> 
> for a testcase i deleted the whole mysqle dir + scan files + amarokrc
> collection setup entry and played around with just two directories, one
> containing a compilation and the other containing a normal album.
> 
> to reproduce: i marked the folders in the "setup collection" dialog and pressed
> apply (not "rescan button") to do a rescan.
> 
> - select album 1, apply, all ok
> - select collection 1, apply, all ok
> - deselect album 1, apply, broken: VA node with the removed albumname +cover
> and no children, collection trackcount shows tracknumber of compilation
> - rescan (full), still broken
> 
> - restart amarok: compilation fine.
> - select album 1, apply, broken: VA node gone, entry for each artist in
> compilation, no added album
> 
> - restart amarok: album fine, compilation still broken (cover, year+ title of
> album, single tracks for each artist)
> 
> - deselect album 1, apply, album ok
> - select compilation , apply, all ok.
> 
> - restart amarok: back to square 1 -> album fine, collection broken ...
> - deselect album, apply, even more broken ( VA node with the removed albumname
> +cover and no children, collection trackcount shows tracknumber of compilation,
> see above)
> 
> 
> ok, at this point i just decided to drink beer.
> cheers

I have the same problem. When I add new album to my collection folder, after the collection update everything seem messed up...now every time i add new abum (or song) and avoid that problem I have to delete mysqle folder .

Comment 2 Mikko C. 2009-06-24 15:14:31 UTC

this should be now fixed in trunk.
Please reopen if not.

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