The "rpmdrake" program crashed. Drakbug-14.22.4 caught it. not sure. its something my system needs. many crashes. Just registered. May have to use and ISO. Can't call method "is_arch_compat" on an undefined value at /usr/lib/perl5/vendor_perl/5.14.2/i386-linux-thread-multi/URPM/Resolve.pm line 230. Perl's trace: standalone::bug_handler() called from /usr/lib/libDrakX/mygtk2.pm:1424 mygtk2::main() called from /usr/lib/libDrakX/ugtk2.pm:767 ugtk2::main() called from /usr/lib/perl5/vendor_perl/5.14.2/Rpmdrake/gui.pm:596 Rpmdrake::gui::ask_browse_tree_given_widgets_for_rpmdrake() called from /usr/sbin/rpmdrake:780 main::run_treeview_dialog() called from /usr/sbin/rpmdrake:804 Theme name: Adwaita Kernel version = 3.4.69-desktop-1.mga2 Distribution=Mageia release 2 (Official) for i586 CPU=Intel(R) Pentium(R) 4 CPU 2.80GHz
(In reply to hannah Mrs from comment #0) > The "rpmdrake" program crashed. Drakbug-14.22.4 caught it. > > not sure. its something my system needs. many crashes. Just registered. > May have to use and ISO. > Dear Mrs Hannah, Thanks for taking the trouble to file a bug report. Unfortunately, you are using a very old version of Mageia, that's no longer maintained since November 2013 http://blog.mageia.org/en/2013/11/21/farewell-mageia-2/ That means that since then, there were no more security updates for your computer, and that your computer is very vulnerable now. Please install Mageia 5, the currently supported version, as soon as possible. It is not possible to upgrade directly from Mageia 2 to Mageia 5, it is better to do a clean install. I know too little about security to know whether it is safe to keep all of your /home partition while doing a fresh classic install, or not. Please (especially if you're using flash or java, or if you do not know whether you use them) go to the forums https://forums.mageia.org/en/ for better advise on that than I can give. Closing this report as invalid, because Mageia 2 is no longer maintained Kind regards, Marja
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => INVALID
*** Bug 17697 has been marked as a duplicate of this bug. ***