[Libreoffice-bugs] [Bug 50371] CONFIGURATION: JRE 7.x incompatibility not resolved

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=50371

--- Comment #23 from cincenko at seznam.cz 2012-08-09 16:24:03 UTC ---
(In reply to comment #15)
> Actually the problem is not with LibreOffice, but rather the configuration of
> Oracle Java on your Windows system.
> 
> Oracle's installers are not very fastidious about cleaning up prior releases of
> Java. Also they copy the last installed Java executables into the
> Windows\System32 directory rather than correctly establishing a system
> JAVA_HOME environment variable to direct to the program. And they establish
> Windows registry keys that are not fully removed during uninstallation.
> 
> LibreOffice can not include a dedicated Java Runtime Environment package due to
> licensing issues, so it is dependent on what YOU provide in your Windows
> system. If your system is misconfigured--it is NOT a LibreOffice bug.
> 
> LibreOffice does correctly function with a Java JRE 1.7 build.  If you want to
> run with an Oracle Java 1.7 JRE, and you should, you have to fix your JRE
> installation Windows. A LO enhancement to try to fix Oracle's mess of JRE
> instllation on Windows would be helpful, but that is not the present capability
> and the responsibility lies with us as users of these two software packages to
> accomodate.
> 
> As a general rule in Windows OS maintain only one JRE, either a 1.6 or a 1.7
> release, but not both! Also, LibreOffice is a 32-bit program--if on a 64-bit
> Windows system, be sure to provide a 32-bit JRE.
> 
> Fortunately you can leave the LibreOffice 3.5.x installation intact, with minor
> configuration changes. And to get things running most work is with the JRE:
> 
> First, fully remove the Java JRE 1.6 (and JRE 1.7) including manual editing of
> the Registry and some clean up of the file system. 
> 
> (1) Run the Windows Add/Remove programs as Administrator and uninstall ALL
> Sun/Oracle Java components. You'll probably want to remove/reinstall any 3rd
> Party Java applets as they will have configurations pointing to old
> installation, the Java Access Bridge as an example.
> 
> (2) Open a command window "Run as Administrator" and run
> "regedit.exe"--navigate to the Key
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft (for 64-bit Windows) and
> HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft (for both 32-bit AND 64-bit Windows) and
> delete it.  And while still in registry editor, also delete the JreMetrics
> Keys.
> 
> (3) Also delete the JavaSoft keys for each user account
> HKEY_CURRENT_USER\Software\JavaSoft, starting with the Administrator account.
> And then from a new regedit.exe session for each user
> 
> (4) Use Windows Explorer and navigate to the C:\Program Files\Java folder.
> Delete jre6. Delete jre7.  And, if on 64-bit Windows, navigate to C:\Program
> Files (x86)\Java. Delete jre6. Delete jre7.
> 
> (5) Check in the C:\Windows\System32 folder for java.exe, javaw.exe,
> javaws.exe--running the uninstallers should have removed them but if still
> present delete.
> 
> (6) All Java should be off the Windows sytem at this point. Search the registry
> for Java, and the Windows file system for java.exe if you'd like to be certain.
> 
> (7) Reboot!
> 
> Now locate and download for installation the "Windows Offline" Oracle JRE 1.7
> installers. 32-bit (and 64-bit if applicable). Use this Oracle provided link: 
> http://www.java.com/en/download/manual.jsp
> 
> (1) if on 64-bit windows, run the 64-bit JRE 1.7u5 installer.
> 
> (2) run the 32-bit JRE 1.7u5 installer.
> 
> (3) the 32-bit install should have placed 32-bit versions of Java into the
> C:\Windows\System32 folder. But it could also end up being the 64-bit version
> on 64-bit windows.  So you need to force use of the 32-bit Java. Delete the
> java.exe, javaw.exe, javaws.exe from the system32 folder--they are just copies
> and you'll be establishing a location for them on the Path variable.
> 
> (4) Create a system environment variable JAVA_HOME (by Java programming
> convention). Done either from Computer --> Properties --> Advanced system
> settings --> Environment Variables, in the System variables portion of the
> panel.  Or set directly in the registry in the
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
> key. Assign the path to the 32-bit Java installation to the JAVA_HOME variable,
> e.g. "C:\Program Files (x86)\Java\jre7".  Mind the spaces.
> 
> (5) from the Advanced system settings, or the Environment key in the registry
> edit the PATH variable to insert the value "%JAVA_HOME%\bin;"--after the
> %SystemRoot% entries.  Note: setting the JAVA_HOME variable does nothing by
> itself--it is the addition of JAVA_HOME\bin in the Path variable that is doing
> the correction.
> 
> (6) verify that the correct JRE will run by entering on the start menu or from
> command window '"%JAVA_HOME%\bin\java.exe" -version'
> 
> Now clear the LibreOffice configruation file for Java and allow it to be
> rebuilt.
> 
> (1) In each user account
> C:\Users\<userName>\AppData\Roaming\LibreOffice\3\User\Config there will be a
> configuration file "javasettings_Windows_x86.xml" simply delete it. It will be
> rebuilt with now correct Java Runtime Environment settings.  Adjust to
> C:\Documents and Settingon Windows XP
> 
> (2) Launch LibreOffice. Navigate to Tools --> Options --> Java, check the radio
> button to use a Java Runtime Environment. Should have no error, and should see
> just a single value offered. An Oracle Corp Vendor entry, Version 1.7.0_u5 (or
> the version just installed). And below a "Location" value showing the entry for
> the version just installed, e.g. C:\Program Files (x86)\Java\jre7.
> 
> Configuring this way will disrupt some of Oracles auto configruation for JRE
> use on 64-bit system--defaulting most to use 32-bit JRE. But for most users
> this is going to be more functional.




Amazing, this works. Please post it also everywhere else. Thanks.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.