Bug 47313 - Installation fails with non alpha-numeric characters in program path
Summary: Installation fails with non alpha-numeric characters in program path
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
3.5.1 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-14 09:03 UTC by bellgardt
Modified: 2012-03-18 14:29 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bellgardt 2012-03-14 09:03:17 UTC
I tried to install LibreOffice in parallel to older version as a network image by using the DOS command

	msiexec /a LibO_3.5.1rc2_Win_x86_install_multi.msi

into a folder named d:\$temp. Short before the installation finished the following message appeared:

	MS Visula C++ Runtime Library
	Program ...\unopkg.bin
	This application has requested the Runtime to terminate it
	in an unusual way.

Starting soffice.exe then also led to an error message. This behavior was caused by the $-sign in the path name, which is actually a permissible character for a Windows path. After removing that $ from the path by a rename operation soffice.exe could be run! I suppose that other non-alpha-numeric characters cause the same problem. But another user reported "(" or ")" worked for him in the path name.

When the installation path contains no $-sign the installation finishes successfully. 

A similar problem can be found for LO Portable. This also fails to run when being installed into a path containing "$".
Comment 1 Stephan Bergmann 2012-03-15 01:44:56 UTC
"$" is special in that it is used as a macro prefix in LO's ini file syntax.  There are most definitely various places in the code that do not properly escape "$" in pathnames, leading to confusion when such pathnames are used in combination with the ini file macro expansion machinery.

Better avoid "$" in pathnames.
Comment 2 Andras Timar 2012-03-18 14:29:14 UTC
After reading Stephan's comment, this bug looks like a WONTFIX to me. Sorry.