Version: 1.4.4 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux The ScanController keeps on detecting mtime changes on various directories. This is because I had my collection mounted both through samba and nfs. The samba share is currently disabled, nfs is in use. However,in the postgres database there are multiple devices (devices table in postgres db) that carry the same collection. In the directories table the same entries come back with different device ids and slightly different paths: ./collection/mp3/something with deviceid 2 and ./mp3/something with deviceid 4 these entries refer to the same directory, but with different mount methods. Only one (nfs, deviceid 2) is actually active, the other is not mounted at the time). Both directory entries have different changedate (mtime) entries. The one corresponding to the nfs device is correct, the other is stale. The scancontroller doesn't take deviceid into account and thus triggers on the directory entries that belong to the unmounted samba share. However, the mtime entry for the unmounted device does not get updated. Therefor, the next run of scancontroller triggers the same directories to be scanned again and again and again. Another side effect is amarok shows double entries for the affected directories. Suggested fix: also check if the deviceid is actually mounted in the scancontroller. kind regards Tim Froidcoeur
I think http://bugs.kde.org/show_bug.cgi?id=113927 is an entry for the side effect of having duplicate entries in the collection.
*** Bug 143065 has been marked as a duplicate of this bug. ***
I have this problem too. Any ideas? Console output constantly says that 5 specific dirs were changed which is nonsense. My collection is on XFS so no Samba or NFS is involved.
In my case amarok is constantly scanning the collection folders even if the folder are untouched or if amarok is idle. The filesystem is ext3 Plus it seems that amarok creates new copies of the file if it contains latin symbols (ñ,Ñ, ó, í, etc) by appending weird symbols. For example (filename.mp3, filenameWeirdSymbols.mp3, filenameWeirdSymbolsWeirdSymbols.mp3 and so on).
Correct me if I am wrong but this should be close becouse 1.4 branch of amarok is not maintained any more?
Yes indeed, Jonas. Amarok 1.x is no longer maintained, so I'm closing this report.