Issue 99754 - program cannot be started: language could not be determined
Summary: program cannot be started: language could not be determined
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 3.0.1
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: joergbudi
QA Contact: issues@framework
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2009-03-01 22:53 UTC by aziem
Modified: 2009-03-30 09:26 UTC (History)
2 users (show)

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


Attachments
python code to reproduce (159 bytes, text/plain)
2009-03-01 22:57 UTC, aziem
no flags Details
batch file to reproduce (69 bytes, text/plain)
2009-03-01 22:58 UTC, aziem
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description aziem 2009-03-01 22:53:45 UTC
When trying to bootstrap OOo 3.0.1 from OOo Python on Win XP (as administrator),
I get the error

Dialog title: 
 soffice - Fatal Error
Body:
 Program cannot be started.
 Language could not be determined

The same works fine not executed within Python; or with OOo 2.4 (so it is a
regression); or with Linux (so it's just Windows OOo 3.0).

I use this method, probably like many folks, to start bootstrap OOo. I myself
would like to update these OOo benchmarks[1] and introduce a cross-platform
benchmarks.
[1] http://www.oooninja.com/2008/05/openofficeorg-getting-faster-benchmark.html

I will attach a kit to reproduce with Python code and .batch file.
Comment 1 aziem 2009-03-01 22:57:49 UTC
Created attachment 60568 [details]
python code to reproduce
Comment 2 aziem 2009-03-01 22:58:06 UTC
Created attachment 60569 [details]
batch file to reproduce
Comment 3 Olaf Felka 2009-03-02 06:55:41 UTC
please have a look.
Comment 4 Stephan Bergmann 2009-03-30 09:24:02 UTC
I can reproduce the problem with OOO300m15 (i.e., OOo 3.0.1) but not with
OOO310m8 (i.e., toward OOo 3.1.0), so this is probably duplicate to one of the
various OOo/Python issues that got fixed for OOo 3.1.  (Caveat:  Due to both the
OOo-specific python.exe and soffice.exe using the URE_BOOTSTRAP environment
variable, the python.exe and soffice.exe need to be from the same OOo
installation---in case you have more than one installed---so that the
URE_BOOTSTRAP value set by python.exe is also correct for soffice.exe to use.)
Comment 5 Stephan Bergmann 2009-03-30 09:26:31 UTC
.