The "drakrpm-update" program crashed. Drakbug-17.93 caught it. I was updating everthing from mga6 to cauldron on a freshly installed and updated mg6 on physical hardware. via command line urpmi --auto-update --auto I think it stopped around 502 / 1400 packages: 502/1425: java-1.8.0-openjdk-headless ####################################################################################attention : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-1.b14.1.mga7.x86_64/jre/lib/security/java.security créé en tant que /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-1.b14.1.mga7.x86_64/jre/lib/security/java.security.rpmnew # restored /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-1.b14.1.mga7.x86_64/jre/lib/security/java.security.rpmnew to /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-1.b14.1.mga7.x86_64/jre/lib/security/java.security Exception en point flottant (core dumped) then when I try to resume in command Line: [root@localhost dev]# urpmi --auto-update --auto le média « Core Release » est à jour le média « Core Updates » est à jour le média « Nonfree Release » est à jour le média « Nonfree Updates » est à jour le média « Core 32bit Release » est à jour le média « Core 32bit Updates » est à jour le média « Nonfree 32bit Release » est à jour le média « Nonfree 32bit Updates » est à jour Erreur de segmentation (core dumped) and by try to launch update system from MCC, it got this error. SEGV Glibc's trace: 4: /lib64/libperl.so.5.26(Perl_sighandler+0x485) [0x7f5c99fe3655] 5: /lib64/libpthread.so.0(+0x10a70) [0x7f5c99d0ea70] 6: /lib/../lib64/libdb-5.3.so(+0x184b34) [0x7f5c8f4ffb34] 7: /lib/../lib64/libdb-5.3.so(__env_failchk_int+0x3c) [0x7f5c8f4ff33a] 8: /lib/../lib64/libdb-5.3.so(__env_failchk_pp+0x161) [0x7f5c8f4ff2e2] 9: /lib/../lib64/librpm.so.8(+0x16cef) [0x7f5c9046fcef] 10: /lib/../lib64/librpm.so.8(+0x1e78e) [0x7f5c9047778e] 11: /lib/../lib64/librpm.so.8(+0x1efc1) [0x7f5c90477fc1] 12: /lib/../lib64/librpm.so.8(rpmtsOpenDB+0x35) [0x7f5c904a1eb5] 13: /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/auto/URPM/URPM.so(+0x15871) [0x7f5c906e4871] 14: /lib64/libperl.so.5.26(Perl_pp_entersub+0x1f1) [0x7f5c99ffdc11] 15: /lib64/libperl.so.5.26(Perl_runops_standard+0x16) [0x7f5c99ff5ab6] 16: /lib64/libperl.so.5.26(perl_run+0x26f) [0x7f5c99f7801f] 17: /usr/bin/perl() [0x400c7a] 18: /lib64/libc.so.6(__libc_start_main+0xea) [0x7f5c98dfb65a] 19: /usr/bin/perl() [0x400cb9] Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41 drakbug::__ANON__() called from /usr/lib/perl5/vendor_perl/5.22.3/Rpmdrake/open_db.pm:72 (eval)() called from /usr/lib/perl5/vendor_perl/5.22.3/Rpmdrake/open_db.pm:72 Rpmdrake::open_db::open_rpm_db() called from /usr/lib/perl5/vendor_perl/5.22.3/Rpmdrake/pkg.pm:468 (eval)() called from /usr/lib/perl5/vendor_perl/5.22.3/Rpmdrake/pkg.pm:468 Rpmdrake::pkg::get_pkgs() called from /usr/lib/perl5/vendor_perl/5.22.3/Rpmdrake/gui.pm:642 Rpmdrake::gui::pkgs_provider() called from /usr/libexec/drakrpm-update:266 main::run_treeview_dialog() called from /usr/libexec/drakrpm-update:293 Theme name: Adwaita Kernel version = 4.9.35-desktop-1.mga6 Distribution=Mageia release 7 (Cauldron) for x86_64 CPU=Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Make sure that you don't have the broken update candidate for the rpm package that was recently removed from updates_testing. I believe the good current version from updates is rpm-4.13.0.2-3.1.mga6 and the broken one was rpm-4.13.0.2-3.2.mga6.
Keywords: (none) => NEEDINFOCC: (none) => marja11
Some more info about the process to find/repeat the bug: - Install Mageia 6 x64 for Live version from USB onto a laptop - No modification, addintional installation is done - Install all updates of Mageia 6 - Remove all repository, add Cauldron repositories, and lunch the full update. (this is done in command line following instructions of https://wiki.mageia.org/en/Cauldron This is about a 1-hour process. Once the bug is met, I cannot find a way to complete the update, the segmentation fault prevents it every time. So it leaves me with a broken system that will not start. My only current option is to re-install all again. So I will try again to check the rpm version. I don't think I have used one from update-testing as this repo is not activated by default on a refresh installation, and I did not activate it manually. Checking on http://madb.mageia.org/package/show/application/0/arch/x86_64/name/rpm, I see that there are 2 versions listed in core-updates. rpm-4.13.0.2-3.1.mga6.x86_64.rpm (Mageia 6, x86_64 media, core-updates) Install rpm-4.13.0.1-3.mga6.x86_64.rpm (Mageia 6, x86_64 media, core-release) Install rpm-4.13.0.1-3.1.mga6.x86_64.rpm (Mageia 6, x86_64 media, core-updates) Install Is it expected ? Could I get the rpm-4.13.0.2-3.1 by default (the faulty one)? So I guess that if I want it to make the switch to cauldron work, I should change the version of rpm back to rpm-4.13.0.1-3.1 before updating the system. I'll let you know, thanks.
Sorry, at the end of my previous comment I mixed the version numbers. Please ignore. I tried again and managed to complete the update this time. (the system is still not booting but I think this is a separate issue). The reason may be that I have rebooted between the full update of mageia 6 and the procedure to update to mageia 7. So maybe this time I ensured that I used the last rpm version (4.13.0.2-3.1.mga6) and not the original version coming from the Live ISO. So this bug may be closed, but it seems the step to the Cauldron install procedure should be completed: - Before updating the system to Cauldron, update your system fully first and reboot it once. This will ensure your are using the latest version of the packages needed for this update. Would you agree?
(In reply to Stéphane Couturier from comment #3) > > So this bug may be closed, but it seems the step to the Cauldron install > procedure should be completed: > > - Before updating the system to Cauldron, update your system fully first and > reboot it once. This will ensure your are using the latest version of the > packages needed for this update. > That's indeed the best way, https://wiki.mageia.org/en/Cauldron#How_to_update_to_Mageia_Cauldron should indeed be improved. If you have write access to our wiki, then feel free to update it. Else someone from documentation team will do it, when one of them finds time.
Keywords: NEEDINFO => (none)Assignee: bugsquad => doc-bugsSummary: drakrpm-update segfaulted then trying to update the system to cauldron => Enhance the wiki documentation about updating to cauldron
Wiki updated
CC: (none) => yves.brungard_mageiaResolution: (none) => FIXEDStatus: NEW => RESOLVED