Bug 54064 - ACCESSIBILITY: Java JRE 1.7u6 now includes Java Access Bridge 2.0.3, default settings may toggle LibO Accessibility Tools state, result for non administrators group users error message "program soffice.bin version stopped interacting with Windows"
Summary: ACCESSIBILITY: Java JRE 1.7u6 now includes Java Access Bridge 2.0.3, default ...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL: http://docs.oracle.com/javase/7/docs/...
Depends on:
Blocks: a11y-Windows
  Show dependency treegraph
Reported: 2012-08-25 20:49 UTC by V Stuart Foote
Modified: 2018-02-26 11:17 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

truncated registrymodifications.xcu for non-priviledged user (deleted)
2012-08-25 20:49 UTC, V Stuart Foote

Note You need to log in before you can comment on or make changes to this bug.
Description V Stuart Foote 2012-08-25 20:49:22 UTC
Created attachment 66117 [details]
truncated registrymodifications.xcu for non-priviledged user

Install of LO performed as Administrator.

Quick start and Windows Explorer were disabled in a custom installation.

The per-user configurations--C:\Users\<userName>\AppData\Roaming\LibreOffice\3\user--are cleared prior to launch attempts. 

Profiles appear to be correctly created for privileged users but not for regular users.

Administrators group users are able to launch LibreOffice, quickly complete Java extension configurations and move onto LibreOffice panel. Review of the registrymodifications.xcu shows a fully populated configuration.

But, for non-priviledged users, a launch of LibreOffice hangs at the configuration splash screen--and will eventually time out with errors "stopped working"

Looking at Process Explorer -- can see soffice.exe running, with soffice.bin making repeated calls to java.exe.

The registrymodifications.xcu for non-priviledged users appears truncated with only three entries (attached), administrators group users get a fully formed .xcu.

Again this is only for an unpriviledged user. For administrators group priviledged users. If launched "run as administrator" LibreOffice comes up immediately--but is using the profile for the Administrator account. 

Possibly a side effect of the work on fdo#51252 ?
Comment 1 V Stuart Foote 2012-08-26 02:36:19 UTC
Going to call this "Not our Bug".

System was configured with Java Access Bridge with Accessibility Tools active. So believe it was a Java Runtime Environment configuration issue of unresolved nature.

To set things correct, had to remove ALL Java runtime and dependencies.

Removed LibreOffice and cleaned file system and Windows registry.

Had to uninstall NVDA screen reader (2012.2.1)

Had to uninstall Oracle Java Access Bridge (JWin 1.0 based install/config)

Had to uninstall JRE 1.7u06, 32 and 64 bit.

Cleaned file system and Windows registry of all Java, LibreOffice, JavaAccessBridge elements.

Removed per-user LibreOffice profiles.



Logged on as Administrator, installed from scratch:

Oracle JRE 1.7u06, 32-bit

JavaAccessBridge (by running JWin.exe (v1.0))

Verified JAVA_HOME variable set to "C:\Program Files (x86)\Java\jre7"

Added ";%JAVA_HOME%\bin" to PATH variable

Verified "java -version" at a command prompt returned correct details

Installed NVDA screen reader (2012.2.1) and verified function in Windows.

Installed LibreOffice (aka RC2), verified launch and function of accessibility tools.

Loged off, and logged on as non-priviledged user.

Launched LibreOffice--reasonable period of time to complete configuration of extensions.

LibreOffice panel start panel opens with no issues.

Verify creation of a complete registrymodifications.xcu, and javasettings_Windows_x86.xml for the non-priviledged user.

Able to toggle Accessibility Tools on and off, and verify full function of NVDA screen reader.


Suspect issue was with the Oracle Java Access Bridge and version upgrade of 32-bit Java Runtime Environment and possibly a LibreOffice Accessibility Tools JAR.  Expect though that this rather fragile set up will be a problem area for LibreOffice users dependent on Java Access Bridge based screen readers and screen magnifiers.

My advice for folks is to plan to completely remove all Java JRE based components when upgrading versions to be certain that all components are in a known state.

Comment 2 V Stuart Foote 2012-08-26 04:16:28 UTC
Possibly related to the #fdo50584 / #fdo50371 Java Runtime and MSVC100.dll? And the Oracle Java http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7184978 issue.

If so, will have a rough patch of LibreOffice user requiring support of Accessibility Tools as they are transitioning to LO 3.6.1 and upgrading to JRE 1.7 builds.

Needs to be a better way of clearing and reestablishing JRE configuration and dependencies.
Comment 3 V Stuart Foote 2012-08-26 15:46:05 UTC
Reopening--at least for now, to allow a bit more exposure of potential for JRE misconfiguration during upgrades causing a poor LibreOffice experience--especially for users dependent on JRE based Accessibility Tools.

Still feel this is a NOTOURBUG, but we have made other accommodations, e.g. https://bugs.freedesktop.org/show_bug.cgi?id=51252 inclusion of MSVCR100.dll, so we might have to solve the JRE issues impacting Java Access Bridge and LO/AOO Accessibility Tools for Windows and OSX environments.

Comment 4 V Stuart Foote 2012-08-28 14:24:15 UTC
Further to comment 1, appears Oracle has now added Java Access Bridge v2.0.3 to the JRE 1.7u6 installers. It installs but by default is not active (notes in URL above).

I had been using JAB 2.0.2 prior to a JRE 1.7u6 in-place upgrade. Which was done just before the first installation of LO (uninstalled 

If the new JAB 2.0.3 was set inactive by the installer it could have tripped up LibreOffice installation when I selected Enable accessibility at installation.

In removing everything and starting with the JRE 1.7u6 -> JWin (installer for JAB 2.0.2) -> NVDA v2012.2.1 (screen reader) and finally LO, I would have ended the JAB reset to active at start of LO installation.

Think this could end up being very painful for folks. Not so much that it doesn't work, rather that we'll be causing a lot of manual configuration churn to make things stable for our Accessibility and Assistive Technology Tools.
Comment 5 V Stuart Foote 2012-09-05 14:31:24 UTC
Possibly related to: https://bugs.freedesktop.org/show_bug.cgi?id=38913
Comment 6 Xisco Faulí 2018-02-26 11:17:40 UTC
The content of attachment 66117 [details] has been deleted