GNOME Bugzilla – Bug 403631
[blocked] Only the first two items in combo boxes are spoken in Ubuntu Feisty Fawn
Last modified: 2007-02-07 20:47:49 UTC
Steps to reproduce: 1. Get into the Orca Preferences dialog and move to the Speech page 2. Tab to any of the combo boxes that contain at least three items and press Space to expand the list. 3. Use Up and Down Arrow to navigate among the items. Expected results: Orca would speak/braille each item that received focus. Actual results: Orca only speaks/brailles the first two items in the list. Other info: This is not limited to the Orca Preferences dialog box. The above can also be reproduced in Gaim's (2.0 beta 6), Preferences dialog. See the Status to Apply at Startup combo box on the status/idle page.
For more info: I tested this with the Orca Preferences dialog on Ubuntu Edgy and cannot reproduce the problem. It may be a GNOME 2.17.x regression. :-(
Created attachment 81772 [details] full debug.out illustrating the issue It seems that the problem is that only the first two items have names. Compare the focus events at lines 7092 and 7171 (no speech) with those at 7582 and 7678 (spoken).
Re comment #1: Yup. I forgot to mention that. It's fine in Edgy.
I am able to reproduce this one on feisty as well. All is fine on edgy.
*** Bug 404339 has been marked as a duplicate of this bug. ***
I've open bug #404664 against atk/atk for the underlying problem and marked it critical/urgent. I've included a standalone python script that reproduces the problem (i.e. the name field is '' for all combo box items except the first two).
The problem is caused by the patch in bug #398330 http://bugzilla.gnome.org/show_bug.cgi?id=398330 If I comment those two lines out: + if (index < 0 || index > g_list_length (list)) + return NULL; then Orca nicely speaks all of the entries in the combo box.
Just added the following comment to bug #404664: "The version of gail in SVN trunk/HEAD does indeed fix this problem, but I don't think it's a duplicate of bug #403138. If I just apply that new patch attached to that bug to version 1.10.1, then the problem still exists. Anyway, the problem appears fixed. We eagerly await your new tarball. Thanks." Mike, Joanie could you also please try out the SVN trunk/HEAD version of gail and see if the problem has completely gone away? Thanks.
Installing the latest gail does seem to solve the problem.
Mike also mentioned on the phone that this fixes the problem for him (using the latest gail from svn trunk/HEAD). Closing as FIXED.