From: John Robinson <jbr100uk@googlemail.com>
To: gentoo-accessibility@lists.gentoo.org
Subject: [gentoo-accessibility] Difficulty using the Java Access Bridge with Sun-jdk and Orca
Date: Sat, 26 Sep 2009 19:51:21 +0100 [thread overview]
Message-ID: <4ABE62A9.3070307@googlemail.com> (raw)
Hi everyone. I've just installed Sun-jdk-1.6.0.15, Orca-2.26.3 and
Java-access-bridge-1.6.0, all installed with Portage inside a Gnome
terminal. I know there is a page of instructions about how to build and
install the Java Access Bridge on the Orca website at
http://live.gnome.org/Orca, but I assumed the Gentoo ebuild of Java
Access Bridge would do all this for me. When I thought I'd installed
everything correctly, I went to the demo folder of the Sun-jdk and typed
'java -jar Notepad.jar'. orca said that the Java Access bridge was
being loaded and then that the application was being registered. Orca
promptly cut out and when I pressed Alt and Tab to get to where I
thought the Notepad Java application would be, Orca said 'Notepad
Inaccessible'. When I alt-tabbed back to the terminal window from where
I'd started the Java Notepad, the screen was full of messages which had
apparently been produced by the Java program as it tried to launch
Notepad. Unfortunately, I can find no way of capturing these, so any
help with this would be appreciated. For some reason or other, although
it appears to be correctly installed, my Java Access Bridge is not
working with Orca and I have no idea why this is. I have an AMD64
system which runs Java in 64-bit mode only. The Orca page about Java
Access Bridge mentions that you need a file called something like
libjava-access-bridge.so which I do not appear to have. Could this be
the cause of my problem.
Many thanks for any help.
Regards,
John Robinson
reply other threads:[~2009-09-26 18:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ABE62A9.3070307@googlemail.com \
--to=jbr100uk@googlemail.com \
--cc=gentoo-accessibility@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox