Bug 786228 - %{_libdir}/xulrunner-2/libxul.so is truncated
Summary: %{_libdir}/xulrunner-2/libxul.so is truncated
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xulrunner
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-31 18:49 UTC by Michel Alexandre Salim
Modified: 2012-12-21 13:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-21 13:52:47 UTC
Type: ---


Attachments (Terms of Use)

Description Michel Alexandre Salim 2012-01-31 18:49:30 UTC
Description of problem:
If xulrunner is installed, every time ldconfig is triggered I get this warning:

 ldconfig: file /usr/lib64/xulrunner-2/libxul.so;4f25a0c5 is truncated

Version-Release number of selected component (if applicable):
xulrunner-9.0.1-2.fc17.x86_64 -- on Rawhide's usrmove repo

How reproducible:
Always

Steps to Reproduce:
1. yum install xulrunner
2. ldconfig, or install another package that trigger ldconfig
  
Actual results:
The given warning is triggered on both steps 1 and 2

Expected results:
No warning

Additional info:

Comment 1 Martin Stransky 2012-02-24 15:05:47 UTC
Do you still see it?

Comment 2 Michel Alexandre Salim 2012-02-25 09:14:40 UTC
I just tried doing an 'ldconfig' and didn't see it anymore. Not sure when it stopped though.

Comment 3 Martin Stransky 2012-02-27 07:35:32 UTC
Okay, Thanks.

Comment 4 Michel Alexandre Salim 2012-03-02 02:01:48 UTC
And the problem is back:

✗ sudo ldconfig
[sudo] password for michel: 
ldconfig: file /usr/lib64/xulrunner-2/libxul.so;4f25a0c5 is truncated

✗ rpm -V xulrunner
✗ rpm -q xulrunner
xulrunner-10.0.1-3.fc17.x86_64
✗ rpm -qf $(which ldconfig)
glibc-2.15-23.fc17.x86_64
glibc-2.15-23.fc17.i686

Comment 5 Martin Stransky 2012-03-02 06:56:32 UTC
I wonder if prelink is involved here.

Comment 6 Michel Alexandre Salim 2012-03-03 05:21:29 UTC
Any way I can test that, while I can still reproduce the bug?

Comment 7 Martin Stransky 2012-12-21 13:52:47 UTC
Still uble to reproduce. Please reopen if you see it again.


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