JDK-6409883 : Seeing "Java Accessibility Bridge for GNOME loaded" in headless installs
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: solaris_11
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: solaris_nevada
  • CPU: generic
  • Submitted: 2006-04-06
  • Updated: 2018-09-05
While installing Solaris (using 1.5) via a tip line, the message 
"Java Accessibility Bridge for GNOME loaded" appears. See below:

Please specify the media from which you will install Solaris Software 4 for
SPARC Platforms.

Alternatively, choose the selection for "Skip" to skip this disc and go on to
the next one.


2. Network File System
3. Skip

   Media [1]: 2

Please specify the path to the network file system from which you will install
Solaris Software 4 for SPARC Platforms.

Example:   server:/path_to_install_area

If you do not wish to install at this time, enter S to skip.
To select a different media, enter B to go Back.
    [] osento:/export/solaris/nv_s4_5cd

Launching installer for Solaris Software 4 for SPARC Platforms. Please Wait...

Java Accessibility Bridge for GNOME loaded.

The following items will be installed:

Product: Solaris packages (part 4)
Location: /
Size: 601.5 MB
     Solaris packages (part 4)    601.5 MB

Ready to Install

1. Install Now
2. Start Over
3. Exit Installation

   What would you like to do [1]? 

Solaris packages (part 4)

Pausing for 30 seconds at the "Summary" screen. The wizard will continue to
   the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
   continue. [c]

EVALUATION after some discussion it was decided to fix the doc.

EVALUATION the fix for this problem in AWT is rather easy, but we will need to change API documentation since we have the following in javadoc for Toolkit.getDefaultToolkit() * Also loads additional classes into the VM, using the property * 'assistive_technologies' specified in the Sun reference * implementation by a line in the 'accessibility.properties' * file. The form is "assistive_technologies=..." where * the "..." is a comma-separated list of assistive technology * classes to load. Each class is loaded in the order given * and a single instance of each is created using * Class.forName(class).newInstance(). This is done just after * the AWT toolkit is created. All errors are handled via an * AWTError exception. Perhaps, it should be fixed in accessibility bridge instead.