Comment 14 for bug 37346

Okay, this is probably several different things rolled up into one "bug" report. In reality, some of these things may be bugs, and some definitely are not.

It's important to keep in mind that when watching folders, the scanner looks at the mtimes of folders. Note that this means that changing files (and possibly overwriting files already in existence) will not trigger an update. Generally, adding or removing files to a directory is sufficient to change the mtimes of the directory.

NTFS-3G users: Your problem is most likely NTFS-3G. IIRC, for some time it did not properly update directory mtimes. I believe recent versions may have fixed this. Either way, AFAIK from a different bug report Ubuntu is about six versions behind, at 1.328. Enjoy your bugs, or pester the package maintainer to get with it already.

Everyone else: I can't reproduce this, because it works fine on all of my computers. So what you need to do is use stat to take a look at the mtimes of the directories and compare them to those stored in the database.

SQLite users: Run sqlite3 on ~/.kde/share/apps/amarok/collection.db, then run "select * from directories;"
MySQL users: Use your Amarok database, and the same thing: "select * from directories;"

The numbers indicate the time since Unix epoch. You can copy and paste the directories' stat mtimes into date as such:

date -d "2007-04-20 03:38:25.000000000 -0400" +%s

to get a number for comparison.