Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

The upgrade does indeed present an opportunity to install apple java
before invoking any of the apps. Having had prior experiencne with the
Apple Java fiasco and took the OS up on its offer, lol.  Unfortunately
it looks like that install doesn't necessarily "take" (while I am sure
the software is installed, my guess is that there are environmental
variables that are not being fully set until some conjunction of the
planets or the like

I did find a clue in that There are other apps it would appear that are
suffering the same problems (not acknowledging the presence of the Apple
JRE.)  I have rebooted and reinstalled the Apple Java a number of times,
and have finally been able to get it to "take" (though installation was
exactly the same as prior instances and rebooting was not required.)

I can tell you that I had to invoke a different app that demanded apple
java that would not crash, and having installed Apple java (a 5th time)
in response to that apps prompt, it "took".  Then,  on pulling up LO and
looking at the JVM dialog,  one could see the Apple JRE in the selector
box (first time a java version appeared there since the upgrade.)   This
may also suggest that this problem may be a result of Apple changing
locations of the JRE (that is apparently what broke Macports) but I am
just guessing there. Apple did rip out all Java (1.6 AND Oracle 1.7) on
upgrade, and I am wondering about LO's response where it is required to
use a JVM, but can't find it -- in other words, why didn't LO (or other
apps for that matter) see the Apple 1.6 JRE when initially installed
when prompted by the OS, even after reboot.

This smacks very much of the same kind of Java issues I saw on
MountainLion. Eventually one could get Java 1.7 running along side Java
1.6, the latter being used for general OS invocation while the former
could be used via CLI and for browsers...  At present I now have LO
running as it has "found" Apple Java 1.6 

LO needs to make the jump so that it can use 1.7 or make it clear that
LO will be java-free by version 4.x or some such....  but I think the
latter would be potentially unfortunate

On 11/1/13, 1:07 AM, Stephan Bergmann wrote:
On 10/31/2013 05:02 PM, Marc Grober wrote:
It looks like the thread on addressing operating LO 4 under OSX
Mavericks may have taken a small detour.

Yes, Java is a bit of a disaster on OSX, and yes once you upgrade Apple
blows away your java install so you have to start all over (but will
prompt you to install their java.)

Assuming you accept their invitation on reboot (the install will invite
you to install an Apple Java jre) and then try to run LO ( you

Does the OS X upgrade itself indeed mention the possibility to
download an Apple JRE?  I never noticed that.

will likely get an error message that allows you to either install a
java (the install does not say what it is installing, nor from where) or

What I know is the following:

After upgrade or fresh install of OS X (at least since 10.7, IIRC), a
java executable is installed that is merely a stub, bringing up a
dialog inviting you to download and install the real Apple JRE 6.

When LO is run on such a "stub-only" machine, as soon as it tries to
detect a JRE (which might be rather sooner than expected, see the
"LibreOffice 4.1.2 and Mac OS X 10.9 (Mavericks)" thread on this
mailing list), it will run the stub java executable and thus trigger
the dialog.

Now, for some it reportedly works fine to download and install the
Apple JRE via the dialog and continue working with LO (or even not
download and install it, and keep living with LO nagging you about a
missing JRE).  But for some LO reportedly keeps crashing from that
dialog onwards, no matter how they interact with that dialog.  But I
only know about that from here-say, and have never seen the problem
myself, and never seen a backtrace of the crashing LO that could give
us a clue what's going on there.

(I "wasted" my opportunity to find out for myself when soon after
upgrading to OS X 10.9 I got confronted with the java stub dialog
outside the LO context and downloaded/installed it before I came
around to start LO.)

But since, as described in the "LibreOffice 4.1.2 and Mac OS X 10.9
(Mavericks)" thread on this mailing list, one unexpected side-effect
of bundling the Wiki Publisher extension with LO on Mac OS X is that
LO tries to detect a JRE as soon as you type a key in Writer, we
decided to deliver LO 4.1.3 for Mac OS X (from
<>) without a bundled Wiki
Publisher extension.  That should help to somewhat mitigate the
problem and have less people be annoyed by the problem.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.