Bug 30517 - « drakrpm-update » crashed while updating the system from the MCC
Summary: « drakrpm-update » crashed while updating the system from the MCC
Status: RESOLVED DUPLICATE of bug 22042
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-07 11:34 CEST by Jean-Marc Sarat
Modified: 2022-06-07 12:01 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jean-Marc Sarat 2022-06-07 11:34:54 CEST
Description of problem:

Le programme « drakrpm-update » a planté avec l'erreur suivante :

  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 1288.
  Perl's trace:
  drakbug::bug_handler() called from /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm:1288
  URPM::resolve_requested__no_recommends_() called from /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm:1170
  URPM::resolve_requested__no_recommends() called from /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm:1100
  URPM::resolve_requested() called from /usr/share/perl5/vendor_perl/urpm/select.pm:403
  urpm::select::_resolve_priority_upgrades() called from /usr/share/perl5/vendor_perl/urpm/select.pm:391
  urpm::select::resolve_priority_upgrades_after_auto_select() called from /usr/share/perl5/vendor_perl/Rpmdrake/pkg.pm:393
  Rpmdrake::pkg::get_updates_list() called from /usr/share/perl5/vendor_perl/Rpmdrake/pkg.pm:509
  Rpmdrake::pkg::get_pkgs() called from /usr/share/perl5/vendor_perl/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

Thème utilisé : Adwaita

How reproducible:

Every time I attempt to update
Comment 1 sturmvogel 2022-06-07 12:01:59 CEST
Duplicate of 22042

*** This bug has been marked as a duplicate of bug 22042 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.