I have rebooted and the crash on opening (the result of letting LO try
to install java from software update on 10.9) of LO 4.1.2.3 has stopped.
LO is now back to prompting for java (there is no access to LO itself)
Tried saying yes to LO's java install via Software Update again -- this
time it results in no change in behavior
Am I correct here in concluding that neither Apple nor Oracle offer a 32
bit java for Mavericks and that as a result users who have updated to
Mavericks will simply be barred from using LO henceforth until some
unspecified time in the future?
BRAVO!
Anyone know of an office suite that works with Mavericks, lol
if the problem is only in extensions, can one use the command line
unopkg to lost and delete the extension causing the problem?
BUT
isn't the zotero plugin java based, and how many thousands of users are
going to be happy about doing without zotero?
At the least, LO should put up a huge banner that says that LO will not
necessarily work with Mavericks and that users are advised NOT to upgrade
--
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) · Marc Grober
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.