Description of problem:
When the problem described in bug 243304 occurs (and probably on other X-related
errors too), Openoffice fails to indicate that there was a problem. This is
confusing and irritating, and makes it difficult to know what to write in a bug
Version-Release number of selected component (if applicable):
No error messages, no log messages, no error codes, nothing. It just terminates
with an exit code of zero.
Openoffice should print a descriptive error message on stderr and return a
nonzero exit code.
yeah, and it actually has the code to do so, but it's being side-stepped. Fix
checked into rawhide and F-7, if there's another F-7 update it'll be part of it.
openoffice.org-2.2.1-18.1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.