Bug 87844 - Could not create Java implementation loader
Summary: Could not create Java implementation loader
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Extensions (show other bugs)
Version:
(earliest affected)
4.3.5.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-29 22:18 UTC by bioline
Modified: 2014-12-30 15:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bioline 2014-12-29 22:18:43 UTC
"Could not create Java implementation loader" shows in LibreOffice_4.3.5.2 with Java properly installed in Linux Mint 17.1. 
When turned back to LO 4.3.4.1 everything works properly (Java environments visible in Options and extensions working as expected).

Best greetings and wishes for new year from grateful user :-)

KP
Comment 1 V Stuart Foote 2014-12-30 04:36:26 UTC
That is going to be an issue with incorrect detection of the JRE by the LibreOffice install. 

It has been an issue for folks from time to time: 
http://ask.libreoffice.org/en/question/5712/extension-installation-could-not-create-java-implementation-loader/
https://bugs.freedesktop.org/show_bug.cgi?id=50584
https://bugs.freedesktop.org/show_bug.cgi?id=50371

Often cleared by simply completing selection of appropriate JRE from:

Tools -> Options -> Advanced: Java Options panel.

Please try that, otherwise more complete details are needed...

Also, many aspects at play, what build (32-bit or 64-bit) of LibreOffice DEB
package did you install? And, was it an official build from the LibreOffice site, or one of the partial installers from the Community.LinuxMint.com repository?

Post up the the build identification string from the Help -> About LibreOffice dialog.

Which build of Java JRE are available on your system--Oracle, or OpenJDK? 6, or 7 or 8?
Comment 2 bioline 2014-12-30 08:14:05 UTC
OK - that was my fault. I made mistake and installed 32 bit version on 64 bit Linux Mint. When changed to 64 bit LO it works as it should. 

Next time I will do triple check before suspecting a bug :-)

Regards
KP
Comment 3 V Stuart Foote 2014-12-30 15:12:36 UTC
No worries, but setting issue resolved...