[Libreoffice-bugs] [Bug 124776] New: Running soffice.exe with a relative path from Command Prompt doesn't work
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Tue Apr 16 17:34:20 UTC 2019
https://bugs.documentfoundation.org/show_bug.cgi?id=124776
Bug ID: 124776
Summary: Running soffice.exe with a relative path from Command
Prompt doesn't work
Product: LibreOffice
Version: unspecified
Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: libreoffice-bugs at lists.freedesktop.org
Reporter: tml at iki.fi
Description:
Try to run soffice.exe from Command Prompt (this is specific to Windows,
obviously) using instdir\program\soffice.exe. The soffice.exe and soffice.bin
processes run for a short while but exit then without doing anything.
Using an absolute pathname C:\where\ever\instdir\program\soffice.exe works.
Not sure how long this has been broken. But surely the intent is that using
just instdir\program\soffice.exe should work? (Like it does when run from a
Cygwin shell in mintty, and on Linux.)
The problem seems to be that getIniFileName_Impl() in sal/rtl/bootstrap.cxx
does not return a file: URL but a relative pathname, huh.
And that is because osl_getExecutableFile() does not return an absolute
filename, but what happens to be in argv[0]. Surely we should use some other
way to find out the executable's pathname and not rely on what happens to be in
argv[0] (Also, sal_detail_initialize() takes a plain char argv, not a wchar_t
one, and thus is fairly broken already when LibreOffice is installed in a
pathname that isn't expressible in the system codepage. We should use
GetModulePathNameW(NULL,...).
Steps to Reproduce:
.
Actual Results:
.
Expected Results:
.
Reproducible: Always
User Profile Reset: No
Additional Info:
.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20190416/bc29b5d5/attachment-0001.html>
More information about the Libreoffice-bugs
mailing list