Bug 20305

Summary:	drakrpm-update crashed (Can't use an undefined value as an ARRAY reference at /usr/libexec/drakrpm-update line 127.)
Product:	Mageia	Reporter:	Sam Khangyi <khangyi>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	rpmdrake-6.23-1.mga6	CVE:
Status comment:

Description Sam Khangyi 2017-02-16 23:08:58 CET

The "drakrpm-update" program crashed. Drakbug-17.71 caught it.

I just finished my updates, a libmpelame update popeed up, i said ok to update it too, then this crash happened. i was going to restart after the first wave of updates. 

Can't use an undefined value as an ARRAY reference at /usr/libexec/drakrpm-update line 127.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.22.2/Gtk3.pm:524
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1550
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:857
ugtk3::main() called from /usr/libexec/drakrpm-update:282
main::run_treeview_dialog() called from /usr/libexec/drakrpm-update:293

Theme name: oxygen-gtk
Kernel version = 4.9.9-desktop-2.mga6
Distribution=Mageia release 6 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz

Comment 1 Marja Van Waes 2017-02-17 21:39:07 CET

Thanks for the bug report.
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find.
In general it is welcome to search for existing reports first to avoid filing duplicates.

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

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => DUPLICATE
Summary: drakrpm-update crashed => drakrpm-update crashed (Can't use an undefined value as an ARRAY reference at /usr/libexec/drakrpm-update line 127.)

Comment 2 Marja Van Waes 2017-02-17 21:47:05 CET

(In reply to Marja van Waes from comment #1)

> 
> *** This bug has been marked as a duplicate of bug 19249 ***

In fact, bug 8967 is the first report about this issue.

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