Bug 5423 - MageiaUpdate crashed
Summary: MageiaUpdate crashed
Status: RESOLVED DUPLICATE of bug 4972
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-16 02:32 CEST by David Deaderick
Modified: 2012-04-16 03:38 CEST (History)
1 user (show)

See Also:
Source RPM: rpmdrake-5.30-1.mga2
CVE:
Status comment:


Attachments

Description David Deaderick 2012-04-16 02:32:22 CEST
The "MageiaUpdate" program crashed. Drakbug-13.93 caught it.

Fresh installation. Have already removed __db* .rpm.lock and rebuilddb, but I cannot update. In this instance I was trying to update glibc and one other package (either urpmi or rpm). glibc needs to be removed for other packages to be updated, but the attempt fails, since it tries to updated with exactly the same package. The installation fails from the command line and from Software Management.

Can't call method "set_flag_skip" on an undefined value at /usr/sbin/MageiaUpdate line 114.
Perl's trace:
standalone::bug_handler() called from /usr/lib/libDrakX/mygtk2.pm:1424
mygtk2::main() called from /usr/lib/libDrakX/ugtk2.pm:767
ugtk2::main() called from /usr/sbin/MageiaUpdate:273
main::run_treeview_dialog() called from /usr/sbin/MageiaUpdate:284

Theme name: oxygen-gtk
Kernel version = 3.3.0-desktop-0.rc7.1.mga2
Distribution=Mageia release 2 (Cauldron) for x86_64
CPU=AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
Comment 1 David Deaderick 2012-04-16 02:57:38 CEST
The additional package mentioned above is rpmdrake. I think this is the "old" rpmdrake issue related to development just prior to Beta2, but I am unable to work around it with this fresh installation of Beta2.
Comment 2 Dave Hodgins 2012-04-16 03:12:13 CEST
See Bug 4972.

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

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

Comment 3 David Deaderick 2012-04-16 03:38:41 CEST
Yep, it is. Thanks.

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