Bugzilla – Bug 150604
Beagle search spins forever
Last modified: 2006-03-06 22:34:36 UTC
This is not a very good bug report, because all I can say is it does not work. I ran beagle after wondering why .beagle was so huge. Searches in the "chats" section work fine. But all others hang beagle with a busy (clock) icon. I'd run it under gdb, but: Running best from the command line gives: Rendering Done Rendering: .94s ** (best:15710): WARNING **: Binding 'F12' failed! If you're wondering whether Best is working check your notification area (system tray) And no gui appears. beagle-query from the command line sort of works, but has lots of small problems.
Probably deleting the cache file will help. I don't know but maby the size should be limited.
Assuming its the old best interface.
Yeah, the old interface has been replaced with a more reliable one called beagle-search for 10.1. Your ~/.beagle directory may be large because of the indexes, but it may also be large because we're keeping around verbose log files so we can track down bugs. (Beagle is still considered beta.) You might find some information on why searches aren't working in there; any info you can attach would help. Can you describe the problems beagle-query is giving you?
Deleting the cache resolved the hang issue -- for now. bryce@linux:~/cvs/ccs/denali> best --version Gnome best 0.0 Problems: beagle-query "baby food" found the words, not the phrase. No man page to figure out how to do a phrase search. Documentation on --source option wrong, not to mention awkward if true. beagle-status uselsss, and hard to read since it repaints screen. All in all, seemed pretty rough. --- While I'm at it: there are four categories of files on my drive: 1) Personal 2) Cache (thumbnails, mozilla web page cache, imap cache but not imap flags) 3) System files I've never modified. 4) Log files. I can skip backing up #2 and #3, and in many cases #4 -- but it can be hard to indentify what's what. Beagle blurs the line even more. It would be great to have some equivalent of /tmp in userspace which contains files that don't need backing up (because they can be recreated on demand).
The shell escapes quotation marks, so you may need to do something like: beagle-query '"baby food"' to get the phrase. Man page is a fair point, I'll look into adding that. --source searches are fixed in newer versions, which will ship in 10.1 (or can be downloaded and built from the beagle site) Ditto for beagle-status; you can get one-off status by running beagle-info --status. As for the tmp stuff, I don't think Beagle is particularly any different than other stuff like Evolution which maintains huge caches in ~/.evolution. Local stores are kept there, yes, but most of the configuration is done within GConf. A user-specific temp directory might be useful for stuff like that, but speaking specifically to Beagle, you should be able to set the BEAGLE_STORAGE directory to say where to store the beagle index info, but that hasn't been heavily tested.
The shell escapes "? News to me: > perl -e 'while($arg = shift @ARGV) { print "$arg\n" }' "one" "two words" "blue words food words" one two words blue words food words The arguments in "" come in as a single argument. beagle-query "'test word'" also searchs for test and word separately.
Ah, you're right, we weren't quoting them correctly before passing them onto the daemon. Fixed in CVS.
Submitted fixes to these to STABLE.