On 2013/02/15 2:37 PM, Oliver-Rainer Wittmann wrote:
It is the root cause for both which are more or less the same. A user profile corruption in the extension databases causes crashes when checking for extension updates. Extension updates can be triggered manually or automatically as part of the checking for an application update.
I'd rephrase that: These problematic "bundled extensions" disappeared when the older OpenOffice was removed and the new Apache OpenOffice didn't reinstall them at the same locations as they were before. All this time the user profile stays exactly the same, it is not corrupted.
The problem was that there was a bug in the OpenOffice code which wasn't prepared for the bundled extensions to disappear. Oliver's fix to catch the exceptions thrown in that case fix that problem.
An example from the real world exemplifies this scenario: you get a cloak room ticket, then somebody accidentally moves your coat in the cloak room and later the attendant dies from the distress of the coat not being where he expected it to be from the ticket's text. The ticket was never corrupted at all. The fix is simply to stay cool if stuff was moved around.
The "hackish" way to solve the problem was to remove the user profile altogether so that OpenOffice never knew there were such extensions. In the cloak room analogy above this corresponds to dropping the ticket before the easily irritable attendant ever gets a reason to get over-excited.
Herbert
