Bug 12632 - drakrpm crashed
Summary: drakrpm crashed
Status: RESOLVED DUPLICATE of bug 12390
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 15:59 CET by Sébastien Forestier
Modified: 2014-12-13 09:54 CET (History)
2 users (show)

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


Attachments

Description Sébastien Forestier 2014-02-06 15:59:17 CET
The "drakrpm" program crashed. Drakbug-16.26.7 caught it.

Launching rpmdrake from command line right after trying to add urpmi.addmedia of blogdrake repositories using url:  urpmi.addmedia --wget --distrib http://ftp.blogdrake.net/mageia/mageia4/x86_64, the latter operation which failed twice due to wrong MD5SUM.

Since the double failure of urpmi.addmedia operation I haven't been able to launch rpmdrake anymore.

undefined value for mandatory argument 'is_active' encountered at /usr/libexec/drakrpm line 701.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/5.18.1/Carp.pm:100
Carp::croak() called from /usr/lib/perl5/vendor_perl/5.18.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm:59
Glib::Object::Introspection::__ANON__() called from /usr/libexec/drakrpm:701
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=Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
Comment 1 Sébastien Forestier 2014-02-06 16:10:32 CET
Just tried launching rpmdrake interface from withing drakconf, no change.
Also tried "rm -rf /etc/urpmi/mediacfg.d/BlogDrake-4-x86_64/" then "rpmdrake" again from root shell, no change.

Rpmdrake still crashes before even displaying any window, with same error message.

Note: Mageia 4 as upgraded from Mageia 3, through the urpmi.addmedia --distrib manual online method, with the urpmi --auto --auto-update --download-all [...] command.

Used rpmdrake many times with Mageia 4 before this crash at launch that appeared first right after the failed addition of blogdrake repositories.

(note: my mother tongue is French in case that's easier for some readers, I can also use French or Spanish)
Comment 2 Sébastien Forestier 2014-02-06 16:15:01 CET
Also found a few Blogdrake entries in /etc/urpmi/proxy.cfg, removed them, no change.

Why is it that Blogdrake repositories got almost added but not completely with this MD5SUM error?

Shouldn't the MD5SUM check be done first, then once successful start writing anything to urpmi configuration?

Also, how does it come that rpmdrake is so fragile - such a central tool to Mageia should be much more robust and not crash in front of wrong input (which I haven't figured out yet, what is).
Comment 3 Sébastien Forestier 2014-02-06 16:22:03 CET
Again, removed blogdrake entries in /var/lib/urpmi (rm -rf /var/lib/urpmi/BDK-*), but still stuck.

Then, removed (urpmi.removemedia) the 3 MLO (Mageia Linux Online) repositories that I had added not long before adding the Blogdrake repos (Core, Nonfree & Tainted, all x86_64), no improvement. rpmdrake still crashes at launch from commandline with same message, haven't tried other launch methods but unlikely to make any change now since it didn't before.
Comment 4 Sébastien Forestier 2014-02-06 16:29:18 CET
Oh, fogot to provide the commandline output of rpmdrake:

Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 296.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 545.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 545.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 545.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 545.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 545.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 545.
Use of uninitialized value $value in numeric eq (==) at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 545.
Impossible to set by_group view as default
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 296.
Comment 5 Manuel Hiebel 2014-02-06 16:32:12 CET
dup

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

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

Comment 6 Sébastien Forestier 2014-02-06 16:35:01 CET
As the command line output indicates it seems to be linked with the setting of by_group view, or anything that's linked to UI, because drakrpm-update works well (based on similar code but not doing by_group view for example, and likely not parsing the corresponding group information).
Comment 7 Sébastien Forestier 2014-02-06 16:41:23 CET
Duplicate confirmed - following the comments in bug 12390 I deleted /root/.rpmdrake and it worked again.
Comment 8 Herman Viaene 2014-12-12 16:01:57 CET
Encountered the same problem on MGA4-64 on a new PC. Has been updated till a week ago, but now trying to update or open the window to install a package , bombs out with this error as in Comment 4.
I deleted /root/.rpmdrake as in Comment 7. The result is that the update window comes up querying the list of updates, and then bombs out again, all following tries on any operation, also bombs out.

CC: (none) => herman.viaene

Comment 9 Angelo Naselli 2014-12-12 16:59:35 CET
If the error is the one reported in comment #1
the line 701 of drakrpm seem to set the checkbox for "Search in _full package names"
So i wonder if it's that the offending option that is somehow missed in configuration file e.g. NVR_searches.

CC: (none) => anaselli

Comment 10 Herman Viaene 2014-12-13 09:54:18 CET
(In reply to Angelo Naselli from comment #9)
> If the error is the one reported in comment #1
> the line 701 of drakrpm seem to set the checkbox for "Search in _full
> package names"
> So i wonder if it's that the offending option that is somehow missed in
> configuration file e.g. NVR_searches.

From Comment 1 it  is difficult to say, since at the first try the operations were not launched from the CLI, but further on the messages are the same as Sébastien reports in Comment 4.

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