Bug 1989 - After installing RPM 4.8.xx the graphical tools for updating/installing rpm's is broken
Summary: After installing RPM 4.8.xx the graphical tools for updating/installing rpm's...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
: 2296 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-07-01 21:57 CEST by Daniel Kreuter
Modified: 2011-07-28 08:32 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Daniel Kreuter 2011-07-01 21:57:25 CEST
Description of problem:

After installing the package mentioned in the title the graphical tools in mcc shut down with an unexpected error. urpmi still works fine.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Installing Mageia in a VM
2. Activate Cauldron (see http://www.mageia.org/wiki/doku.php?id=cauldron)
3. Go into the graphical tool in MCC and choose install & remove software
4. click on apply to install auto-selected packages
5. start Install Updates or Install & Remove Software again
Comment 1 Daniel Kreuter 2011-07-01 22:00:05 CEST
After rebooting the vm MCC doesn't start anymore.
Comment 2 Ahmad Samir 2011-07-02 02:00:05 CEST
Start if from terminal and post the output here.
Comment 3 Daniel Kreuter 2011-07-02 10:08:12 CEST
drakrpm
/usr/bin/perl: symbol lookup error: /usr/lib/libDrakX/auto/c/stuff/stuff.so: undefined symbol: Perl_Gthr_key_ptr
Comment 4 Daniel Kreuter 2011-07-02 17:02:55 CEST
Ok after a full upgrade using urpmi the drak* tools are working again.

But it's not very nice if you update some packages and after that the Gui tools for installing RPM Packages aren't working.

Maybe we should fix that before Mageia 2 Release so we are able to do a full upgrade from Mageia 1 to 2 ??
Comment 5 Ahmad Samir 2011-07-02 17:53:44 CEST
A botched update/upgrade is a botched update/upgrade, and in this case it was a perl upgrade, urpmi does prioritise and update itself, rpm, perl, glibc... etc first, judging by the fact the urpmi from terminal worked.

But when there's a major (perl in this case) upgrade, you can't cherry pick updates, you have to get them all or some stuff will barf like you saw; in this particular case it was a flaky mirror (seeing your thread on the -dev ML).

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

Comment 6 Ahmad Samir 2011-07-28 08:32:39 CEST
*** Bug 2296 has been marked as a duplicate of this bug. ***

CC: (none) => dantou


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