Bug 15691

Summary:	updatedb segfault
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <randal.leavitt>
Component:	slocate	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	7.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-08-09 00:53:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2000-08-07 23:56:50 UTC

I installed some RPMs related to "docbook" and then issued the "updatedb"
command.
It immediately reported a segmentation fault.
I then uploaded the latest rpm for "slocate" that I could find and
installed it:  slocate-2.2-1k
The problem still perisists.
A few days ago I installed the latest Helix-code version of Gnome.
So now I cannot "updatedb" and I cannot use "locate" to find newly
installed items.
Gnome provides alternatives so this is not crippling.  I just think it
should work.

I am running Red Hat 6.1 with many things updated.

Comment 1 Bill Nottingham 2000-08-08 02:04:38 UTC

Did you update to the pinstripe glibc? If you didn't,
slocate from pinstripe *will* segfault.

Comment 2 Need Real Name 2000-08-09 00:53:26 UTC

I have not changed "glibc" since I installed Red Hat 6.1.  I suspect that I do
not want to change it now since it may affect many other things in subtle ways. 
The "rpm" that I used to install the latest version of "slocate" did not object.

Comment 3 Bill Nottingham 2000-08-09 01:38:34 UTC

If you actually installed the pinstripe RPM on 6.1, that
is not guaranteed to work.

If you installed something else and can reliably reproduce
this, please re-open. A stack trace would be helpful.