Description of problem: Three/five minutes after I start the Mageia 4.1, KDE, 64bits, the error message appears: "A fatal error occurred: unable to open rpmdb" I close that window and another message appeared with the warning:"Service configuration problem. Please check logs and send mail to support@mageiaonline.com". I checked the "Update your systema" and it was ok. I typed in the terminal command to fix rpmdb: [mageia41@localhost ~]$ su - Password: [root@localhost ~]# rm -f /var/lib/rpm/__db* [root@localhost ~]# rpm --rebuilddb [root@localhost ~]# I click on the Mageiaonline button in the system tray, and select "check updates" and the error message appears again: "A fatal error occurred: unable to open rpmdb" I checked the "Update your systema" and it was ok. I restart the Mageia and the error happened again. Despite this error in mageiaonline, upgrading and installing packages through the Mageia Control Center are working ok. Version-Release number of selected component (if applicable): Mageia 4.1, KDE, 64bits How reproducible: restart the Mageia or click on the Mageiaonline button in the system tray, and select "check updates" Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
I too have the same problem having installed Mageia 4.1 64-bit recently. There is something somewhat peculiar here though as this machine is almost identical to another which does not exhibit the odd behaviour - they are both HP ML350 G5s, installed from the same DVD ISO. Both were installed over Mageia 4 32-bit. The machine with the issue is quite capable of downloading updates and of installing new packages using rpmdrake. There is no evidence of rpmdb corruption, so I have not rebuilt the database. It simply seems that there is some sort of race condition in running mgaonline.
CC: (none) => mark.dawsonbutterworth
*** Bug 14821 has been marked as a duplicate of this bug. ***
CC: (none) => nougueyc
Have you found something, because I have this problem since a long time, and it is impossible to update normally mageia... I am obliged to use a console and type autoupdate. This evening, I had a new kernel, but I have always the problem with the new one... thanks
Assignee: bugsquad => thierry.vignaud
I opened the Bug 16203 reporting the same error in Mageia 5 installed on Virtualbox and on a physical machine. Error warnings keep happening in Mageia 5 installed on Virtualbox.Now, the same error message occurs in "Mageia 4.1" and "Mageia 5" installed on the physical machine. "A fatal error occurred: unable to open rpmdb".
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16203
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16197
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: UNCONFIRMED => RESOLVEDResolution: (none) => OLD
(In reply to Marja van Waes from comment #6) > As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status > on 2015-09-19. It is is no longer maintained, which means that it will not > receive any further security or bug fix updates. Hi Marja van Waes, I already updated to the Mageia 5 Thank you
(In reply to Samuel VERSCHELDE from comment #5) > Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no > longer > maintained, which means that it will not receive any further security or bug > fix updates. Hi Samuel VERSCHELDE, I already updated to the Mageia 5 Thank you