Bugzilla – Bug 118203
beagled locks up indexing an smb mounted directory
Last modified: 2005-10-17 12:52:01 UTC
When I run w/o smb mounts under home (/home/jrobiso2/W and Y) beagled and best run great. When I run with those directories mounted, beagled will stall, and best will lock up (no results, screen gui fails to update image, etc.) Both current-Beagle and current-IndexHelper show System.NullReferenceException: Object reference not set to an instance of an object. The IndexHelper appears to go PAST the error (at least the log shows another +file entry), but beagled itself does not go past it. When stuck, beagled still responds to beagle-info, etc. (of course beagle-info shows the same item being worked on, over and over). I will attach current-Beagle and current-IndexHelper
Created attachment 50533 [details] current-Beagle file from the lockup
Created attachment 50534 [details] current-IndexHelper
This little lockup also causes a total corruption of the "Files" data, requiring a rm -rf .beagle/Indexes/FileSystemIndex and thus a re-indexing.
I just fixed this problem upstream. It's not directly related to using smb, it can happen in any circumstance. http://mail.gnome.org/archives/dashboard-hackers/2005-September/msg00114.html
Created attachment 50545 [details] CVS patch to fix the problem This is diffed against the 0.0.13.2 tag in CVS. I'm not sure what kind of mess of patches we have in there now, but I think this will apply.
How are we on timing to ensure this gets into Gold? I know we're probably too late for RC3, (or RC4 . . . I heard there was one this time).
It was too late for gold. AJ, we'd like to ship this with the update for bug 117362 and bug 116372 Use the same swamp ID?
Ok, to ship with the other updates. Btw. since it's one submission, you have to use the same swamp ID.
released
closing