Bug 16484 - drakrpm-update crashed (Can't use an undefined value as an ARRAY reference at drakrpm-update line 127)
Summary: drakrpm-update crashed (Can't use an undefined value as an ARRAY reference at...
Status: RESOLVED DUPLICATE of bug 8967
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-27 23:57 CEST by Henk Elbers
Modified: 2015-07-31 09:27 CEST (History)
1 user (show)

See Also:
Source RPM: rpmdrake-6.20-1.mga5
CVE:
Status comment:


Attachments

Description Henk Elbers 2015-07-27 23:57:49 CEST
The "drakrpm-update" program crashed. Drakbug-16.104 caught it.

just installing 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.20.1/Gtk3.pm:295
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1521
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:859
ugtk3::main() called from /usr/libexec/drakrpm-update:282
main::run_treeview_dialog() called from /usr/libexec/drakrpm-update:293

Theme name: TraditionalOk
Kernel version = 3.19.8-desktop-3.mga5
Distribution=Mageia release 5 (Official) for x86_64
CPU=AMD Phenom(tm) II X4 965 Processor
Comment 1 Thierry Vignaud 2015-07-31 09:26:11 CEST
Dup

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

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => DUPLICATE
Summary: drakrpm-update crashed => drakrpm-update crashed (Can't use an undefined value as an ARRAY reference at drakrpm-update line 12)

Thierry Vignaud 2015-07-31 09:27:04 CEST

Summary: drakrpm-update crashed (Can't use an undefined value as an ARRAY reference at drakrpm-update line 12) => drakrpm-update crashed (Can't use an undefined value as an ARRAY reference at drakrpm-update line 127)


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