Bug 21165

Summary:	Updating the medias won't work
Product:	Mageia	Reporter:	william bastian <rfarc2000>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lovaren, marja11
Version:	5	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	ALL	CVE:
Status comment:

Description william bastian 2017-06-30 15:32:33 CEST

Description of problem:
I have indication of updates available.
Click on it
enter password
 message"fatal error occurred:couldn't open RPM DB () at usr/lib/perl5.20.1/Rpmdrake/open_db.pm line74.."
It has been this way for almost a week.

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


How reproducible:every single time I try to update, when the red exclamation point shows on the bar on the bottom.  Red exclamation point is now a permanent indication on bottom of screen, every single attempt to upgrade gets the message quoted above. 
  


Steps to Reproduce:Reproduceable every single time I try to update without exception.  This has never happened in  all the years I have used Mandrake/Mandriva/Mageia.  
1.
2.
3.

Comment 1 Marja Van Waes 2017-07-01 06:34:39 CEST

the rpm database can get corrupted for many different reasons, usually for reasons outside Mageia. Running the following commands as root should fix it


  rm -f /var/lib/rpm/__db*
  rpm --rebuilddb


Please tell whether that fixes the problem for you.

CC: (none) => marja11

Kristoffer Grundström 2017-07-01 06:44:51 CEST

CC: (none) => hamnisdude
Summary: can't get updated => Updating the medias won't work

Marja Van Waes 2017-07-02 22:21:23 CEST

Keywords: (none) => NEEDINFO

Comment 2 Marja Van Waes 2017-07-08 06:26:26 CEST

(In reply to Marja van Waes from comment #1)
> the rpm database can get corrupted for many different reasons, usually for
> reasons outside Mageia. Running the following commands as root should fix it
> 
> 
>   rm -f /var/lib/rpm/__db*
>   rpm --rebuilddb
> 
> 
> Please tell whether that fixes the problem for you.

No reply, so assuming that did the trick.

Also, no one else reported this recently, so it is very unlikely that this is an exceptional case in which this is caused by a bug in a Mageia package.

Closing.

Please reopen if the problem persists.

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