Description of problem: rpm gives a segmentation fault after hang on rpm -Fvh binutils-2.13.90.0.18-6 (100 % complete, then a hang.) binutils is twice in the database rpm -qa | grep binutils gives binutils-2.13.90.0.2-2 binutils-2.13.90.0.18-6 every rpm update gives a segmentation fault Version-Release number of selected component (if applicable): rpm-4.1-1.06 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
tried rpm --rebuild, db_verify (no errors), db_dump db_load every update gives a segmentation fault for example rpm -Fvvh cvs-1.11.2.8.i386.rpm gives at the end . . ########################################### [100%] D: ========== +++ cvs-1.11.2-8 D: Expected size: 1128389 = lead(96)+sigs(344)+pad(0)+data(1127949) D: Actual size: 1128389 D: install: cvs-1.11.2-8 has 55 files, test = 0 D: read h# 645 Header V3 DSA signature: NOKEY, key ID db42a60e Segmentation fault in fact every update gives a segmentation fault
"Every install segfaults" smells like LDAP pam module. Try doing server nscd restart and repeating. If that fixes, then insure that nscd is started during boot. If that does not fix, please reopen this bug with more specific information.
I've tried a rpm --rebuilddb after deleting all files but the Packages file with nscd started, this didn't fix the problem. A db_verify didn't help either. I still think that the problem is caused by the dubbel binutils in the rpm Packages file. binutils-2.13.90.0.2-2 binutils-2.13.90.0.18-6 (all the file on my system are from the newest binutils package) rpm -qa still works fine. Every update gives a segfault, i am not able to remove one of the binutils. The only thing I can find to do is a "pretended install" to recreate a new rpm database. This looks very tricky to me.
Please give me a pointer (i.e. URL, attachments won't work) to a tarball of your database cd /var/lib tar czvf /tmp/rpmdb-86553.tar.gz and I'll verify that there is nothing wrong.
Hmmm that should have been tar czvf /tmp/rpmdb-86553.tar.gz rpm
Closing due to inactivity. If this issue still occurs with current releases, please reopen and set the release in which you've encountered the problem.