Apache OpenOffice (AOO) Bugzilla – Issue 122006
Unexpected quits after using load/save and print preview
Last modified: 2015-09-12 02:08:05 UTC
Just downloaded OpenOffice (1300hrs 05/04). Seems superior to Mac Apps, but having problems with stability. After using print preview in WP, App 'quits unexpectedly' and generates report. In Preferences, clicking on Load/save has the same effect. Are there any changes to my OS that I need to carry out before using OpenOffice? I would like to use OpenOffice as it is close to MS Office, without the expense of buying Office for Mac.
When I went to print preview in OpenOffice 4.0.1, on a MacBook running OS X Yosemite (v. 10.10.3), AOO crashed. When I went to restart AOO, a persistent message box opened up with the message "The last time you opened OpenOffice, it unexpectedly quit while reopening windows. Do you want to try to reopen its windows again?" Two buttons are provided in the message box "Don't Reopen" and "Reopen" When making either button choice, nothing happens, and the box remains open. Utility menu items like print, save and save as are non-functional, as are CMD-key combinations that execute same. Also, AOO cannot be shutdown using the AOO menu function "Quit OpenOffice." Such functions are "greyed-out." The only way to quit AOO is to "Force Quit" using the OS X menu. I have tried to remove the disk image and download an another copy of AOO 4.0.1, but after I completed the re-install overlay, the same bug appeared with the same symptoms. I cannot use AOO at all, at this point.
My issue is the same as Mjolnir. My Open Office is unusable and indicates that the last time it was used was back in August when this error message box first appeared. I haven't removed and re-installed AOO (glad I didn't go thru that hassle since it apparently doesn't work). But I have forced my Mac to quit/restart by removing power, since with the error box present, there is no other way to either Quit AOO or restart/quit my Mac. The forced Quit Restart did not cause AOO to recover. the Error message is still there.