Bug 118203

Summary:	beagled locks up indexing an smb mounted directory
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Jonathon Robison <jrobiso2>
Component:	GNOME	Assignee:	Joe Shaw <joeshaw>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P1 - Urgent	CC:	aj
Version:	RC 1
Target Milestone:	---
Hardware:	i686
OS:	All
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	current-Beagle file from the lockup current-IndexHelper CVS patch to fix the problem

Description Jonathon Robison 2005-09-21 11:36:25 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

Comment 1 Jonathon Robison 2005-09-21 11:37:37 UTC

Created attachment 50533 [details]
current-Beagle file from the lockup

Comment 2 Jonathon Robison 2005-09-21 11:37:59 UTC

Created attachment 50534 [details]
current-IndexHelper

Comment 3 Jonathon Robison 2005-09-21 11:41:13 UTC

This little lockup also causes a total corruption of the "Files" data, requiring
a rm -rf .beagle/Indexes/FileSystemIndex and thus a re-indexing.

Comment 4 Joe Shaw 2005-09-21 15:35:07 UTC

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

Comment 5 Joe Shaw 2005-09-21 15:38:22 UTC

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.

Comment 6 Jonathon Robison 2005-09-21 15:48:34 UTC

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).

Comment 7 JP Rosevear 2005-09-29 17:03:10 UTC

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?

Comment 8 Andreas Jaeger 2005-09-30 07:59:34 UTC

Ok, to ship with the other updates.

Btw. since it's one submission, you have to use the same swamp ID.

Comment 9 Anja Stock 2005-10-17 12:51:16 UTC

released

Comment 10 Anja Stock 2005-10-17 12:51:37 UTC

closing