279825 - ld.so.1: ./mozilla-bin: fatal: relocation error:..... libgklayout.so: symbol __fabsf: referenced symbol not found

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Brant Nelson]

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.5) Gecko/20041221
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.5) Gecko/20041221

I am running Mozilla 1.7.5 on a Sun/Sparc with Solaris 2.8.
When I go to www.cnn.com, Mozilla crashes with the error message:

ld.so.1: ./mozilla-bin: fatal: relocation error: file
/scr/nelson/mozilla175/components/libgklayout.so: symbol __fabsf: referenced
symbol not found
Killed

I also tried the 1.8a6 build and got exactly the same error.

I do not get this error when running 1.7.3.

Reproducible: Always

Comment 1

[timeless]

what fixpacks are you running? and where did you get your mozilla from?

Comment 2

[Brant Nelson]

If I knew what "fixpacks" were I'd tell you, but I do know that I got the
Mozilla builds from the releases page at mozilla.org. If it's patches you're
referring to, I would not at all be surprised if my machine is not up to date.

Comment 3

[Brant Nelson]

I get the exact same behavior in 1.7.6 and 1.8.beta, so I still 
can only run 1.7.3 on my machine. Again, I know nothing about 
patches or how to check them. All I know is that it's a SunBlade 100
running Solaris 2.8. 

Comment 4

[Mick Kelleher]

I've tried it on my Mozilla 1.7.7 on Solaris 10 (patches are current) and it
works fine for me.
I've also tried it on a few Solaris 8 and 9 machines with Mozilla 1.7.5 and they
also work fine.
Saying that they are builds i've compiled myself and all our patches are fairly
recent (within the last 9 months).

The only time i've seen problems like that is when there are patches that are
out of date on a system.
Do you get a warning when Mozilla starts complaining that your patches are out
of date?

My guess is that the recent builds of Mozilla (1.7.5+) were done on a more
recently patched system then the previous builds and that is what's causing the
problem. The C and C++ library patches for Solaris have done this to me plenty
of times in the past and i've had to patch all our systems to correct the problem.

Can you also do a 'ldd' on the mozilla-bin to see where your sourcing your
libraries..
i.e.
ldd mozilla-bin

Comment 5

[Brant Nelson]

Attachment: Dialog box warning about patches

Mozilla doesn't give me warnings about patches, HOWEVER,
I also tried the Solaris 2.8 version of Firefox, and it DOES
give me warnings about patches, PLUS gives me the same error. 
I've included an image of the dialog box. So I've now all but 
concluded that it's due to my having old patches. Presumably when
(if?!) we switch to Solaris 10, I won't have this problem. Installing
patches is not an option, based on past experience with our system
administration people.

Comment 6

[Mick Kelleher]

Hi Brant,

I had a look at the patch revisions you have from the attachment, and you're
going to have to get them updated especially, the C, C++, linker, and Math
library patches. Those patches are very non-envasive to a Solaris system and
would'nt cause any effect on stability, i'd contact your local admin and point
him at this bug ID.

Nominating that this bug be closed as Resolved -> INVALID.

Comment 7

[A. Gill]

I am also seeing this error while running Mozilla 1.7.6 on a Solaris 8 machine
that has all necessary packages and patches for Mozilla 1.7.6.  This issue did
not occur in Mozilla 1.7.3.  It also occurs in Firefox 1.0.4.

Details:
 - The error is always reproducible if I am on the system console and visit
www.wunderground.com.  
 - If I am NOT on the system console (i.e., I ssh into the machine and run
Mozilla) the crash/error does NOT occur.
 - If I am on the system console and I ssh to the host itself, the crash does
NOT occur.  However, if I set DISPLAY=:0 to bypass the SSH tunnel, the crash
will occur.

Comment 8

[mz_v_honda]

I can confirm that in case of Mozilla 1.7.8 on Solaris 8
installing these patches solved this problem at least
I am not able to reproduce.

111721-04
113261-02
114542-01

108434-17
108435-17
108652-83
109147-30
109159-03
109704-03

Comment 9

[A. Gill]

This issue has reoccurred in 1.7.11.

Comment 10

[Thomas Kloeber]

i have the very same error with 1.7.12 on Solaris 2.8.

the only patches i have not installed refer to some additional language support, which i don't need/want.

Comment 11

[Thomas Kloeber]

the solution can be found here:
http://dcs.nac.uci.edu/support/sysadmin/security/archive/msg00810.html

my problem was, that my LD_LIBRARY_PATH pointed to an older version of libm.so.1. after fixing it, i don't seem to get the crash anymore...

thomas

Comment 12

[Mick Kelleher]

This bug has been proven to be a mixture of outdated Sun patches and an incorrectly configured LD_LIBRARY_PATH environment variable.

CLOSED -> INVALID ?

Comment 13

[Alfred Peng]

From the comments above, this bug is related to the Solaris patches. Mark as INVALID for Mozilla.

Feel free to reopen it if you can still reproduce the problem after trying the suggested solutions in comment 11.