Bug 66389 - Extensionname: Installation of LanguageTool 2.1 aborts on Mac OS X
Summary: Extensionname: Installation of LanguageTool 2.1 aborts on Mac OS X
Status: RESOLVED DUPLICATE of bug 66703
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Extensions (show other bugs)
(earliest affected) rc
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2013-06-29 22:56 UTC by bugzilla
Modified: 2013-07-09 14:11 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description bugzilla 2013-06-29 22:56:05 UTC
Problem description: The installation of LanguageTool 2.1 is not possible on Mac OS X with LibreOffice (Version RC).

Steps to reproduce:
1. Install LibreOffice (Version RC) on Mac OS X
2. Activate current Java version in the LibreOffice's options (Java Version: 1.6.0_45 from Apple)
3. Try to install LanguageTool 2.1 with Extension Manager for all users

Current behavior: The installation of LanguageTool 2.1 aborts with following message:

(com.sun.star.uno.RuntimeException) { { Message = "javaloader error - no mapping from java to C++ ", Context = (com.sun.star.uno.XInterface) @0 } }

This effect was also detected with Duden Korrektor version 9 and was reported with Bug 66082.

After restart of LibreOffice, the extension LanguageTool 2.1 is listed in the Extension Manager in grey and with the remark “Error: The status of this extension is unknown”. The extension is also added to the Tools in the menu bar but is not working.
Operating System: Mac OS X
Version: rc
Comment 1 Julien Nabet 2013-06-30 10:36:23 UTC
bugzilla: On pc Debian x86-64 with master sources or 4.0.3 Debian packages, I don't reproduce this. It seems Mac specific

Alex/Stephan: same Java error here than fdo#66239, a dup?
Comment 2 Martin Srebotnjak 2013-06-30 20:02:20 UTC
I can confirm this on OSX 10.8.4 on LO41RC1, both versions 2.1 and 2.2.

I uninstalled older versions and tried the new release, but got this message.
Comment 3 Stephan Bergmann 2013-07-09 14:11:39 UTC

*** This bug has been marked as a duplicate of bug 66703 ***