Bug 11667 - MageiaUpdate crashed
Summary: MageiaUpdate crashed
Status: RESOLVED DUPLICATE of bug 10674
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-14 12:57 CET by Joep van Ham
Modified: 2013-11-14 18:20 CET (History)
0 users

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


Attachments

Description Joep van Ham 2013-11-14 12:57:13 CET
The "MageiaUpdate" program crashed. Drakbug-15.54.1 caught it.

Mageia-3 upograde from mageia-2 failed.
I tried to update from root privileges, software management, update your system, accepting dependencies.
System crashed, see log reprot
Please advise & regards,
Joep van Ham

Can't use an undefined value as a HASH reference at /usr/lib/perl5/vendor_perl/5.16.3/Rpmdrake/gui.pm line 361.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.16.3/Rpmdrake/gui.pm:361
Rpmdrake::gui::warn_if_no_pkg() called from /usr/lib/perl5/vendor_perl/5.16.3/Rpmdrake/gui.pm:387
Rpmdrake::gui::node_state() called from /usr/lib/perl5/vendor_perl/5.16.3/Rpmdrake/gui.pm:883
Rpmdrake::gui::toggle_nodes() called from /usr/sbin/MageiaUpdate:122
main::toggle() called from /usr/sbin/MageiaUpdate:82
main::refresh_packages_list() called from /usr/sbin/MageiaUpdate:261
main::run_treeview_dialog() called from /usr/sbin/MageiaUpdate:286

Theme name: oxygen-gtk
Kernel version = 3.4.52-desktop-1.mga2
Distribution=Mageia release 3 (Official) for i586
CPU=Pentium(R) Dual-Core CPU       T4400  @ 2.20GHz
claire robinson 2013-11-14 17:59:29 CET

Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2013-11-14 18:20:41 CET
A dup. By the way, if you can provides the info asked on bug #10674, ...

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

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


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