Created attachment 230513 [details] A more detailed screenshot from 01:32 on the 25th % pkg info -x recoll recoll-1.31.2 % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #118 main-n251923-4bae154fe8c: Sat Dec 25 08:03:37 GMT 2021 root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 1400045 1400045 % Recoll 1.31.2 patched for bug 260093. Observations ============ After using Spectacle to save a screenshot on Christmas day (around 01:15 on the 25th), I realised that Recoll could not find the name of the file: <https://i.imgur.com/39DnI38.png> Later results of a variety of searches for files within the same directory showed that the directory appears to be only partially indexed. Initial assumption ================== A corrupt index From bug 260162 comment 0: > Update version from 1.31.2 to 1.31.4. See changelog > > https://www.lesbonscomptes.com/recoll/pages/release-1.31.html Amongst the notes: > Linux/Mac: Bug in threads management could result in index > corruption or crash after signal interrupt.
Created attachment 230514 [details] Screenshot: an example of a found item within the same directory For this particular directory: it seems that some items are indexed, some not. I'm tempted to stop indexing, then rebuild. I can as easily await the update to 1.31.4 or 1.31.5 before a rebuild. (I assume that an update from 1.31.2 to 1.31.4 or greater will not automatically fix corruption …)
Now that 1.31.4 has landed, can we verify this corruption is fixed?
Created attachment 231591 [details] Screenshot: an item found by Recoll very soon after a save by Spectacle (In reply to Fernando Apesteguía from comment #2) Not reproducible, thanks. To be honest, I _might_ have opted to rebuild the index before 1.31.4 became available. My memory of this is fuzzy.