Mavericks Apple Java WAS installed on my machine before LO was invoked,
so it was not simply a matter of Java not being on the machine at the
time of the invocation if Apple supplies as before 32 and 64 bit Java.
How did anyone at LO argue that LO would work under Mavericks if using a
JVM crashes LO? Under what circumstances will LO NOT crash if Use JVM
is selected prior to upgrade? And if the devs knew that Mavericks would
cause LO to crash over a week ago, why wasn't that published clearly?
In my case Java was repeatedly installed after the LO problem, with no
impact on LO
LO blew up even if one started the product by opening a calc file; one
did not have to open write and enter any keystrokes -- by blew up I mean
that the app simply disappears and generates no crash or error report.
It does so starting from command line or gui -- in any event my case
indicates that the problem IS NOT limited to entering text
It will still crash any time you access Zotero, though I now have it
stable enough that I can otherwise use it
so, at present, Zotero plugin will not work with LO because Zotero, no
matter the java supplied to the OS, will not recognize it.
I started a new thread because the existing one seemed to be slipping
sideways :-)
On 11/1/13, 1:24 AM, Stephan Bergmann wrote:
On 10/25/2013 08:59 AM, Stephan Bergmann wrote:
On 10/24/2013 05:18 PM, sberg wrote:
I assume you have installed some LibreOffice extension for
spell/grammar
checking or similar that uses Java. That might explain it if you
experience
crashes now when typing in Writer after upgrading to Mavericks (which
appears to replace any pre-existing Java installation with a
"download it
now" stub).
Can you provide a list of LibreOffice extensions you have installed
("Tools
- Extension Manager...")?
Meanwhile found out that it is the wiki-publisher extension (which comes
bundled with LibreOffice by default) that requires a Java VM to be
instantiated in the LibreOffice process as soon as you type the first
letter in Writer. (See
<http://lists.freedesktop.org/archives/libreoffice/2013-October/056991.html>
"Why typing in Writer instantiates the JVM on Mac OS X" for details.)
So, one quick fix for people who are stuck with Writer keeping crashing
would probably be to move away the wiki-publisher extension that is
bundled in the LibreOffice installation. To do that in Finder, first
make sure LibreOffice is not running, then navigate to the LibreOffice
(aka LibreOffice.app) application, from the right-click menu select
"Show Package Contents", there navigate from "Contents" to "share" to
"extensions" and move the "wiki-publisher" folder to the trash (or move
it to some other place outside the "extensions" folder). Then create a
new folder (with more or less arbitrary name, you can use "Dummy")
within the "extensions" folder. When you start LibreOffice again, the
problem should be gone (it might show a "LibreOffice quit unexpectedly"
dialog once directly while starting, which is an unrelated problem and a
different story, in which case just press the "Reopen" button).
Note that LO 4.1.3 for Mac OS X from
<http://www.libreoffice.org/download> comes without a bundled Wiki
Publisher extension.
Stephan
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] Re: LibreOffice 4.1.2 and Mac OS X 10.9 (Mavericks) (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.