https://issues.apache.org/ooo/show_bug.cgi?id=121625
--- Comment #7 from Oliver-Rainer Wittmann <[email protected]> --- I was able to reproduce crashes of AOO 3.4 and AOO 3.4.1 which are upgrades of a former OOo 3.3 installation. The problem is caused by the OOo 3.3 bundled extensions - namely three dictionaries - which are not correctly migrated. The AOO 3.4/3.4.1 installation process more or less "removes" the intrinsic bundled extensions. Only their folders (found in the installation folder) and the extension database entries (found in the user profile as Berkeley DBs) are left. The extension database entries are imported into the new extension database format. Thus, regarding these bundled extensions the state is inconsistent. The crashes are triggered when the extensions are accessed in order to check for updates. The check for extension updates can be performed manually or is triggered by the automatic check for an application update, if the check for an application update is configured respectively. The problem persists even, if the user profile has been renamed/removed. This is causes by the still existing bundled extension folders. These folders "let the office think" that such bundled extensions are available. Thus corresponding extension database entries are created during the startup after the user profile had been renamed/removed. This results more or less in the same inconsistent state as above. A possible workaround is to remove the following files from the user profile: - $USERPROFILE/3/user/extensions/bundled/extensions.pmap - $USERPROFILE/3/user/extensions/bundled/extensions.db, if it exists. -- You are receiving this mail because: You are on the CC list for the bug.
