So I ran chmod -x /opt/openoffice.org/ure/bin/javaldx and then tried to start openoffice again and this is what I got:

bash-3.1$ openoffice.org3
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[Java framework]sunjavaplugin.so could not load Java runtime library:
file:///usr/lib/gcj-4.2.3/libjvm.so./opt/openoffice.org3/program/soffice: line 134: 9919 Segmentation fault "$sd_prog/$sd_binary" "$@"


Do you have any other ideas? This is frustrating lol

This error only appears when java isn't allowed to run.



This is there both ways however.

So I went ahead and uninstalled OO 3.0 and installed 2.4.2 and everything works fine with that version. For future reference though if anyone knows why that was messing up let me know.

Thanks,
Steven

I have the exact same problem trying to run the package

openoffice.org-3.0.0_en_US-i586-2_rlw.tgz

under Slamd64 12.1. The error is:

$ soffice
[Java framework]sunjavaplugin.so could not load Java runtime library:
file:///usr/lib64/../lib/gcj-4.2.3/libjvm.so./usr/bin/soffice: line 134: 24453 Segmentation fault "$sd_prog/$sd_binary" "$@"

You'll be wanting to run a build of OOo specifically for x86_64. In this case, it's provided by Andrew Brouwers. The stuff to build it can be found at http://slackadelic.com/~thrice/openoffice.org/. To get the OOo source, run "grep DOWNLOAD openoffice.org.info | cut -d \" -f 2 | wget -i -" in the directory containing those files, then run (as root) "./openoffice.org.SlackBuild"

Since the SlackBuild doesn't build from source, but instead rebuilds the binary distribution into something usable, this shouldn't take too long at all. In the end, you'll have an installable package in /tmp.

Note that while you are likely to find help at the LQ Slackware forums, the proper place to bring questions about Slamd64 is http://forums.slamd64.com. Happy Slacking!