The "mgaapplet-update-checker" program crashed. Drakbug-18.33 caught it. je checkai les mises à jour... Magéia 8.b1 ici, c'est peut être déjà corrigé dans la béta 2... SEGV Glibc's trace: 0: /usr/lib/libDrakX/auto/c/stuff/stuff.so(+0x95d5) [0x7fd81e0685d5] 1: /lib64/libperl.so.5.32(Perl_pp_entersub+0x217) [0x7fd81dddbe17] 2: /lib64/libperl.so.5.32(Perl_runops_standard+0x2e) [0x7fd81ddd241e] 3: /lib64/libperl.so.5.32(Perl_call_sv+0x364) [0x7fd81dd39394] 4: /lib64/libperl.so.5.32(Perl_perly_sighandler+0x229) [0x7fd81ddc0c49] 5: /lib64/libc.so.6(+0x3a4e0) [0x7fd81db464e0] 6: /lib64/libc.so.6(+0x1b3120) [0x7fd81dcbf120] Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41 drakbug::__ANON__() called from /usr/share/perl5/vendor_perl/urpm.pm:424 (eval)() called from /usr/share/perl5/vendor_perl/urpm.pm:424 urpm::db_open_or_die() called from /usr/bin/mgaapplet-update-checker:73 Theme name: Adwaita Kernel version = 5.8.13-desktop-1.mga8 Distribution=Mageia release 8 (Cauldron) for x86_64 CPU=Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Yeah. Beta 1 Stuff + repositories going to synchronization... Sometimes it leads to a crash in mgaapplet stuff. But this can't be satisfactorily. I do think there are fix in newer version. And we have newer versions. Is this reproducible? If you have upgraded your packages successfully, does it reoccur?
CC: (none) => ouaurelien
> Is this reproducible? it was there, each time the mga applet was trying to get updates or if I asked it to do so from the beta1 install... > If you have upgraded your packages successfully, does it reoccur? So, I've upgraded by hand through the CCM and all goes fine, but as soon as mgaapplet does its job (auto mode or asked for) it still throw problems : after the update it cry for 'not being able to open the rpm database' as ever... After all these Mageia updates (for me from v4 to v8) that dreaded bug is still there ! why ??? I get it each time I install a new machine (real or virtualized) or upgrade an old one. If I have luck, reconstructing the rpm db with the habitual 'rpm -vv --rebuilddb' in root mode will suffice for that problem to disappear for good, but if luck is out of sync that problem survive and reappear at each reboot... I've had some machines where it has never ceased. I can see how newcomers to Mageia and linux can be bugged and potentially disgusted from linux by that sole bug...
The segfault you are complaining is not reproducible on our computers. Please do the following: - launch a Terminal (Console) and type killall mgaapplet - remove the .MageiaOnline hidden directory in your home user - remove all medias in drakrpm-edit-media. Even the cd-rom lines. - add new media properly with add button. Only select core, core/updates, eventually nonfree nonfree/updates and if you desire, tainted and tainted/updates. - please use Updates from CCM Softwares pane. This will trigger Mageia Update. Please see if there are updates. Mgaapplet runs fine with default media.
[Collided with Aurélien, but these questions remain relevant] 'mgaapplet-update-checker' is in pkg 'mgaonline'. > After all these Mageia updates (for me from v4 to v8) that dreaded bug is > still there ! why ??? Do you mean it has troubled you since Mageia 4 ? If it has troubled you for a long time, is this the first bug you raised about it ? >> Is this reproducible? > it was there, each time the mga applet was trying to get updates > or if I asked it to do so from the beta1 install... So it is always the automatic update check (mgaapplet) that crashes, but you can do updates 'by hand'. > 'not being able to open the rpm database' as ever Do you mean 'forever' (sans terminer) or 'since always' (depuis toujours) ? Or maybe both ? As Aurélien suggested, you certainly need to try the latest RC ISO (please say which one), and report back whether the fault is still present or gone. You are the only person to report it, so it is not widespread. The repository mirrors were in a mess recently (I could do nothing rpm-related for some time), but that has been fixed. That could have a bearing.
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #4) > [Collided with Aurélien, but these questions remain relevant] > 'mgaapplet-update-checker' is in pkg 'mgaonline'. > > > After all these Mageia updates (for me from v4 to v8) that dreaded bug is > > still there ! why ??? > Do you mean it has troubled you since Mageia 4 ? If it has troubled you for > a long time, is this the first bug you raised about it ? I don't remember if I've filled a bugzy before but I've sent a lot of emails to the ml (Fr for the most) about that problem and seing the answers I got I was not the sole to have stumbled upon that problem as they have all the solution ready... first I was said to try 'rpm --rebuilddb' in root mode after erasing the dbs but this one if it effectively rebuild the db isn't sufficient enough as the bug was resurfacing after the initial use of the mga applet or each subsequent reboots... Then I've found the 'rpm -vv --rebuilddb' and this one worked better. for instance, this time (with beta8#1) I had to rebuild the db two times only before the bug let me alone ^^) > > >> Is this reproducible? > > it was there, each time the mga applet was trying to get updates > > or if I asked it to do so from the beta1 install... > So it is always the automatic update check (mgaapplet) that crashes, but you > can do updates 'by hand'. yes, it has ever worked when updates are done by the ccm. > > > 'not being able to open the rpm database' as ever > Do you mean 'forever' (sans terminer) or 'since always' (depuis toujours) ? > Or maybe both ? I mean 'each time' I install a new machine and first clean boot of it... to try to cure that problem, I've tried to quickly open the ccm and change the first time check of updates after boot to 30 minutes (instead of 3), reboot, done a complete new repos update, rebuild the db after that and rebooted again to see if the applet worked better but a lot of times I was still bugged by the applet bug and its 'can't open rpm db bla bla bla please reconfigure the repos bla bla bla'... the thing I had just been doing... arg. > > As Aurélien suggested, you certainly need to try the latest RC ISO (please > say which one), and report back whether the fault is still present or gone. > You are the only person to report it, so it is not widespread. perhaps noone thinked of doing it before ? but as said upper I don't think I was the sole to be bugged by this... BTW, Just installed a new (virtual) machine using the beta#2, done the updates during the install and this time after the reboot mga applet worked without fuss ^^) crossing fingers it do same at each boot now ;) > > The repository mirrors were in a mess recently (I could do nothing > rpm-related for some time), but that has been fixed. That could have a > bearing. for that 8 beta I'm ok but why it comes with older versions even when installed away from the repos rebuild ?
You don't have to rebuild the rpm database. As long as you only use mageia provided repos, this is no necessary. Do you use other repo for other software not provided by Mageia? Do you use a particular mirror like http://ftp.free.fr/mirrors/mageia.org/distrib/8/ Or do you use $MIRRORLIST ?
Also, do you mix usage of rpmdrake/urpmi with DNF/dnfdragora/Discover/PackageKit?
(In reply to Aurelien Oudelet from comment #6) > You don't have to rebuild the rpm database. > > As long as you only use mageia provided repos, this is no necessary. > > Do you use other repo for other software not provided by Mageia? No > Do you use a particular mirror like > http://ftp.free.fr/mirrors/mageia.org/distrib/8/ ah! forgotten about this one... so no > > Or do you use $MIRRORLIST ? I use what is proposed by default at install, $MIRRORLIST
(In reply to Aurelien Oudelet from comment #7) > Also, do you mix usage of rpmdrake/urpmi with > DNF/dnfdragora/Discover/PackageKit? Never on this machine or the ones I do for customers. only the ccm for installs or updates or the applet for 'auto' updates
Note that the RC iso images are still in qa testing, so not yet available to the general public. Jean-François Bachelet is not one of the qa iso testers, so beta2 is the latest available iso image. It's been a very long time since I've seen a problem requiring a rebuild of the rpm database. When it did happen, it required running rm -f /var/lib/rpm/__db.* rpm --rebuilddb The database corruption typically occurs when an update of the rpm database is interrupted, for example by powering off the system while a package is being installed. It's supposed to be handled automatically, as I understand it, but it's a tricky problem to test. It also affected all rpm installation, not just mgaapplet.
CC: (none) => davidwhodgins
Not reproducible? This week there are many updates coming to 7 and to 8. Can you check out that mgaapplet does not segfault anymore? Perhaps, it's better to use a manually a French mirror like http://ftp.free.fr/mirrors/mageia.org/distrib/VERSION/ARCH where VERSION is either 7 or 8 and ARCH is x86_64 or i586.
Status: NEW => NEEDINFO
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEEDINFO => RESOLVEDResolution: (none) => OLD