Issue 114541

Summary: Office shows error msg and cannot start due to broken extension xcu file
Product: General Reporter: carsten.driesner
Component: codeAssignee: carsten.driesner
Status: CLOSED FIXED QA Contact: issues@framework <issues>
Severity: Trivial    
Priority: P2 CC: issues, joerg.skottke, mdxonefour
Version: OOO330m7   
Target Milestone: OOo 3.3   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 111112    

Description carsten.driesner 2010-09-16 09:23:45 UTC
It's possible that people have a broken XCU file in their user folder that is
part of an extension. Starting the new OOo 3.3 beta version which uses this user
folder leads to an error message 

"Oracle Open Office 3.3 - Fatal Error"
"The application cannot be started. A general error occurred while accessing
your central configuration." 

and the Office cannot start.

This is caused by a more restricted xml parser included in the new configuration
manager implementation. Unfortunately most users are not able to resolve these
problems and have to remove/rename their user folder. This results losing their
user settings.
Comment 1 carsten.driesner 2010-09-16 09:25:53 UTC
CCed: md
Comment 2 Stephan Bergmann 2010-09-16 13:36:38 UTC
fixed as <>
"generally ignore erroneous xcs/xcu files during startup (typically from
extensions installed pre 3.3)" -- during OOo start up, exceptions from reading
xcs/xcu files are now swallowed and only reported as OSL_TRACE, which
unfortunately only outputs anything in specially built debug-mode OOo; the net
effect is that extensions with bad xcs/xcu files that are carried over from a
previous <3.3 installation do not work properly, and the user not getting a hint
that and why that is so
Comment 3 Olaf Felka 2010-09-17 10:43:36 UTC
CCed: jsk
Comment 4 carsten.driesner 2010-09-20 10:51:39 UTC
cd: Taking over for verification.
Comment 5 carsten.driesner 2010-09-20 10:52:10 UTC
cd: Verifed on CWS.