Closed Bug 282514 Opened 20 years ago Closed 19 years ago

firefox reports errors on starting

Categories

(Firefox :: General, defect)

Other
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: jonrysh, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0

On certain Linux platforms, e.g. FC3, firefox reports these errors when started
from the console:

$ firefox
grep: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such fileor directory
sed: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
cut: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory


Reproducible: Always

Steps to Reproduce:
1. See above
Actual Results:  
grep: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such fileor directory
sed: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
cut: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory


Expected Results:  
firefox starts without errors.

The problem is that LD_ASSUME_KERNEL=2.2.5 breaks grep, sed, and cut on these
platforms.  You may not need this at all -- I don't think the 2.2 kernel has
been in use for about 4 years.  If you do, the following seems to fix things, at
least on my machine:

$ diff -c /usr/bin/firefox.bk /usr/bin/firefox
*** /usr/bin/firefox.bk Wed Nov 10 22:17:35 2004
--- /usr/bin/firefox    Wed Feb 16 15:04:31 2005
***************
*** 116,130 ****
         fi
      fi

      # export this temporarily - it seems to work with old and new
      # versions of the JVM.
      export LD_ASSUME_KERNEL=2.2.5
!
!     # get the version
!     JVM_VERSION=`$JVM_COMMAND -version 2>&1 | grep version | cut -f 3 -d " " |
sed -e 's/\"//g'`
!
      unset LD_ASSUME_KERNEL

      case "$JVM_VERSION" in
        (1.3.0*)
        # bad JVM
--- 116,131 ----
         fi
      fi

+     # get the version
+
      # export this temporarily - it seems to work with old and new
      # versions of the JVM.
      export LD_ASSUME_KERNEL=2.2.5
!     JVM_INFO=`$JVM_COMMAND -version 2>&1 `
      unset LD_ASSUME_KERNEL

+     JVM_VERSION=`echo $JVM_INFO | grep version | cut -f 3 -d " " | sed -e
's/\"//g'`
+
      case "$JVM_VERSION" in
        (1.3.0*)
        # bad JVM
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.