Bug 69881

Summary:	Bad: Segmentation fault
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <bugzilla>
Component:	rpm	Assignee:	Jeff Johnson <jbj>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
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:	2002-07-26 00:03:18 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 2002-07-25 22:53:49 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530

Description of problem:
Accidentially deleted /usr/src/linux02.4.18-5/ before removing the files inside
with "rpm -e kernel-source"
Tried to rpm -e kernel-source afterwards, and get a "segmentation fault".
I've tried rpm -e --justdb with the same results.
even rpm -ivh or -Uvh result in the same seg fault.  I've also tried rpm
--rebuilddb thinking the problem might be there.
The only thing that doesn't seg fault when dealing with that rpm file is "rpm
--verify"  that just shows all the files as "missing".

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.rm -r /usr/src/linux-2.4.18-5
2.rpm -e kernel-source
3.
	

Actual Results:  Segmentation fault

Expected Results:  kernel-source rpm should have been removed from the rpm database.

Additional info:

RPM version 4.0.4

Comment 1 Jeff Johnson 2002-07-25 23:51:10 UTC

What happens if you do rpm --rebuilddb?
Please add -vv to your erase command as well.

Comment 2 Jeff Johnson 2002-07-25 23:53:26 UTC

Sorry, I overlooked that you've tried --rebuilddb.

If you give me a pointer (i.e. a URL, attachments won't work)
to a tarball of your database
	cd /var/lib
	tar czvf /tmp/rpmdb.tar.gz rpm
I'll see if I can get you a fix.

Comment 3 Need Real Name 2002-07-26 00:03:12 UTC

I did a Microsoft-standard fix..  I rebooted the server and all is well.  I
could try to do the same thing again and see if it seg faults again if you want.

Comment 4 Jeff Johnson 2002-07-26 14:00:37 UTC

No, please don't :-) But reopen the bug if the
problem reoccurs.