This is directly related to Ubuntu/Debian, but may also apply to other linux distros that install their own version of OOo.
When attempting to start OOo3RC1 and OOo3RC2 (OOO300m7) after installation, OOo may crash with a: terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' error when run from a terminal. If you run directly, the program will go into a crash state and continue to loop attempting to recover an untitled document. (get out of the loop my opening a terminal and using: killall soffice). This will occur if during the "Welcome to OpenOffice.org 3.0" startup and registration process you have elected to "Transfer personal data". The problem is that Ubuntu/Debian uses a newer version of libdb4 (libdb4.6) than that supplied with OOO300m7 (libdb-4.2). In short, the tranfer process copies the newer database files from the existing OOo into the new OOo3RC2 user profile (~/.openoffice.org/3), OOo3RC2 then attempts to open the new database using libdb-4.2, and the end result is a crash. http://www.openoffice.org/issues/show_bug.cgi?id=94240 provides details. Workaround: 1. If you are just installing OOo3RC2 for the first time simply uncheck the "Transfer personal data" box on page 2 of the registration dialog. 2. If you have already installed but are experiencing the crash: - delete ~/.openoffice.org (*your existing ~/.openoffice.org2 should be left alone*) - restart OOo3RC2 (/opt/openoffice.org3/program/soffice) and follow #1 above. Issues after the workaround: You will need to setup OOo3RC2 as a new user/install - meaning that you will need to reenter your personal data/settings and reinstall your extensions. Current known issues for OOo3RC2 are listed here: http://wiki.services.openoffice.org/wiki/OOoRelease30_rc2_knownissues If you experience problems with this version please keep in mind that it is a "Release Candidate" and is not a final release. Therefore it's important to file an issue as soon as you find it so that the problem can be worked on before the 3.0 release, or scheduled to be fixed later in 3.0.1. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
