Hi ! On a clean KDE Neon install (non-LTS), I finally decided to turn indexing on. It used to be way too slow and got really usable thanks to an SSD. The "timeline" feature is pretty useful. MY ISSUE IS THE FOLLOWING : timeline:/today frequently yields strange results while the former entries are correct as far as I can tell (yesterday, this month etc.) timeline:/today always shows a specific file that was created months ago. And (more tests required on my part) doesn't reflect new files for a while. FOR INSTANCE : it's 0:46 am. I created quite a few files that were instantly indexed by baloo and appear in search results. However, they do not appear in timeline:/today. Instead, the very same old file appears and is the only one on the list. I'm well aware the scope of this "bug" is potentially very wide and its description pretty vague. I'm clearly willing to investigate more if someone can give me some directions :-) Cheers
More details : - so at the beginning of the day the only present file in today's timeline was an OLD jpeg picture - when downloading / duplicating other jpg files, none would appear in the timeline even though they were in the baloo database (so only the file specified above would still appear) - I figured out that when creating a text file (or downloading a video file) it would instantly appear in today's timeline (so there's something filetype related -- but I do have a jpg picture in yesterday's timeline) - and then it would remove the aforementioned old picture file fixing the bogus entry issue (until tomorrow :-)
(In reply to Mahendra Tallur from comment #0) > MY ISSUE IS THE FOLLOWING : timeline:/today frequently yields strange > results while the former entries are correct as far as I can tell > (yesterday, this month etc.) > ... when downloading / duplicating other jpg files, none would appear > in the timeline even though they were in the baloo database > ... then it would remove the aforementioned old picture file fixing the > bogus entry issue (until tomorrow :-) So, you get given an entry in timeline:/today that you had not modified (or changed its metadata) today. If you wait a day, that file doesn't appear under "yesterday" in the timeline. You can download/copy .JPG's and baloo indexes them but these don't appear in the timeline. Sounds somehow like a caching issue within Dolphin or timeline.so. In the case that you still see the issue (it's a long time ago and there've been a load of baloo bug fixes :-), check the details of the file on the filesystem and compare to the data that baloo has extracted. First stat strangefile.jpg which will show the date/times when the file was modified plus when the filesystem metadata was changed (normally the same, but "changed" would show when you've changed permissions or added any tags) Compare these to the dates/times from balooshow -x strangefile.jpg The modified/changed times ought to be the same. The two commands also show the device number/inode for the file. These also should match (otherwise baloo has more than one entry in it's database for the file, and much confusion may ensue...). It is also possible to check whether baloosearch gives more than one result for baloosearch strangefile.jpg There has been a fix where baloosearch returned blank lines, Bug 431664, that confused krunner. Who knows... I'll flag this as "Needsinfo" in case anyone is listening 8-)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!