Description of problem: # /usr/bin/mcc /usr/bin/perl: symbol lookup error: /usr/lib/libDrakX/auto/xf86misc/main/main.so: undefined symbol: Perl_xs_apiversion_bootcheck Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: Clean install of Mageia-5-x86_64-DVD.iso. Default runlevel: 3 Package Group Selection screen has all package groups selected except Other Graphical Desktops. select Gnome and KDE. non-free and tainted media are enabled. Followed with: remove-unused-packages urpmi --downloader wget --auto --auto-update urpme --auto-orphans and reboot. change /5/ to /cauldron/ in /etc/urpmi/urpmi.cfg urpmi.removemedia -y Debug Backport Testing drakrpm-edit-media --expert and enable all media Desktop: KDE Theme: Oxygen Window Decorations: plastik Desktop effects are disabled. 1. click up a terminal 2. su - root 3. mcc Reproducible: Steps to Reproduce:
Should not be part of the problem but I forgot to mention; problem found in a 64 bit VirtualBox guest using vendor VB 5.0.2-102096 and extension pack.
You didn't installed anything from CPAN manually? What reports the following command? rpm -q perl{,-base}
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudSummary: mga6: mcc will not launch. /usr/bin/perl: symbol lookup error: /usr/lib/libDrakX/auto/xf86misc => mga6: mcc will not launch (perl: symbol lookup error: xf86misc: : undefined symbol: Perl_xs_apiversion_bootcheck)
(In reply to Thierry Vignaud from comment #2) > You didn't installed anything from CPAN manually? Nope, pretty much just as the test procedure indicates except for the vendor install of Oracle_VM_VirtualBox_Extension_Pack-5.0.2-102096.vbox-extpack VirtualBox-5.0.2-102096-Linux_amd64.run on host and VB on guest. Everything working on mga5 guest with all updates. Did a VB guest clone to mg6 change /5/ to /cauldron/ in /etc/urpmi/urpmi.cfg urpmi --downloader wget --auto --auto-update --test and ran mcc->Software Management->Update your system answered Yes/Ok and next mcc or drakrpm-update fail to run. > What reports the following command? > rpm -q perl{,-base} # rpm -q perl{,base} perl-5.22.0-6.mga6 package perlbase is not installed I can repeatedly run urpmi --downloader wget --auto --auto-update until nothing installs then mcc will launch.
Keywords: NEEDINFO => (none)
That should have been: rpm -q perl{,-base} Anyway, your issue is that you've drakx-kbd-mouse-x11-1.8-1.mga5 whereas drakx-kbd-mouse-x11-1.8-2.mga6 was uploaded on June 23 so that it was rebuild with perl-5.22 I think the root issue is that you used MageiaUpdate, however it only looks at media tagged as "update" (which core/release is not). You should run "urpmi --auto-select"
Status: NEW => RESOLVEDResolution: (none) => INVALID
(ie update is not the same as upgrade, MageiaUpdate does the former whereas urpmi --auto-select will do both)
(In reply to Thierry Vignaud from comment #4) > That should have been: > rpm -q perl{,-base} # rpm -q perl{,-base} perl-5.22.0-6.mga6 perl-base-5.22.0-6.mga6 > Anyway, your issue is that you've drakx-kbd-mouse-x11-1.8-1.mga5 whereas > drakx-kbd-mouse-x11-1.8-2.mga6 was uploaded on June 23 so that it was > rebuild with perl-5.22 Well, I would have assumed some package should make it mandatory with the other drake updates like drakxtools-16.104-6.mga6.x86_64 Mon-24-Aug > I think the root issue is that you used MageiaUpdate, however it only looks > at media tagged as "update" (which core/release is not). > You should run "urpmi --auto-select" Not many newbies would know to run the command line for software update. I suggest to you running drakrpm-update should have worked anyway because I did have all media enabled/update.
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
Created attachment 6960 [details] /etc/urpmi/urpmi.cfg
Not many newbies are using cauldron, or should use cauldron if they don't know how to work with it :)
CC: (none) => mageia
(In reply to Sander Lepik from comment #8) > Not many newbies are using cauldron, or should use cauldron if they don't > know how to work with it :) Yeah, I hear where you are coming from, but as I misunderstand it, user sees the "There is a new release, do you want to upgrade" I thought drakrpm-update was eventually called to proceed with the upgrade. If so, those first mandatory packages (about 101 in my case) would be install and suggest reboot, and there is where the user will not be able to run mcc or drakrpm-update again.
We don't do upgrade with MageiaUpdate and never did. It never was able to.
Status: REOPENED => RESOLVEDResolution: (none) => INVALID