From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: Open office hangs before opening any windows. The strace I ran didn't help me find the bug. However, when I moved the files: .openoffice-install-log .openoffice-lock .rhopenoffice1.1/ to a temp directory and started oowriter it failed as follows [jdunn@porkrind ~]$ oowriter sh: line 1: 14292 Aborted LD_LIBRARY_PATH=/usr/lib/ooo-1.1:/usr/lib/ooo-1.1/program /usr/lib/ooo-1.1/program/setup -R:/tmp/ooo-wrapper.autoresponse.file.k14290 -v -nogui >~/.openoffice-install-log 2>&1 Installation of OpenOffice.org 1.1.2 failed: 'LD_LIBRARY_PATH=/usr/lib/ooo-1.1:/usr/lib/ooo-1.1/program /usr/lib/ooo-1.1/program/setup -R:/tmp/ooo-wrapper.autoresponse.file.k14290 -v -nogui > ~/.openoffice-install-log 2>&1' Running a piece of this by hand: [jdunn@porkrind ~]$ LD_LIBRARY_PATH=/usr/lib/ooo-1.1:/usr/lib/ooo-1.1/program /usr/lib/ooo-1.1/program/setup ** ERROR **: Resource problem creating 'blah/orbit-jdunn' aborting... Aborted After a little thinking I realized that I had set the environment variable TEMP to the value blah. So, openoffice is using $TEMP as the path for temporary files. From what my coworker and I remember TEMP is a windows environment variable, not Unix. The same behavior can be seen by setting TMP to invalid values. This isn't exactly a bug, but could be awfully confusing for the user (as it was for me =). A modification to the startup scripts for openoffice should allow for clearer failure in all cases. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. in gnome-terminal run the following 2. export TEMP=blah 3. oowriter 4. watch it sit (assuming there is no writable "blah" directory) alternatively: 1. in gnome-terminal run the following 2. rm -rf ~/.openoffice-* ~/.rhopenoffice1.1 3. oowriter 4. watch it fail as described Actual Results: An annoying hang, and a cryptic failure. Expected Results: certainly no hang, and hopefully a clear error that could be acted on by someone with less experience. Additional info:
The hang isn't openoffice.org's fault. the oowriter etc script calls gconftool-2 --get which hangs with such an invalid TEMP dir. The hang is the real nuisance, at least if you didn't hang there you would later see the "** ERROR **: Resource problem creating 'blah/orbit-jdunn' aborting..." error message from oowriter like you do from the setup program, which would give the hint as to what is wrong. This is coming from libORBit-2, nothing OOo can do about that either (e.g. run gedit from a gnome-terminal with TEMP set to blah). Whether orbit-2 should honour TEMP rather than TMPDIR, or hardcode to P_tmpdir is a question for them :-)
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier.