First, I want to check if its ok to keep posting errors to the mailing list on the most current CVS build, I am reluctant to file them with the bugzilla since we are talking about a bleeding edge release. (Well, not even a release really) With that said, I'm gonna throw these 2 little bugs out there. 1) It appears that wvglue struggles with oddly formatted MS-Word Documents. The document linked here ( http://kubasik.net/Calendar0506.doc ) caused the beagle daemon to continue to 05-09-11 02.56.08.85 00463 Beagle DEBUG: *** Add '/home/kevin/Documents/AP CompSci' 'Calendar0506.doc' (file) 05-09-11 02.56.08.95 00463 Beagle DEBUG: *** Add '/home/kevin/Documents/AP CompSci' 'Calendar0506.doc' (file) 05-09-11 02.56.09.21 00463 Beagle DEBUG: *** Add '/home/kevin/Documents/AP CompSci' 'Calendar0506.doc' (file) 05-09-11 02.56.09.32 00463 Beagle DEBUG: *** Add '/home/kevin/Documents/AP CompSci' 'Calendar0506.doc' (file) 05-09-11 02.56.09.77 00463 Beagle DEBUG: *** Add '/home/kevin/Documents/AP CompSci' 'Calendar0506.doc' (file) 05-09-11 02.56.09.88 00463 Beagle DEBUG: *** Add '/home/kevin/Documents/AP CompSci' 'Calendar0506.doc' (file) 05-09-11 02.56.09.96 00463 Beagle DEBUG: Thottling immediate priority tasks 05-09-11 02.56.11.46 00463 Beagle DEBUG: Thottling immediate priority tasks 05-09-11 02.56.11.62 00463 Beagle DEBUG: *** Add '/home/kevin/Documents/AP CompSci' 'Calendar0506.doc' (file) over and over until the daemon was halted an restarted. the output of wvText does not strip down to just text, but instead has lots of 'text table' formatting +-------+ | | | | +-------+ Which might be giving Lucene some problems, but what seems more likely as I think about it is wvglue is triggering inotify. Perhaps beagle should keep a history of all events thrown in the last second and ignore duplicates? I am new to the code and still have a very shallow grasp of how the beagle classes fit together, but it doesn't seem impossible. 2) This one might be more of a system specific issue, but I add it because I can't tell if the wiki is up to date (as some articles are not) On debian unstable (my current system) dbus 0.2* is a dependency of gnome, in short it must be installed, and dbus 0.34 is available, but listed as a conflict with 0.2 (for obvious reasons) best seems to be having problems communicating with beagled (when I issue a query through best, beagles debugging output does not show that it its querying Lucene, and best hangs on 'Rendering', while showing a number of files found in the lower left corner) So, does Best/Beagle require the newest dbus? if so, should/can this be added to the configure script. I thought I had read that a sans-dbus workaround had been submitted to the cvs, but I could be wrong. The only error that I am seeing in the debug logs is ** (beagled:6540): WARNING **: _wapi_connect: Need to translate 2 [No such file or directory] into winsock error DEBUG: Caught ResponseMessageException: System call failed which I have always seen (even when beagled/best where working fine) I hope this helps Cheers, Kevin Kubasik
Attachment:
signature.asc
Description: This is a digitally signed message part