Summary: | pam RPM update segfaults | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | zbeckman |
Component: | rpm | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | Keywords: | Security |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-12-10 17:58:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: |
Description
zbeckman
1999-12-10 02:54:00 UTC
What version of rpm (rpm --version)? If 3.0.4, try rpm-3.0.2. You should also do a "rpm --rebuilddb" to insure that the seg fault is due to data from a corrupted database. I presume you mean "is NOT due to"... |