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


Activating a Java Runtime Environment in LibreOffice 3.5.4  took a little
while to complete its initial load following upgrade, but  the JRE 1.7
update 5  does function correctly with JAB 2.02 installed with LibreOffice
3.5.4 on 64-bit Windows 7.  So, not  a problem with the LibreOffice
Accesibility and the Assistive technology tools.

Installation of the updates (32bit and 64bit versions from  did
not corrupt my LibreOffice user profile, and JAB 2.0.2 was not affected. The
NVDA screen reader continues to work correctly with LibreOffice.

So, the JRE installer is not the problem, and that leaves LibreOffice user
profile configuration issues.

I suspect you were just unluky this time round with the Java update
misconfiguring some component of your profile. 

I beleive Bjørn's guidance to delete or to rename the
*javasettings_Windows_x86.xml*  file is the correct way to clear the issue
by allowing your user profile to rebuild. 

Or you could completely remove your LibreOffice user profile and allow it to
be rebuilt with defaults.

The full profile is the folder located at *C:\Users\<your user
name>\AppData\Roaming\LibreOffice\3\user* which can be renamed.


View this message in context:
Sent from the Users mailing list archive at

For unsubscribe instructions 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.