Bug 11895 - drakrpm-editmedia crashed
Summary: drakrpm-editmedia crashed
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11778
  Show dependency treegraph
 
Reported: 2013-12-06 08:28 CET by René Lagoni Neukirch
Modified: 2013-12-06 10:57 CET (History)
1 user (show)

See Also:
Source RPM: rpmdrake-6.1-2.mga4
CVE:
Status comment:


Attachments

Description René Lagoni Neukirch 2013-12-06 08:28:44 CET
The "drakrpm-editmedia" program crashed. Drakbug-16.8 caught it.

After having added medias I just tride to remove one again.

Can't call method "to_string" on unblessed reference at /usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/edit_urpm_sources.pm line 92.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm:303
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1498
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:747
ugtk3::main() called from /usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/edit_urpm_sources.pm:1205
Rpmdrake::edit_urpm_sources::mainwindow() called from /usr/lib/perl5/vendor_perl/5.18.1/Rpmdrake/edit_urpm_sources.pm:1234
Rpmdrake::edit_urpm_sources::run() called from /usr/libexec/drakrpm-editmedia:38

Theme name: oxygen-gtk
Kernel version = 3.12.3-server-1.mga4
Distribution=Mageia release 4 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i5-3350P CPU @ 3.10GHz


PS. The instability and error level in these kind of packages and upgrades etc. seams increasing ... albeit we are far down the road towards final release.
Thierry Vignaud 2013-12-06 09:46:22 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2013-12-06 10:56:48 CET
Fixed in 6.2

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Thierry Vignaud 2013-12-06 10:57:32 CET

Blocks: (none) => 11778


Note You need to log in before you can comment on or make changes to this bug.