System/shutdown dialog are inaccessible with Orca screen reader.

[Attila Hammer]

Dear Ubuntu Developers!

When I trying shutdown the sistem with system/shutdown menu item, the dialog are inaccessible with Orca screen reader. This problem present with logout dialog and shutdown dialog.
In Hardy, this dialogs are work fine.
Same users says this bug with bugzilla:
http://bugzilla.gnome.org/show_bug.cgi?id=535827

Attila

[Attila Hammer (hammera)]

Wilie Walker writing this answer my question with this problem:
Hi Attila:

I believe that patch is not what the GTK+ folks intended to be the
solution. Instead, the third (the last) patch is the one to use, and is
 the one that
has been committed.

If it's not working, either a11y integration is broken in Ubuntu or some
 more work needs to be done. I suspect a11y integration may be broken
on Ubuntu
and they need to know about it:
http://bugzilla.gnome.org/show_bug.cgi?id=535827#c30
http://bugzilla.gnome.org/show_bug.cgi?id=535827#c31

Can you contact Ubuntu, please, and try to work through this issue with
 them?

Thanks!

Will

Possible solve this problem?
I copyed two comment with bug 535227
(http://bugzilla.gnome.org/show_bug.cgi?id=535827#c30
and http://bugzilla.gnome.org/show_bug.cgi?id=535827#c31)

did at-spi have a schema before?

If it didn't, the ubuntu packager may forgotton to add

gconftool-2 --makefile-install-rule ...

as a post installation step in the package.

Can you confirm that the schema is installed by doing:

gconftool-2 --get-schema-name
/apps/gnome_settings_daemon/gtk-modules/gail:atk-bridge

If it's not installed it will yell.

Could be there's a bug in GConf like Jens mentions as a possibility, too,
though. Not sure.

Comment
#31
 from
Ray Strode
(developer,
points: 16 )
2008-09-29 15:52 UTC [reply ]
I'm guessing this is a packaging bug, because when I'm on a rawhide
machine and
I do:

gconftool-2 --recursive-unset /apps/gnome_settings_daemono/gtk-modules

(to undo the gconftool call from my test above)

and then do

gconftool-2 -R /apps/gnome_settings_daemon/gtk-modules

(which presumably does something similar to the g-s-d code)

then I get:

gnomebreakpad = true
gail:atk-bridge = /desktop/gnome/interface/accessibility

which comes from the schemas and seems right.

Attila

[Luke Yelavich (themuso)]

The schema file is present, and carrying out the suggested steps in the comments you copied all work as expected, however the logout dialogs are still broken, so I guess the problem is somewhere else in the stack.

[Attila Hammer (hammera)]

I installed few hours ago the Jaunty Alpha-6 32 bit release with my
Toshiba notebook, all updates are installed. The system/shutdown or
logout dialogs is full
accessible with Orca.

But the 64 bit release my desktop machine (all updates are installed)
the shutdown/logout dialogs are inaccessible.
I using my desktop machine with Ubuntu Jaunty Alpha-6, 64 bit release.

Interesting, but all alpha-6 Live cd's this dialogs correct speak with
Orca screen reader.
My friend using the 64 bit release he's Lenovo notebook. The
shutdown/logout dialog speaks correct he machine, but if he working
longer time the system, this dialogs are inaccessible with Orca.

Luke, have any ydea how can fix this problem?

Attila

[Luke Yelavich (themuso)]

its a gnome-session bug, reported upstream already. Will attach a bug watch for it.

[Attila Hammer (hammera)]

Luke, I think this problem present only if I using the oldest sudoers
file (your Hardy suggestion)?
Now I see the live cd the second default row is changed by following line:
Defaults env_keep = "ORBIT_SOCKETDIR XDG_SESSION_COOKIE GTK_MODULES"

I replace the /etc/sudoers file second default line with this line and
deleted the /root/.orbitrc file, and the shutdown dialog are works
perfect with 64 bit release.
I think this is the problem because not confirming another user with
accessibility list this problem with Jaunty.
For testing, I doing a clean installation with original cd, because very
lot of think changed (the launched sudo applications is talking good).
Please leave now open this bug if this is needed.

Attila