GNOME Bugzilla – Bug 334055
beagle-query not returning all indexed files
Last modified: 2006-09-22 09:46:23 UTC
Please describe the problem: beagle-query failes to return results for files that are indexed. In my case a certain query to beagle will return 8 results. The same query using Nautilus with beagle-integration returns all expected results which is ~100 items. Running beagled --fg --debug error messages like the ones below appears. Perhaps related to filenames starting with a '0'. I've created an attachment with the complete list of errormessages for a particular query. However it's a "if error then '0'" relationship and not the converse since the query sucesfully returns: file:///home/bh/media/pictures/Kenya1/096 Mara.jpg file:///home/bh/media/pictures/Kenya1/097 Mara Lions.jpg file:///home/bh/media/pictures/Kenya1/098 Mara.jpg file:///home/bh/media/pictures/Kenya1/099 Mara.jpg file:///home/bh/media/pictures/Kenya1/101 Mara.jpg file:///home/bh/media/pictures/Kenya1/100 Mara.jpg file:///home/bh/media/pictures/Kenya1/058 Mt Kenya.jpg file:///home/bh/media/pictures/Kenya1/059 Mt Kenya.jpg ============== debug info ===================== Debug: Couldn't find path of file with name '081 Mt Kenya Coming back.jpg' and parent 'p2pt2b75RkGli3LsaTjHOw' Debug: Couldn't find path of file with name '082 Lake Nakuru.jpg' and parent 'p2pt2b75RkGli3LsaTjHOw' Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Yes Other information: Ubuntu dapper dev. Sqlite3 Beagle-cvs
Created attachment 60996 [details] Complete debug-info Extended debug-info to the original bug-report
Created attachment 60997 [details] Complete debug-info Extended debug-info to the original report.
Can you attach the output of "getfattr -d /home/bh/media/pictures/Kenya1" and "getattr -d /home/bh/media/pictures/Kenya1/082 Lake Nakuru.jpg" ? (You will probably need to add quotes to get it to do the spaces correctly) Also, if you create a new directory and copy those files to that new directory, wait for them to be indexed, and then search, do any get missed from the new directory? I'm not having much luck trying to duplicate this one myself. It would also be good to check the logs when you do this to see if you see any errors while indexing.
Here ya' go. I'll do the reeindexing-thing and doublecheck my logs "soon" :) bh@lifebook34:~$ getfattr -d /home/bh/media/pictures/Kenya1 getfattr: Removing leading '/' from absolute path names # file: home/bh/media/pictures/Kenya1 user.Beagle.AttrTime="20060309192039" user.Beagle.Fingerprint="02 W2q0E2LB7UiGgdbC8_iK+A" user.Beagle.MTime="20060309192039" user.Beagle.Uid="ek1AyL1BYEaPe6Qhcw0FuA" bh@lifebook34:~$ getfattr -d '/home/bh/media/pictures/Kenya1/082 Lake Nakuru.jpg' getfattr: Removing leading '/' from absolute path names # file: home/bh/media/pictures/Kenya1/082\040Lake\040Nakuru.jpg user.Beagle.AttrTime="20060308173203" user.Beagle.Filter="003 Beagle.Filters.FilterJpeg" user.Beagle.Fingerprint="02 W2q0E2LB7UiGgdbC8_iK+A" user.Beagle.MTime="20060308173125" user.Beagle.Uid="ad6HUi7E_kCsAgX3NNoPdA"
Ok, problem is gone for me now. Initially I tried moving/copying a single file to a new directory. This caused an exception, see the attached logs. Then I tried again, and this time the file was succesfully indexed. So I moved the entire directorycontents back and forth which caused all files to index correctly. Perhaps f-spot messed up things? I'm using f-spot to write metadata to files.
Created attachment 61005 [details] debug-info
I doubt it's F-Spot related. It has a fallback to gracefully handle errors, and the other report sent to dashboard-hackers was mp3s, not images. I think there is something else going on here. I'm just not sure what yet.
Bjørn, do you still see this problem? I can't get this to happen for me, unfortunately.
(In reply to comment #8) > Bjørn, do you still see this problem? I can't get this to happen for me, > unfortunately. > It's been a while since I've last seen it, but occasionally it does occur. Though admittedly I never really could reproduce it... So I donno what to say except from, uuhhmmmmm?????????
It's possible this was caused by the same thing as bug 354161, which I've just fixed in CVS. Can you keep an eye out for this with post-0.2.9?
Still haven't heard anything, changing to NEEDINFO
I haven't seen this in a very long time (and many versions ago). Since I'm the only reporter on this particular bug, I'll just close it.