After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 641730 - Navigation of user chooser not accessible when GDM first loads
Navigation of user chooser not accessible when GDM first loads
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2011-02-07 15:25 UTC by Michael Whapples
Modified: 2018-05-24 10:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Whapples 2011-02-07 15:25:28 UTC 
When GDM first loads (in archlinux package version 2.32.0-5 which includes the patch solving bug #629310 ) and having the orca screen reader set to start at the log in screen, the accessible events are not sent to notify orca of navigation (using cursor keys) of the user list. If I press tab then the chooser becomes accessible, likewise if I take focus away and move it back. A debugging of this with orca reveals no events being sent.
Comment 1 Hammer Attila 2011-03-29 08:02:09 UTC 
I full confirm Michael wrote bug.
In Ubuntu Natty packaged gdm version is producing same issue with Michael wrote, package version is following: 2.32.0-0ubuntu12.
If I press Tab or Escape key, the user chooser is accessible wonderful, but if I not press this example keys and try moving the user chooser list with arrow keys, Orca does'nt spokening selected usernames because not notify the selection is changed (hopefuly I write right what the problem).

Attila
Comment 2 Rob Whyte 2011-06-08 02:02:43 UTC 
seems the focus for keyboard is not in the userlist, so one needs to tab first.
Comment 3 GNOME Infrastructure Team 2018-05-24 10:33:12 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/55.