Bug 8120 - MageiaUpdate crashed
Summary: MageiaUpdate crashed
Status: RESOLVED DUPLICATE of bug 8106
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-18 05:52 CET by Teymuraz Khazaradze
Modified: 2012-11-18 12:51 CET (History)
0 users

See Also:
Source RPM: rpmdrake-5.39-1.mga3
CVE:
Status comment:


Attachments

Description Teymuraz Khazaradze 2012-11-18 05:52:11 CET
The "MageiaUpdate" program crashed. Drakbug-14.50 caught it.

I installed Mageia 3 alpha 3. I added repos Core Release and Update, Non-free Release and Update, Tainted Release and Update. 
After I selected System update from MCC and run update. Update failed with this message:

detecting looping forever while trying to resolve dependancies.
Aborting... Try again with '-vv --debug' options at /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/URPM/Resolve.pm line 1061.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/URPM/Resolve.pm:1061
URPM::resolve_requested__no_suggests_() called from /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/URPM/Resolve.pm:944
URPM::resolve_requested__no_suggests() called from /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/URPM/Resolve.pm:874
URPM::resolve_requested() called from /usr/lib/perl5/vendor_perl/5.16.1/Rpmdrake/pkg.pm:407
Rpmdrake::pkg::get_updates_list() called from /usr/lib/perl5/vendor_perl/5.16.1/Rpmdrake/pkg.pm:508
Rpmdrake::pkg::get_pkgs() called from /usr/lib/perl5/vendor_perl/5.16.1/Rpmdrake/gui.pm:630
Rpmdrake::gui::pkgs_provider() called from /usr/sbin/MageiaUpdate:259
main::run_treeview_dialog() called from /usr/sbin/MageiaUpdate:286

Theme name: oxygen-gtk
Kernel version = 3.6.5-server-1.mga3
Distribution=Mageia release 3 (Cauldron) for i586
CPU=Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz
Comment 1 Manuel Hiebel 2012-11-18 12:51:20 CET

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

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


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