Bug 14361 - A fatal error occured: couldn't open
Summary: A fatal error occured: couldn't open
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-10-24 13:00 CEST by Barry Aulis
Modified: 2014-12-15 19:21 CET (History)
1 user (show)

See Also:
Source RPM: rpmdrake
CVE:
Status comment:


Attachments

Description Barry Aulis 2014-10-24 13:00:37 CEST
Description of problem:
Try to install new ipdates for your system and I get the above.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2014-10-24 23:05:35 CEST
"RPM DB() at/usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/open_db.pm line 74"

you can reproduce ?

I guess it was searching for updating

Keywords: (none) => NEEDINFO
Source RPM: RPM DB() at/usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/open_db.pm line 74 => rpmdrake

Comment 2 Barry Aulis 2014-10-25 01:10:48 CEST
(In reply to Manuel Hiebel from comment #1)
> "RPM DB() at/usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/open_db.pm line 74"
> 
> you can reproduce ?
> 
> I guess it was searching for updating

I discovered this bug when I had New updates are available for your system message. When I login to update the software manager gives "A fatal error occured: couldn't open RPM DB() at/usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/open_db.pm line 74". I started using Mageia last april. This is the first bug I have gotten. Should I reinstall? Thanks Barry.
Comment 3 James Kerr 2014-10-25 02:46:18 CEST
It could be due to a corrupted rpm data base. In a root terminal execute the following two commands to rebuild the data base:

rm -f /var/lib/rpm/__db*
rpm --rebuilddb
Comment 4 Barry Aulis 2014-10-25 19:30:51 CEST
The above did the job. After executing I went onto the Internet and Mageia immediately installed the new updates.
Thank you Mr. Kerr. Barry.

Just for information any idea as to why the database became corrupted?
Again Thanks Barry.
Comment 5 Barry Aulis 2014-11-02 14:54:25 CET
The suggestion by James Kerr repaired the database. Though I would like to know any reason why the database became corrupted in the first place.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 6 Al Do 2014-12-15 19:21:00 CET
I just got this error. I think it was because I Installed a printer driver from an RPM file from the vender with out using MCC. The fix from James Kerr worked for me.

CC: (none) => al_tech


Note You need to log in before you can comment on or make changes to this bug.