Bug 20172 - draklog crashed (undefined value for mandatory argument 'text' encountered at /usr/lib/libDrakX/mygtk3.pm line 1449.)
Summary: draklog crashed (undefined value for mandatory argument 'text' encountered at...
Status: RESOLVED DUPLICATE of bug 14940
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 tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-24 18:30 CET by Jiri Fuksa
Modified: 2017-03-13 16:44 CET (History)
1 user (show)

See Also:
Source RPM: drakxtools-16.105.1-1.mga5
CVE:
Status comment:

Attachments
output of lspcidrake -l (4.68 KB, text/plain)
2017-01-24 18:30 CET, Jiri Fuksa 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jiri Fuksa 2017-01-24 18:30:27 CET 
Created attachment 8893 [details]
output of lspcidrake -l

The "draklog" program crashed. Drakbug-16.105.1 caught it.

Looking at PC's hardware info provided by Mageia Ctrl Center.

undefined value for mandatory argument 'text' encountered at /usr/lib/libDrakX/mygtk3.pm line 1449.
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/draklog:191

Theme name: oxygen-gtk
Kernel version = 4.4.39-desktop-1.mga5
Distribution=Mageia release 5 (Official) for x86_64
CPU=Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
Marja Van Waes 2017-01-24 21:58:58 CET

CC: (none) => marja11
Assignee: bugsquad => mageiatools
Summary: draklog crashed => draklog crashed (undefined value for mandatory argument 'text' encountered at /usr/lib/libDrakX/mygtk3.pm line 1449.)

Comment 1 Rémi Verschelde 2017-03-13 16:44:39 CET 
Thanks for the report. It appears to be the same issue as bug 14940.

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

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