To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=95369
User mux2005 changed the following:
What |Old value |New value
================================================================================
Keywords|needmoreinfo, oooqa |oooqa
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Fri Dec 18 07:27:30
+0000 2009 -------
The crash can also be reproduced without installing the uno.pkg extension. To do
this, change the instructions as follows
1. Instead of WollMux.uno.pkg download version 5.9.3 of WollMuxBar.jar from
http://forge.osor.eu/frs/?group_id=11
4b. After the normal step 4, edit the wollmux.conf to add the following line at
the end
ALLOW_EXTERNAL_WOLLMUX "true"
5.-7. Instead, after closing all OOo instances launch
java -jar WollMuxBar.jar
This will start OOo via the bootstrap mechanism. The dialog described in step 8.
will pop up. The remaining steps are the same.
--------
As you can see even when just communicating with OOo via the socket connection,
it will crash. In this scenario there's none of our code executing in OOo's JVM.
As you will also notice, in this scenario OUR GUI remains even after OOo
crashes, because it's not our Java code that crashes.
---------------------------------------------------------------------
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]
