Issue 114541 - Office shows error msg and cannot start due to broken extension xcu file
Summary: Office shows error msg and cannot start due to broken extension xcu file
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO330m7
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: carsten.driesner
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks: 111112
  Show dependency tree
 
Reported: 2010-09-16 09:23 UTC by carsten.driesner
Modified: 2017-05-20 10:22 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
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 <http://hg.services.openoffice.org/cws/fwk158/rev/0ea6b6129b32>
"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.