Description of problem: I'm trying to see the various openoffice apps using the accessibility tools and failing. Version-Release number of selected component (if applicable): openoffice.org-writer-1.9.128-2.2.0.fc5 openoffice.org-impress-1.9.128-2.2.0.fc5 openoffice.org-core-1.9.128-2.2.0.fc5 How reproducible: 100% Steps to Reproduce: 1. Ensure accessibility support is enabled for the user (logging out and then back in if necessary) 2. Start OO.org Writer 3. Start at-poke (locally built, though the package is in Extras) Actual results: OO.org apps aren't visible in at-poke (all of the other apps running are, as far as I can tell) Expected results: OO.org ought to be visible to at-poke
my understanding is that OOo needs the gnome java access bridge to get accessibility off the ground. Now with gcj and so forth I think we should a) get java-access-bridge from gnome working with gcj b) give it a whirl to see this will all work with gcj and friends
I'm informed that the java solution which is the default accessibility story for OOo is fairly horrible, and that there is an alternative native atk solution in the works. This solution sounds like the better long-term solution rather than the java bridge hackery.
screw the java solution, lets try out the experimental native one.
should work in next rawhide release, if compiler doesn't throw another another of its little fits.
Works for me with openoffice.org-writer 1:2.0.0-1.2.2 Awesome - thanks!
It's not working here - openoffice.org-writer-2.0.1-0.142.3.2.i386 on an x86_64.
Try on a 32bit machine, OOo is 32bit, even on 64. If it's a 64bit only problem then it's not a OOo problem, but a more general one.
With most recent OOo 2.0.1-143.1.2 in i386 and with accessibility enabled, i.e. > gconftool-2 -g "/desktop/gnome/interface/accessibility" says "true" and on running "at-poke" then soffice.bin is listed and responds to at-poke. So seems to work fine for i386.
OK, it still doesn't work with those packages. zcerza@tallest ~ =) % oowriter Gtk-Message: Failed to load module "gail": libgail.so: cannot open shared object file: No such file or directory Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory <break> zcerza@tallest ~ =) % sudo yum -y install at-spi.i386 gail.i386 ... No Match for argument: at-spi.i386 ... Installed: gail.i386 0:1.8.8-1 zcerza@tallest ~ =) % oowriter Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory ...And so it is still not accessible. We need at-spi.i386 and probably ligail-gnome.i386 for it to work. Reopening and reassigning to comps.
Reassigning to default owner.
I can reproduce this on my x86_64 system and can confirm that installing at-spi, gail, and libgail-gnome fixes it.
Putting them in comps causes problems, though, due to things requiring libgail-gnome. This pulls in the 64bit libgail-gnome on a 64bit ppc machine (eg, G5) which then pulls in a 64bit panel instead of the 32bit one. We could fix this by splitting the panel libs into a subpackage or by making the requirements on libgail-gnome understand arch. The former is probably the easier
Assigning back to Jesse. I took it accidentally.
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
To properly fix this, the suggestion from comment #13 needs to be done. Reassigning to libgail-gnome.
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp