The "drakrpm-update" program crashed. Drakbug-18.21 caught it. There is some issue with libuser, that has been going on for days. detecting looping forever while trying to resolve dependencies. Aborting... Try again with '-vv --debug' options at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 1287. Perl's trace: drakbug::bug_handler() called from /usr/share/perl5/vendor_perl/Gtk3.pm:538 Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1550 mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:857 ugtk3::main() called from /usr/libexec/drakrpm-update:282 main::run_treeview_dialog() called from /usr/libexec/drakrpm-update:293 Theme name: Adwaita Kernel version = 5.3.2-desktop-1.mga8 Distribution=Mageia release 8 (Cauldron) for x86_64 CPU=Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
This looks like a duplicate of the following bugs which also look like duplicates (but may not be): bug 18127, bug 21898, bug 22387, bug 22868, bug 24262. Assigning to mageiatools group, to whom I ask to check these 6 bugs and see whether they are really duplicates; if so, please close those those that are. CC'ing Thierry who already has one of these (18127).
Assignee: bugsquad => mageiatoolsCC: (none) => lewyssmith, thierry.vignaud
Well, at least I am in good company! Several attempts to update Cauldron seemed to go ahead, then, while I was doing something else, drakrpm mysteriously disappeared. This time, I caught it. Subsequent smaller updates have run O.K.
Doug It is clear from a recent spate of similar bugs that updating a Cauldron system while Cauldron itself is bubbling (if not boiling) is likely to lead to failures such as this, which disappear once things have calmed down. This is just one of the prices to pay for using Cauldron, and not an intrinsic error in itself. Can we close this?
(In reply to Lewis Smith from comment #3) > Doug > It is clear from a recent spate of similar bugs that updating a Cauldron > system while Cauldron itself is bubbling (if not boiling) is likely to lead > to failures such as this, which disappear once things have calmed down. This > is just one of the prices to pay for using Cauldron, and not an intrinsic > error in itself. > > Can we close this? Closed: This report was originally lodged by the bug squisher, not consciously by me.
Status: NEW => RESOLVEDResolution: (none) => FIXED