https://bugs.kde.org/show_bug.cgi?id=490484
--- Comment #74 from Maik Qualmann <metzping...@gmail.com> --- There are different depths of scanning, the option "Rescan file when files are modified" will do a full scan as if the file is unknown to capture all changes. Without this option, the scan will not be as deep, just file date and size or similar. When metadata is written, we need to rescan the file as the file size changes and the unique file hash needs to be updated in the database. Otherwise, this process would only take place at the next start when the initial scan is active. In the meantime, the database would not be in sync with the files, e.g. an incorrect file size would be displayed in the GUI, etc. Maik -- You are receiving this mail because: You are watching all bug changes.
