Summary: | baloo reindexes files with date of 0 or prior to UNIX epoch on every restart | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | skierpage <skierpage> |
Component: | general | Assignee: | baloo-bugs-null |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | dschridde+kde, nate, nilskemail+kde, tagwerk19 |
Priority: | NOR | ||
Version: | 5.94.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=438074 | ||
Latest Commit: | Version Fixed In: |
Description
skierpage
2022-06-29 03:42:18 UTC
Can confirm Checked with F35 with BTRFS and an NTFS3 (the new Paragon code) mounted disc. The test files reindexed with each "balooctl check". Checked with Neon Unstable with ext4, ditto. The test files reindexed with each "balooctl check". Good catch :-) Just to make sure, baloo treats a file modified at the year 2038 "rollover" touch -m --date=2038-01-19T03:14:08Z $HOME/file_from_epochalypse.txt as it should... ... when the signed 32 bit count of seconds since 1970 "goes negative". Checked as above on ext4, BTRFS, NTFS3 I enabled baloo logging and restarted baloo, and baloo reindexed a bunch of files with the same modified times in 1970-0-01 (1969 in my timezone). The journal included lines like ... baloo_file[21819]: kf.baloo: "/home/spage/programs/skrooge_dev/skrooge/flatpak_build-dir/files/share/doc/HTML/en/skrooge/dashboard_report.png" mtime/ctime changed: 0 / 1675907011 -> 28800 / 1675907011 I think this is saying baloo thought the file's mtime was 0 and now thinks it's 28800, so it reindexed. My timezone is PST -0800, which is 28,800 seconds before GMT. baloo appears to not handle the timezone here, although `balooshow` does display the correct localtime (with no timezone) for recently updated files If I manually call for reindex with `balooctl index /path/to/1970_file`, the command prints Skipping: /home/spage/programs/skrooge_dev/skrooge/flatpak_build-dir/files/share/doc/HTML/en/skrooge/dashboard_report.png Reason: Already indexed I don't know if this skip happens when baloo thinks it needs to reindex these files. |