Bug 20005

Summary:	drakrpm-update crashed (<data>:1:28Expected a string. at /usr/lib/perl5/vendor_perl/5.22.2/Gtk3.pm line 1050.)
Product:	Mageia	Reporter:	Ron Brickle <ronb19495>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	rpmdrake-6.23-1.mga6	CVE:
Status comment:

Description Ron Brickle 2016-12-22 14:29:04 CET

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

having a shower

<data>:1:28Expected a string. at /usr/lib/perl5/vendor_perl/5.22.2/Gtk3.pm line 1050.
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-update:205
main::run_treeview_dialog() called from /usr/libexec/drakrpm-update:293

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

Comment 1 Marja Van Waes 2016-12-23 20:38:53 CET

This reminds me of bug 19406, but the line number is different (1050 now instead of 988)

@ Ron 

What does the following command return?

       rpm -q perl-Gtk3

and the following:

       rpm -q drakxtools

CC: (none) => marja11
Assignee: bugsquad => mageiatools
Summary: drakrpm-update crashed => drakrpm-update crashed (<data>:1:28Expected a string. at /usr/lib/perl5/vendor_perl/5.22.2/Gtk3.pm line 1050.)

Comment 2 Thierry Vignaud 2016-12-23 23:21:08 CET

That's just because Gtk3 lines numbers have been moved due to doc, ...
Anyway that does not point to the real culprit, the real error still happen in the same place in rpmdrake.
The drakbug version obviously shows it's an even older drakxtools version than in the other bug so please apply updates

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

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => DUPLICATE