Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 133430 - at-spi: accessibility is broken
at-spi: accessibility is broken
Product: Fedora
Classification: Fedora
Component: at-spi (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Blandford
Depends On:
Blocks: 131589
  Show dependency treegraph
Reported: 2004-09-23 18:13 EDT by Zack Cerza
Modified: 2013-04-02 00:20 EDT (History)
2 users (show)

See Also:
Fixed In Version: 1.6.0-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-24 06:20:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Zack Cerza 2004-09-23 18:13:40 EDT
Description of problem:
After enabling accessibility, I see this error on startup of any GNOME

"Accessibility: failed to find module 'libatk-bridge' which is needed
to make this application accessible"

Version-Release number of selected component (if applicable):

How reproducible:
x86_64: Always
i386: Never

Steps to Reproduce:
1. $ gconftool-2 -t boolean -s /desktop/gnome/interface/accessibility true
2. $ gedit
Actual results:
Bonobo accessibility support initialized
GTK Accessibility Module initialized

(gedit:12637): Gnome-WARNING **: Accessibility: failed to find module
'libatk-bridge' which is needed to make this application accessible

Expected results:

Additional info:
$ file /usr/lib64/gtk-2.0/modules/libatk-bridge.*
/usr/lib64/gtk-2.0/modules/libatk-bridge.a:  current ar archive
/usr/lib64/gtk-2.0/modules/libatk-bridge.la: ASCII English text, with
very long lines
$ ar t /usr/lib64/gtk-2.0/modules/libatk-bridge.a

It looks like a libtool issue. Maybe a rebuild with a newer libtool
will suffice; maybe at-spi's libtool-fu itself needs an upgrade.
Comment 1 Mark McLoughlin 2004-09-24 06:20:16 EDT
Okay, I removed some redundant stuff from the spec file and we now
(magically!) the .so seems to pop out the other end correctly.

Fingers crossed :-)

Note You need to log in before you can comment on or make changes to this bug.