Bug 198664

Summary:	"Organise Files" causes tracks to be lost from the collection
Product:	[Applications] amarok	Reporter:	Michael Liddle <michael>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	2.1.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Michael Liddle 2009-07-02 17:18:19 UTC

Version:           2.1.1 (using 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) "release 139", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.20-0.4-default

When I run Organise Files on a set of tracks (say by right-clicking on an album) the renaming is successful (i.e. the files move), but they disappear from the collection until I run an "Update"

Comment 1 Myriam Schweingruber 2009-07-08 13:31:57 UTC


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

Comment 2 Michael Liddle 2009-07-08 13:56:15 UTC

Presuming that you know more than me, then no problems with this bug being marked as a duplicate.

But just in case there's been a misunderstanding (the problems don't sound exactly the same), in my case, the move itself works fine: i.e. _no data was lost_. But just the entry in the collection browser (i.e. presumably the DB too). Running an "Update collection" finds the moved files in their new location.

Comment 3 Myriam Schweingruber 2009-07-09 17:35:37 UTC

Well, then it is indeed not a duplicate, and not even a bug. Removing files from a physical location to another one of course needs an update of the collection, don't you think? I don't know of any database that can guess where files are moved to unless you tell it to rescan the folders.

Comment 4 Michael Liddle 2009-07-09 18:19:18 UTC

Er, but the move is caused through the "Organise Files" action. I.e. Amarok does the move. I really think that this is a bug.

Comment 5 Myriam Schweingruber 2009-08-13 10:46:35 UTC

This is a duplicate nonetheless. I wonder how this ended up as "verified".

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