Bug 12514

Summary: drakhardware crashed (Can't load URPM/URPM.so' for module URPM: /lib64/libncursesw.so.5: undefined symbol: _nc_putchar)
Product: Mageia Reporter: x x <packthead>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: mageia, thierry.vignaud
Version: 4Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: report.bug.xz
install.log
ddbug.log

Description x x 2014-02-02 11:31:11 CET
The "drakhardware" program crashed. Drakbug-16.26.7 caught it.

lancement de urpmi when detect materiel with mcc.
same issue when trying to use urpmi
i made an upgragde from mageia 3

Can't load '/usr/lib/perl5/vendor_perl/5.18.1/x86_64-linux-thread-multi/auto/URPM/URPM.so' for module URPM: /lib64/libncursesw.so.5: undefined symbol: _nc_putchar at /usr/lib/perl5/5.18.1/x86_64-linux-thread-multi/DynaLoader.pm line 190.
 at /usr/lib/perl5/vendor_perl/5.18.1/urpm/msg.pm line 8.
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.18.1/urpm/msg.pm line 8.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.18.1/urpm/msg.pm line 8.
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.18.1/urpm.pm line 8.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.18.1/urpm.pm line 8.
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.18.1/urpm/media.pm line 6.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.18.1/urpm/media.pm line 6.
Compilation failed in require at /usr/lib/libDrakX/do_pkgs.pm line 255.
Perl's trace:
standalone::bug_handler() called from /usr/lib/libDrakX/do_pkgs.pm:255
do_pkgs_standalone::are_available() called from /usr/lib/libDrakX/do_pkgs.pm:103
do_pkgs_common::is_available() called from /usr/lib/libDrakX/network/thirdparty.pm:279
network::thirdparty::get_available_packages() called from /usr/lib/libDrakX/pkgs.pm:212
pkgs::detect_network_drivers() called from /usr/lib/libDrakX/pkgs.pm:226
pkgs::detect_hardware_packages() called from /usr/libexec/drakhardware:496

Theme name: oxygen-gtk
Kernel version = 3.12.8-server-2.mga4
Distribution=Mageia release 4 (Official) for x86_64
CPU=AMD Phenom(tm) II X4 980 Processor
Comment 1 Manuel Hiebel 2014-02-02 12:03:26 CET
looks like urpmi is broken

urpmi --auto-update does work ?

CC: (none) => thierry.vignaud

Comment 2 Thierry Vignaud 2014-02-02 13:54:02 CET
this is already answered in initial report.
What does report the following command:
rpm -q urpmi perl-URPM perl lib64ncursesw5

Keywords: (none) => NEEDINFO

Thierry Vignaud 2014-02-02 13:54:24 CET

Summary: drakhardware crashed => drakhardware crashed (Can't load URPM/URPM.so' for module URPM: /lib64/libncursesw.so.5: undefined symbol: _nc_putchar)

Comment 3 x x 2014-02-02 16:15:16 CET
rpm -q urpmi perl-URPM perl lib64ncursesw5
rpm: symbol lookup error: /lib64/libncursesw.so.5: undefined symbol: _nc_putchar
Comment 4 x x 2014-02-02 16:17:43 CET
upgrade have been made from dvd 64 kde

seems paths have changed between mageia 3 and 4...but i might be wrong
Comment 5 x x 2014-02-02 16:19:14 CET
urpmi --auto-update
Can't load '/usr/lib/perl5/vendor_perl/5.18.1/x86_64-linux-thread-multi/auto/URPM/URPM.so' for module URPM: /lib64/libncursesw.so.5: undefined symbol: _nc_putchar at /usr/lib/perl5/5.18.1/x86_64-linux-thread-multi/DynaLoader.pm line 190.
 at /usr/lib/perl5/vendor_perl/5.18.1/urpm/msg.pm line 8.
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.18.1/urpm/msg.pm line 8.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.18.1/urpm/msg.pm line 8.
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.18.1/urpm.pm line 8.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.18.1/urpm.pm line 8.
Compilation failed in require at /usr/sbin/urpmi line 26.
BEGIN failed--compilation aborted at /usr/sbin/urpmi line 26.
[root@packthead ~]#
Comment 6 Thierry Vignaud 2014-02-02 16:39:23 CET
Can you attach your /root/drakx/report.bug.xz file?
Comment 7 x x 2014-02-02 17:49:48 CET
Created attachment 4914 [details]
report.bug.xz
Comment 8 Thierry Vignaud 2014-02-02 18:46:09 CET
Comment on attachment 4914 [details]
report.bug.xz

This is an old mga3 install logs.
Don't you've more recent files in /root/drakx?
The files of interest would be latest ddebug.log & install.log files

Attachment 4914 is obsolete: 0 => 1

Comment 9 x x 2014-02-02 19:08:59 CET
Created attachment 4916 [details]
install.log
Comment 10 x x 2014-02-02 19:11:15 CET
Created attachment 4917 [details]
ddbug.log
Comment 11 x x 2014-02-02 19:15:57 CET
maybe an information that might be usefulas it concern ncurse :

i've made a compilation  of upstream ncurse to try to install modules for bitcoins
but i didn't uninstall mageia ncurse.

if it may help...
Comment 12 Thierry Vignaud 2014-02-02 19:20:00 CET
That explains your logs.
ddebug.log shows that there were already issues with lib64ncurses in the system to upgrade thus failling to select some packages.
Thus none of rpm/perl-URPM/urpmi or lib64ncursesw5 or even basesystem was updated.

You screwed you system.
You should never never overwrite a system library or you can destroy the system.

You should either reinstall from scrath or boot the install DVD with the "rescue" option, then manually install lib64ncurses from the DVD.

You can also download http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/4/x86_64/media/core/release/lib64ncurses5-5.9-17.mga4.x86_64.rpm

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

Comment 13 Thierry Vignaud 2014-02-02 19:21:29 CET
In mga5, we could rely on URPM in order to examine the chrooted system for installed packages.
Comment 14 x x 2014-02-02 19:36:04 CET
;-)

yes i know there might always be a risk to do that, but maybe mageia team shouldn't ignore compilation's option on important parts of system ;-)

go for a reinstall from scrath...

Resolution: INVALID => FIXED

Comment 15 Sander Lepik 2014-02-02 19:54:37 CET
Nothing was fixed here..

CC: (none) => mageia
Resolution: FIXED => INVALID

Comment 16 x x 2014-02-02 20:18:37 CET
no,but it's always possible, i won't reinstall before days...