To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54013
                  Issue #:|54013
                  Summary:|Soffice fails to startup on 64 bit machine
                Component:|Word processor
                  Version:|OOO 2.0 Beta2
                 Platform:|All
                      URL:|
               OS/Version:|Linux
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|configuration
              Assigned to:|mru
              Reported by:|robtanner





------- Additional comments from [EMAIL PROTECTED] Tue Aug 30 23:10:34 -0700 
2005 -------
This issue applies to staring soffice regardless of the application.  The
platform is RH ES4/AMD64.  When attempting to start soffice, the following
errors occur:

/opt/openoffice.org1.9.125/program/javaldx: error while loading shared
libraries: /usr/lib/libc.so.6: invalid ELF header
/opt/openoffice.org1.9.125/program/pagein: error while loading shared libraries:
/usr/lib/libc.so.6: invalid ELF header
/opt/openoffice.org1.9.125/program/soffice.bin: error while loading shared
libraries: /usr/lib/libc.so.6: invalid ELF header

Invoking soffice.bin (skipping the soffice startup shell script) works okay
despite the last error message -- I presume the problem is the soffice shell
script itself.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to