Issue 107440 - Office crashes if Program Path contains Special Character
Summary: Office crashes if Program Path contains Special Character
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO320m3
Hardware: PC Windows, all
: P2 Trivial (vote)
Target Milestone: OOo 3.2
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks: 99999
  Show dependency tree
 
Reported: 2009-12-04 10:11 UTC by weko
Modified: 2017-05-20 10:24 UTC (History)
6 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 weko 2009-12-04 10:11:23 UTC 
The Office crashes if the program path contains a special character like German 
Umlauts (äöü).

If you open an ODF document via double-click in Windows Explorer and the 
corresponding application (Writer, Calc etc.) in not already running, the Office 
crashes.

Same behavior if you open a document via New|Recent documents from Start-
Center.

Furthermore the StarBasic macros are not available.
Comment 1 mikhail.voytenko 2009-12-04 10:53:41 UTC 
The problem is that Barkley DB seems not to be able to handle paths with special
characters. As result the package manager throws always exceptions when it is
asked for installed packages and so on. This exception causes the problem.

The workaround would be to catch the exception in this scenario, so that the
documents could be loaded. But the main problem remains: the package manager can
not be used in this case at all.
Comment 2 mikhail.voytenko 2009-12-04 11:56:29 UTC 
The workaround that fixes the scenario has been integrated in cws fwk131.
Comment 3 mikhail.voytenko 2009-12-04 15:27:38 UTC 
mav->tm: Please verify the issue.
Comment 4 thorsten.martens 2009-12-08 14:43:42 UTC 
Checked and verified in cws fwk131 -> OK !
Comment 5 caolanm 2010-03-14 14:08:07 UTC 
*** Issue 110101 has been marked as a duplicate of this issue. ***