Bug 58495 - LibreOffice fails to launch if mismatch between user directory encoding and system locale
Summary: LibreOffice fails to launch if mismatch between user directory encoding and s...
Status: RESOLVED DUPLICATE of bug 103525
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.6.4.3 release
Hardware: x86 (IA32) Windows (All)
: medium blocker
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-19 03:40 UTC by Socratis
Modified: 2023-01-03 09:21 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Error message with LO 3.6.4 (10.70 KB, image/png)
2012-12-19 03:40 UTC, Socratis
Details
Error message with LO 4.0.0b1 (9.67 KB, image/png)
2012-12-19 03:42 UTC, Socratis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Socratis 2012-12-19 03:40:17 UTC
Created attachment 71781 [details]
Error message with LO 3.6.4

Under Win2K/WinXP/Win7/Win8 create a user with a non-ASCII (actually Greek) home directory e.g "Χρήστης" (translation="User").

If the system locale is set to Greek, all is good. But, if the system locale is set to English:

1) LO 3.6.4 fails to launch with a fatal error:
The service manager is not available
("cannot open /URE/services.rdb: 21")
Start setup application to repair to repair the installation from CD, or the folder containing the installation packages.

2) LOdev 4.0.0.0.beta1 fails to launch with a fatal error:
The application cannot be started.
[context="user"] caught unexpected
com.sun.star.ucb.ContentCreationException: Cannot create folder
(invalid path):

Notes:

1) For a user with an English name, no problem with either locale.

2) The bug doesn't exhibit itself under *nix or MOSX because they won't allow you to create a non-ASCII home directory.
Comment 1 Socratis 2012-12-19 03:42:01 UTC
Created attachment 71782 [details]
Error message with LO 4.0.0b1
Comment 2 Urmas 2012-12-19 10:15:28 UTC

*** This bug has been marked as a duplicate of bug 47163 ***
Comment 3 Mike Kaganski 2023-01-03 09:21:54 UTC

*** This bug has been marked as a duplicate of bug 103525 ***