To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=99754
User sb changed the following:
What |Old value |New value
================================================================================
Status|UNCONFIRMED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |WORKSFORME
--------------------------------------------------------------------------------
------- Additional comments from s...@openoffice.org Mon Mar 30 08:24:02 +0000
2009 -------
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.)
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org
For additional commands, e-mail: issues-h...@framework.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
