GNOME Bugzilla – Bug 419648
Some results (file) are not listed any more
Last modified: 2007-03-21 21:56:44 UTC
This is a very strange behaviour: some files I have in my home, were indexed and were listed when I search for them. After a while they are not listed any more, even they were neither moved or modified. It only occurs with files: all the other objects are correctly listed. Unfortunately I don't know how to reproduce it, but you can ask me for any further information. My OS is Ubuntu Edgy Eft, and I'm using Beagle 0.2.16 from Beagle-Project.org repository. Regards, Michele C. S.
Can you attach the tarball of ~/.beagle/Log ? If it is too large, then the log files of Beagle and IndexHelper running during this incident is what I am looking for. The name of the log files would give you the time when it was created.
At the following link you will find the last two days log: http://media9.filewind.com/g.php?filepath=4504 In the last two days the problem _DID_ occur: a directory was listed one day and the day after, after rebooting, it was not. Thanks.
The problem happened due to the following files which made the indexer go into an infinite loop: file:///mnt/space/michele/Backup/Altro/SAVE/Altro/raffolina/Impostazioni locali/Temporary Internet Files/Content.IE5/OT2JOXQN/ UNIKO%2520P4%252012C[1].jpg and file:///mnt/space/michele/Programmi/Windows/Windows Vista Local KMS Activation Server.tar.gz The problem with the jpg is probably fixed in svn trunk. The http://beagle-project.org/files/ubuntu/edgy should have an updated edgy bugfix backport (0.2.16.3) but I dont see it there. I will ask edgy packager. I dont know about the "Windows Vista Local KMS Activation Server.tar.gz". Possibly it contains something which is causing the problem. Could you run $ beagle-extract-content "/mnt/space/michele/Programmi/Windows/Windows Vista Local KMS Activation Server.tar.gz" to see what it does ? If its not a problem, can you attach / email me the tar.gz file (and also the jpg file, just to make sure) ? Thanks.
Upon personal communication, I found out the problems were being caused by a jpg file that was causing 100% loop which prevented proper shutdown of beagled. This lead to purging of the index in the next run. I believe this should be fixed with 0.2.16.3 (updated packages in the beagle-project.org repo). Please reopen if the problem persists.