Bug 138666 - additional collection directory ignored
Summary: additional collection directory ignored
Status: RESOLVED INTENTIONAL
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-11 10:14 UTC by richlv
Modified: 2008-06-15 16:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description richlv 2006-12-11 10:14:46 UTC
Version:           svn 612366 (using KDE KDE 3.5.4)
Installed from:    Slackware Packages
OS:                Linux

i had a single directory marked as a source for my collection. it was a remote nfs share, had a device id 8.
i wanted to add another directory, this one resides on the local hdd, having device id 1.
this directory is marked in collection setup and listed in amarokrc section [Collection Folders].
there's also section named [Collection] in amarok rc - it has a parameter "Collection Folders", which lists only the old location (and a full path to it as if not using dynamic collection) - might be left over from previous amarok versions without dynamic collection.

"dcop kded mediamanager fullList" lists both devices fine.

i've tried restarting amarok, "touch"ing subdirectories in the local collection directory and running "update collection" - amarok does not even notice that the directories have changed.
local filesystem is ext3.
Comment 1 richlv 2006-12-11 10:17:06 UTC
damn. missed the problem itself :)
no files from the local directory appear in the collection browser, there are no entries in amarok.tags with device id 1.

i haven't yet tried a full rescan, which is quite slow because of the nfs part of the collection.
Comment 2 Maximilian Kossick 2006-12-11 14:20:01 UTC
You'll need a full rescan for Amarok to pick up your local files. The problem is the way the incremental scan works. It will just check directories for changes which were previously included in a full rescan.
Comment 3 Maximilian Kossick 2006-12-11 14:25:24 UTC
I forgot: there should be a way to cheat if you don't want to start a full rescan. Add a row for each of your local directories to the DIRECTORIES table in your database. Setting the changedate column to something low, like 1, for each of the new rows and then starting an incremental scan should make Amarok detect your local files. But make a backup of your database before you try it. I didn't actually test this.
Comment 4 richlv 2006-12-11 14:30:58 UTC
oh. i suppose i'll do a full rescan then - just to be sure that my db is in a more or less safe state :)

btw, is it technically unfeasible to make amarok pick up new directories without a full rescan ?
maybe this could be set to a wish item or something.
Comment 5 Fabian Zeindl 2007-11-23 18:43:25 UTC
I think this behaviour is very frustrating for users. It's not intuitive at all and destroys all my attached coverart etc. 

:-(
Comment 6 Fabian Zeindl 2007-11-23 18:45:00 UTC
So why is this WONTFIX?
Comment 7 Fabian Zeindl 2007-12-29 10:47:48 UTC
Hello?
Comment 8 Seb Ruiz 2007-12-29 13:28:23 UTC
If you read the previous comments (#2 to be precise) you would know. Please stop the harassment.
Comment 9 richlv 2008-01-02 11:01:29 UTC
would a new behaviour in amarok2 be possible, where collection directory setup changes would be detected and the new directories forced for a full scan after confirming the changes (in the setup) ?
Comment 10 Fabian Zeindl 2008-01-04 15:12:43 UTC
I read the comments and I understand that it's not easily possible at the moment. Nevertheless I don't think this issue should be stay like that forever in the next ten versions of amaroK. Therefore I don't understand why the bug is closed.
Comment 11 Fabian Zeindl 2008-01-05 19:10:08 UTC
How about marking this as LATER instaed of WONTFIX?