Bug 19444 - drakrpm crashed
Summary: drakrpm crashed
Status: RESOLVED DUPLICATE of bug 19406
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: 2016-09-22 18:30 CEST by Francois Lacroix
Modified: 2016-09-22 21:47 CEST (History)
1 user (show)

See Also:
Source RPM: rpmdrake-6.22-2.mga6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Francois Lacroix 2016-09-22 18:30:41 CEST 
The "drakrpm" program crashed. Drakbug-17.46 caught it.

j'ouvrais le gestionnaire de logiciels


<data>:1:28Expected a string. at /usr/lib/perl5/vendor_perl/5.22.2/Gtk3.pm line 988.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/Glib/Object/Introspection.pm:67
Glib::Object::Introspection::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1302
mygtk3::MagicWindow::AUTOLOAD() called from /usr/lib/libDrakX/ugtk3.pm:130
ugtk3::gtkadd() called from /usr/libexec/drakrpm:766
main::run_treeview_dialog() called from /usr/libexec/drakrpm:848

Theme name: Adwaita
Kernel version = 4.6.3-desktop-1.mga6
Distribution=Mageia release 6 (Cauldron) for x86_64
CPU=AMD A6-3400M APU with Radeon(tm) HD Graphics
Comment 1 Francois Lacroix 2016-09-22 18:32:10 CEST 
Je ne peux plus utiliser le centre de controle
Comment 2 Marja Van Waes 2016-09-22 21:47:23 CEST 
(In reply to Francois Lacroix from comment #1)
> Je ne peux plus utiliser le centre de controle

Please do as said in
https://bugs.mageia.org/show_bug.cgi?id=19406#c26 :

> Please open a terminal/konsole and run, as root:
> 
>     urpmi --auto-update
> 
> to update your system. After that everything should work well again.

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

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.