Bug 191199

Summary:	Tags missing when collection location is unmounted and amarok is started
Product:	[Applications] amarok	Reporter:	Nikhil Marathe <nsm.nikhil>
Component:	Collections/Local	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED FIXED
Severity:	normal	CC:	ashl1future, cycoone, jan, jithin1987, mitchell
Priority:	NOR
Version:	2.1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nikhil Marathe 2009-05-01 04:51:30 UTC

Version:           2.0.90 (using KDE 4.2.2)
OS:                Linux
Installed from:    Unlisted Binary Package

My collection is on an NTFS partition mounted using ntfs3g and fuse.ntfs

Sometimes the ntfs partition is marked for checking and remains unmounted. If I start Amarok, it shows the entire playlist as one single list without information and can't play it. Which is perfectly fine.

But if I fix the filesystem and remount it, then start Amarok, it refuses to fix the issue even though all the files are available now. All tags and metadata continues to be missing although I can play the files.

The only way to fix this is to just delete all the amarok related configuration files and collection and recreate the playlist, which can be really really annoying.

The expected behaviour is that the playlist is refreshed and recategorized.

Comment 1 Alexey Shildyakov 2009-06-22 17:36:56 UTC

Ok. Please tell us, if you only rescan collection information are missing too? Or after rescan (you mustn't delete configuration folder) collection is OK?

Comment 2 Nikhil Marathe 2009-06-22 17:42:59 UTC

I tried some more things. The collection doesn't have to be deleted manually but the process is still tedious.

1. Uncheck my music folders from the collection. Let amarok scan empty. Then restart amarok.

2. Check the music folders again. Let is scan collection. Restart amarok.

3. Now load the playlist. Then all the tags and so on are fine and the playlist is displayed properly

Thanks.

Comment 3 Alexey Shildyakov 2009-06-22 17:49:51 UTC

Ok. It's better then delete configuration directory but I think it's not a solve for this problem. Lets wait if anybody confirm you bug.

Comment 4 Myriam Schweingruber 2009-06-22 22:28:22 UTC

Nikhil, you should upgrade to Amarok 2.1, or even 2.1.1 it has been released quite some time ago.

Comment 5 Nikhil Marathe 2009-06-23 05:37:42 UTC

yes, i did upgrade to 2.1.0, bug still persists. I haven't tried 2.1.1 though

Comment 6 Myriam Schweingruber 2009-07-10 18:08:23 UTC

Changed status to confirmed.

Comment 7 Myriam Schweingruber 2009-07-10 18:47:36 UTC

*** Bug 192114 has been marked as a duplicate of this bug. ***

Comment 8 Stephen Baker 2009-07-13 05:14:43 UTC

I don't think Bug 192114 is a duplicate of this one.  In that bug the tracks would play if you hit play after each track.  In this one it appears that they do not play at all until you refresh the collection.

Comment 9 Nikhil Marathe 2009-07-13 08:01:48 UTC

the tracks play once the partition is remounted. But the id3 tags are not refreshed, so the entire playlist is sorted under one album/artist, and the filenames are shown as titles. And I have to refresh the collection multiple times before it gets all the tags right.

Comment 10 Myriam Schweingruber 2009-07-30 08:54:58 UTC

*** Bug 201911 has been marked as a duplicate of this bug. ***

Comment 11 Jithin Emmanuel 2009-07-30 10:13:35 UTC

I can confirm this one. My collection itself was gone and playlist all flat with no grouping and time 0

Comment 12 Myriam Schweingruber 2009-11-04 00:43:03 UTC

Is this still valid with current git?

Comment 13 Jeff Mitchell 2009-11-04 03:27:10 UTC

(In reply to comment #9)
> filenames are shown as titles. And I have to refresh the collection multiple
> times before it gets all the tags right.

Refresh how? If you mean that you have to rescan the collection multiple times, what you really need to do is quite and reopen Amarok after the first scan. The collection browser not refreshing properly after a scan is a longstanding bug.

Comment 14 Myriam Schweingruber 2009-11-16 14:00:24 UTC

This should be solved in Amarok 2.2.1, besides the bug mentioned in comment #13