928534 – ldconfig aborts on signal 6

Bug 928534 - ldconfig aborts on signal 6

Summary: ldconfig aborts on signal 6

Status:	RESOLVED DUPLICATE of bug 908780

Alias:	None

Product:	openSUSE Tumbleweed
Classification:	openSUSE
Component:	Basesystem (show other bugs)
Version:	201503*
Hardware:	x86-64 openSUSE 13.2

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2015-04-24 12:32 UTC by Dr. Werner Fink
Modified:	2015-04-26 12:31 UTC (History)
CC List:	3 users (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Dr. Werner Fink 2015-04-24 12:32:39 UTC

On the virtual system d136 I see

     d136:~ # ldconfig -v
     [...]
             libcom_err.so.2 -> libcom_err.so.2.1
             libcrack.so.2 -> libcrack.so.2.9.0
     /usr/lib64:
     Aborted

interesting

     d136:~ # ldconfig -vn /usr/lib64

works

     d136:~ # uname -r
     3.19.4-1-desktop
     d136:~ # rpm -q glibc
     glibc-2.21-3.2.x86_64

beside this an older binary of ldcondig also shows this.  Therefore I guess that something in the layout of the library structure and/or configuration for ldconfig cause the abort.

Comment 1 Dr. Werner Fink 2015-04-24 12:36:08 UTC

Maybe a dup of bug #908780

Comment 2 Dr. Werner Fink 2015-04-24 12:56:19 UTC

Specifying all paths used by ldconfig on the command line with option -n does not crash.

Comment 4 Bernhard Wiedemann 2015-04-26 12:31:35 UTC

the machine has / type xfs 

and the problem went away after
ln -sf libnuma.so.1.0.0 /usr/lib64/libnuma.so.1

so definitely a dup

with numa being installed on 2015-01-22
this might be fixed meanwhile in kernel, but one cannot be sure

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