The "mgaapplet-update-checker" program crashed. Drakbug-17.56 caught it. I was doing nothing. This was a normal update in the background. It did this earlier, and I assumed it was because the list of updates has a problem. As a precaution, I will reset my list of rpms, and try again detecting looping forever while trying to resolve dependancies. Aborting... Try again with '-vv --debug' options at /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/URPM/Resolve.pm line 1286. Perl's trace: drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/URPM/Resolve.pm:1286 URPM::resolve_requested__no_recommends_() called from /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/URPM/Resolve.pm:1168 URPM::resolve_requested__no_recommends() called from /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/URPM/Resolve.pm:1098 URPM::resolve_requested() called from /usr/lib/perl5/vendor_perl/5.22.2/urpm/select.pm:347 urpm::select::resolve_dependencies() called from /bin/mgaapplet-update-checker:79 Theme name: Adwaita Kernel version = 4.8.1-desktop-1.mga6 Distribution=Mageia release 6 (Cauldron) for x86_64 CPU=Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
Updating my RPM database made no difference.
CC: (none) => marja11Assignee: bugsquad => mageiatoolsSummary: mgaapplet-update-checker crashed => mgaapplet-update-checker crashed (detecting looping forever while trying to resolve dependancies.)
I seem to be the only person with this bug. It is still there in my default Mga6 installation, but I just updated my original "Cauldron" installation, and so far, it has not appeared there. Where should I start looking?
Because of the observations in Comment 2, I deleted the sources in my default Mga6, and installed them again following the procedure on the "Cauldron" page of the wiki. Updating from the command line brought down all of the updates I had missed. The bug has not returned. By now, it should have. I will leave this bug report open for a while, to allow for a "soak test."
This happens often when upgrading from one Mageia version to the next, when: * the old Mageia version has received updates and * for the next version only the iso is used, without online media. In that case, there can be packages with a newer version in Mageia_old than in Mageia_new from the iso. I don't see that in our errata, iiuc it needs to be added again. ==NOTE: FOR_ERRATA _only_ for the upgrade issue ^^^^ *However*, since you weren't upgrading, there might be something wrong with one specific update. @ anyone hitting this, please run, as root: urpmi --auto-update -vv --debug 2>&1 | tee urpmi_debug.txt and attach urpmi_debug.txt to this report.
Keywords: (none) => FOR_ERRATA5, FOR_ERRATA6Status comment: (none) => "FOR_ERRATA" only for this issue while upgrading without online media
This is history as far as I am concerned. Feel free to close it when appropriate.
(In reply to Doug Laidlaw from comment #5) > This is history as far as I am concerned. Feel free to close it when > appropriate. now ;-)
Keywords: FOR_ERRATA6 => IN_ERRATA6
Closed as fixed.
Status: NEW => RESOLVEDResolution: (none) => FIXED
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=22042