To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=102568


User pjessen changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|RESOLVED                  |UNCONFIRMED
--------------------------------------------------------------------------------
              Resolution|WORKSFORME                |
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Mon Jun  8 12:54:25 
+0000 2009 -------
I managed to get the daemon running by adding '-nofirststartwizard'.  I have now
switched to running vanilla OO 3.1, and the issue manifests itself a little
differently.  I still get a core dump, but so far I have not seen the assertion
mentioned initially. 

The daemon I'm running is:

/opt/openoffice.org3/program/soffice.bin -headless -nologo -norestore
-accept='socket,host=localhost,port=8100;urp;StarOffice.ServiceManager'
-nofirststartwizard

My client is the following script:

export PYTHONPATH=/opt/openoffice.org/basis3.1/program
export LD_LIBRARY_PATH=/opt/openoffice.org/basis3.1/program/
export
URE_BOOTSTRAP="vnd.sun.star.pathname:/opt/openoffice.org3/program/fundamentalrc"
taskset 0x1 python /usr/share/ooo3/program/DocumentConverter.py sxwfile pdffile



---------------------------------------------------------------------
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: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to