Bug 12508 - drakrpm crashed (undefined value for mandatory argument 'text')
Summary: drakrpm crashed (undefined value for mandatory argument 'text')
Status: RESOLVED DUPLICATE of bug 13268
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11778
  Show dependency tree / graph
 
Reported: 2014-02-02 01:03 CET by Robert Ottlovich
Modified: 2014-05-01 20:17 CEST (History)
0 users

See Also:
Source RPM: rpmdrake-6.10-1.mga4
CVE:
Status comment:

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

Description Robert Ottlovich 2014-02-02 01:03:37 CET 
The "drakrpm" program crashed. Drakbug-16.26.7 caught it.

While refreshing.

undefined value for mandatory argument 'text' encountered at /usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/edit_urpm_sources.pm line 195.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm:295
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1501
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:748
ugtk3::main() called from /usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/gui.pm:609
Rpmdrake::gui::ask_browse_tree_given_widgets_for_rpmdrake() called from /usr/libexec/drakrpm:822
main::run_treeview_dialog() called from /usr/libexec/drakrpm:846

Theme name: oxygen-gtk
Kernel version = 3.12.8-desktop-2.mga4
Distribution=Mageia release 4 (Official) for x86_64
CPU=Pentium(R) Dual-Core  CPU      E5200  @ 2.50GHz
Manuel Hiebel 2014-02-02 12:01:56 CET

Blocks: (none) => 11778
Summary: drakrpm crashed => drakrpm crashed (undefined value for mandatory argument 'text')

Manuel Hiebel 2014-02-02 12:02:21 CET

Assignee: bugsquad => thierry.vignaud

Comment 1 Manuel Hiebel 2014-05-01 20:17:10 CEST 
use a new one for procedure

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

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