Bug 24633

Summary: drakrpm-update crashed
Product: Mageia Reporter: pierre fernandes <pierre.fernandes>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: 6   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: rpmdrake-6.27-1.mga6 CVE:
Status comment:

Description pierre fernandes 2019-04-07 11:14:44 CEST
The "drakrpm-update" program crashed. Drakbug-17.88.3 caught it.

mise à jour du systeme MGA6.1

Le programme « drakrpm-update » a planté avec l'erreur suivante :

  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.3/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

Thème utilisé : Adwaita

Pour soumettre un rapport de bogue, cliquez sur le bouton Signaler.  
Cela ouvrira une fenêtre de navigateur sur Bugzilla où vous trouverez un formulaire à remplir.  L'information affichée ci-dessus sera transférée vers ce serveur
Il est très utile d'inclure dans votre rapport la sortie de la commande suivante : « lspcidrake -v ».

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.3/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: Adwaita
Kernel version = 4.9.35-desktop-1.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz
Comment 1 Marja Van Waes 2019-04-09 10:29:47 CEST
Thanks for the report, Pierre.

This issue has been reported before, but please do continue to report bugs as you find them. 

However, when you know the issue has already been reported, then please add a comment in that existing bug report to tell that you hit the issue, too.

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

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