Bug 81733

Summary: incompatibility with Java
Product: LibreOffice Reporter: kbnmsf1
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED NOTABUG    
Severity: normal CC: barta, vsfoote
Priority: medium    
Version: 4.2.5.2 release   
Hardware: Other   
OS: Windows (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:

Description kbnmsf1 2014-07-25 07:18:12 UTC
Problem description: 

Steps to reproduce:
1. launch libreoffice

Current behavior:
displays window "configuration has changed, please change java RE in Tools Options LibreOffice Advanced"
Clicking OK has no effect
Closing windows sets it to reopen immediately

Not possible to move forward. Needs to close application with Task Manager.

Not stable bug, happens in one of my Windows account, not in the other one.

Uninstalled and reinstalled LibreOffice twice, without improvmenent.

Using Java JRE7

Expected behavior:
Launch Libre Office

              
Operating System: Windows 8
Version: 4.2.5.2 release
Comment 1 V Stuart Foote 2014-07-26 15:41:59 UTC
Please verify that you have a 32-bit JRE available on path and specified for LibreOffice to use.
Comment 2 kbnmsf1 2014-07-30 01:27:08 UTC
Java path:
1.7	1.7.0_65	http://java.sun.com/products/autodl/j2se	C:\Program Files (x86)\Java\jre7\bin\javaw.exe		true

"specified for LibreOffice to use."
I don't know what this mean.
Comment 3 V Stuart Foote 2014-07-30 02:27:53 UTC
(In reply to comment #2)
> Java path:
> 1.7	1.7.0_65	http://java.sun.com/products/autodl/j2se	C:\Program Files
> (x86)\Java\jre7\bin\javaw.exe		true
> 
> "specified for LibreOffice to use."
> I don't know what this mean.

Open a Microsoft Command Window and at the prompt enter the command:

java -version

If it report the 64-bit build, that won't work as you must be using a 32-bit JRE.

You can also check the variables %JAVA_HOME%, or %JRE_HOME% if set and verify that the 32-bit version is available to you.

You may have to modify the system %PATH% environment variable, to ensure that the 32-bit version is being called rather than the 64-bit.
Comment 4 V Stuart Foote 2014-07-30 02:34:51 UTC
Additionally, you can always clear the configuration for the JRE--and force it to be rebuilt--in you user profile by deleting the file javasettings_Windows_x86.xml

That is located in the C:\Users\<username>\AppData\Roaming\LibreOffice\4\user\config folder.

Another approach is to simply rename (or delete) the entire user profile by renaming LibreOffice to LibreOfficeOLD, or such.
Comment 5 kbnmsf1 2014-07-30 03:19:41 UTC
Thank you.
As explained, this bug was not present in another Windows account. I copied and replaced the content of the javaconfig with that of the working account.
I then reinstalled LibreOffice 4.2 to a similar effect (the java warning is different, it proposes to configure the JRE, opens a new windows that becomes a dead-end).
However, the short cut to a previous installation of LibreOffice 4.2 that I had archived and clicked by error this time launched LibreOffice 4.2 without problem.

Temporary conclusions:
- issue is linked to javaconfig file
- default installation of LibreOffice 4.2 does strange things to the javaconfig file in some circumstances
- user should not have to worry about locating and editing the javaconfig file for LibreOffice to work.

Thank you.
Comment 6 V Stuart Foote 2014-07-30 13:24:03 UTC
Sorry, but your posting of Steps to Reproduce are not clear. Can you capture a screen clip of any message that pops-up.  Also, what outcome of performing the steps of comment 3?

Please review the TDF Wiki User Profile article-- https://wiki.documentfoundation.org/User_Profile

We need you to determine if--with the profile removed (or renamed)--there is still an issue with LibreOffice configuring the 32-bit Java Runtime Environment for your installation, for use with a new LibreOffice user profile with your Windows user account.
Comment 7 kbnmsf1 2014-07-30 15:02:01 UTC
It's working now.
I didn't follow step 3 exactly, instead I copied and pasted content of javaconfig file that worked in a different Windows account to replace the same in the account where the bug existed. This was enough to resolve the problem.
Comment 8 V Stuart Foote 2014-07-30 15:10:40 UTC
OK then setting this resolved.