oocalc: Due to an unexpected error, OpenOffice.org crashed
Posted: Sat Oct 17, 2009 6:15 pm
[PROBLEM]
On Ubuntu hardy 8.04, OpenOffice spreadsheet (v2.4) suddenly stopped working (I presume after a recent package upgrade). Other parts of OpenOffice.org (draw, writer, ...) were working fine.
When starting it, you are presented a message saying:
[SOLUTION]
I reinstalled the following packages:
That fixed the startup-crash problem.
[Things I've tried, that didn't help]
1) To check if it might have been a local (user-specific) problem, I tried removing the "~/.openoffice.org2" folder to reset my user-specific settings, but the error persisted.
2) Starting it from the comandline (/usr/bin/oocalc), gave the following error message:
3) It was claiming to recover a document, so I ran it with "oocalc -norestore". Did not help either.
On Ubuntu hardy 8.04, OpenOffice spreadsheet (v2.4) suddenly stopped working (I presume after a recent package upgrade). Other parts of OpenOffice.org (draw, writer, ...) were working fine.
When starting it, you are presented a message saying:
The list of "The following files will be recovered" was empty, and after pressing "OK" nothing happened - and OpenOffice.org did not start.Due to an unexpected error, OpenOffice.org crashed. All the files you were working on will now be saved. The next time OpenOffice.org is launched, your files will be recovered automatically.
[SOLUTION]
I reinstalled the following packages:
Code: Select all
openoffice.org-base-core
openoffice.org-calc
openoffice.org-common
openoffice.org-core[Things I've tried, that didn't help]
1) To check if it might have been a local (user-specific) problem, I tried removing the "~/.openoffice.org2" folder to reset my user-specific settings, but the error persisted.
2) Starting it from the comandline (/usr/bin/oocalc), gave the following error message:
I've tried installing the package openoffice.org-java-common, which removed the javaldx error, but did not fix the startup problem of oocalc.javaldx: Could not find a Java Runtime Environment!
3) It was claiming to recover a document, so I ran it with "oocalc -norestore". Did not help either.