Description of problem: Three/five minutes after I start the Mageia 5, 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". See screenshots: https://picasaweb.google.com/106373477520489204423/Mageia5KDEMageiaonlineRpmdb?authuser=0&authkey=Gv1sRgCMXGx5KY092spQE&feat=directlink The same Bug 13835 of Mageia 4.1. 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 ~]# After I typed: [root@localhost ~]# urpmi --auto-update The update occurs correctly in text-mode, but error message appears on the KDE desktop environment. The error occurs in the language "Portuguese of Brazil" and in English. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
The error reported above is occurring with the instalation ISO LiveDVD Mageia 5 KDE 64, installed in VirtualBox. I removed all media repositories and added again choosing the specific repository from Brazil (BR): http://mageia.c3sl.ufpr.br/distrib/5/x86_64 The error occurs in graphical-mode, but does not seem to occur in text-mode and the software installation by MCC functions properly. This same error does not occur in Mageia 5 KDE, 64 installed since 2014 as Mageia Alpha (Cauldron) on a real machine and today has been updated as Mageia 5, including that I've removed the repositories Cauldron and added the repositories of Mageia 5.
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=13835
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16197
Summary: mageiaonline: a fatal error occurred: unable to open rpmdb => mgaonline: a fatal error occurred: unable to open rpmdb
I have the same error message "A fatal error occurred: unable to open rpmdb", usually after opening a browser window. This appears to have started when I changed the MSEC security level from standard to secure and/or doing a few updates a while ago. Mageia 5/ WIN7 dual boot on an Asuspro laptop.
CC: (none) => Paul.Lefort
I don't understand why you keep getting the error after deleting the old rpm database and creating a new one :-( Is there anything in your ~/.MgaOnline/ directory? If so, what? (The name of the file(s) + it/their content) Does anyone know whether this occurs in cauldron, too? (If so: please change the version from 5 to cauldron and put "MGA5TOO" on the whiteboard. It is no longer needed to open a new bug report when the same bug occurs in a different Mageia version.)
CC: (none) => marja11Assignee: bugsquad => thierry.vignaudSummary: mgaonline: a fatal error occurred: unable to open rpmdb => mgaonline error persists after rebuilddb (a fatal error occurred: unable to open rpmdb)
(In reply to Paul Lefort from comment #3) > This appears to have started when I changed the MSEC security level from standard to secure. I also have a custom configuration. I modified the setting in "Set System Security, Permissions and Auditing" from "standard" to "secure", with two changes: a) Allow_user_list-yes b) Allow reboot-yes. Maybe this is the cause of the error
(In reply to Marja van Waes from comment #4) > > I don't understand why you keep getting the error after deleting the old rpm > database and creating a new one :-( > > Is there anything in your ~/.MgaOnline/ directory? > > If so, what? (The name of the file(s) + it/their content) > > > Does anyone know whether this occurs in cauldron, too? > (If so: please change the version from 5 to cauldron and put "MGA5TOO" on > the whiteboard. It is no longer needed to open a new bug report when the > same bug occurs in a different Mageia version.) The only MgaOnline directories I can find are called mgaonline (ie all lower case); one in /usr/share and one in /usr/share/doc The first has 9 .png files and the second one has a text file called COPYING. So nothing sinister there I think.
(In reply to macxi macxi from comment #5) > (In reply to Paul Lefort from comment #3) > > This appears to have started when I changed the MSEC security level from standard to secure. > > > I also have a custom configuration. I modified the setting in "Set System > Security, Permissions and Auditing" from "standard" to "secure", with two > changes: a) Allow_user_list-yes b) Allow reboot-yes. Maybe this is the cause > of the error Since I just attempted something listed on KDE bugtracking (no. 328571 comment 3 I think) about adding a file called qt-no-glib.sh this computer seems to have lost the ability to open the MCC and so I cannot get at the system security tab to add those last two changes.
(In reply to macxi macxi from comment #5) > (In reply to Paul Lefort from comment #3) > > This appears to have started when I changed the MSEC security level from standard to secure. > > > I also have a custom configuration. I modified the setting in "Set System > Security, Permissions and Auditing" from "standard" to "secure", with two > changes: a) Allow_user_list-yes b) Allow reboot-yes. Maybe this is the cause > of the error Yeah, in secure mode it is likely that the user lost some rights wrt mgaonline and updating... but since I only knew about the error appearing when the database got corrupted, i didn't think of this as possibility :-( Can you boot Mageia, reproduce the error and then run, as root: journalctl -b > journalctl-b.txt and attach that file to this report?
(In reply to Marja van Waes from comment #8) > (In reply to macxi macxi from comment #5) > > (In reply to Paul Lefort from comment #3) > > > This appears to have started when I changed the MSEC security level from standard to secure. > > > > > > I also have a custom configuration. I modified the setting in "Set System > > Security, Permissions and Auditing" from "standard" to "secure", with two > > changes: a) Allow_user_list-yes b) Allow reboot-yes. Maybe this is the cause > > of the error > > Yeah, in secure mode it is likely that the user lost some rights wrt > mgaonline and updating... but since I only knew about the error appearing > when the database got corrupted, i didn't think of this as possibility :-( > > Can you boot Mageia, reproduce the error and then run, as root: > > journalctl -b > journalctl-b.txt > > and attach that file to this report? I booted into Mageia, waited for the error, and then ran the line above which is no good because I then cannot access the file. So I ran journalctl -b > /home/paul/journalctl-b.txt Now I can access the file but can't read it because it is owned by root. When I run journalctl as a normal user the file output is readable but much smaller. Why is there no simple system log that is readable instead of all this palava?
(In reply to Paul Lefort from comment #9) > > > > Can you boot Mageia, reproduce the error and then run, as root: > > > > journalctl -b > journalctl-b.txt > > > > and attach that file to this report? > > I booted into Mageia, waited for the error, and then ran the line above > which is no good because I then cannot access the file. Ah, of course: my security settings are more lenient, forgot that yours are strict. Please run (as root) chmod 644 journalctl-b.txt Now you'll be able to read and attach it.
Created attachment 7354 [details] journalctl-b.txt in answer to comment #10
Created attachment 7355 [details] journalctl-b.txt
Summary: mgaonline error persists after rebuilddb (a fatal error occurred: unable to open rpmdb) => mgaonline error persists after rebuilddb (a fatal error occurred: unable to open rpmdb), when Secure msec settings are used instead of Standard
Assignee: thierry.vignaud => mageiatools
Hi Macxi & Paul, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
@ Macxi & Paul: No reply, so closing as OLD since Mageia 5 is no longer maintained. ==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==
Resolution: (none) => OLDStatus: NEW => RESOLVED