orca does not read user names

[Alan Bell]

using cursor up and down to switch between users is silent, when running with the screen reader it should read out the user names so that you can find the correct one to log in as.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Thu Mar 1 17:25:57 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120217)
SourcePackage: unity-greeter
UpgradeStatus: No upgrade log present (probably fresh install)

[Joanmarie (joanmarie-diggs-deactivatedaccount)]

I am guessing that we (Orca) is not getting the right events like selection-change or focus to alert us that there is something to present.

[Joanmarie (joanmarie-diggs-deactivatedaccount)]

When I disabled the splash screen (that bug Luke in theory already has fixed), when I arrow up and down amongst the usernames, Orca presents 'Enter password for <selected user's name> password text'. So, I think this is another bug that is just going to go away when Luke's fix for the splash screen is fixed.

[Alan Bell (alanbell)]

video of it not reading user names http://www.youtube.com/watch?v=biJRwpcJBa8

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Attila Hammer (hammera)]

Have some another interesting problems in Unity Greeter, but I think some issues are separate issues.
When Unity greeter present the screen, Orca only spokening window title, but the password entry is not focused I think.
If this time the user begin typing, Orca spokening the typed characters. I don't no this situation happening password writing or not the actual selected username.

When I press TAB and SHIFT+TAB key combination, the password entry is focused, and possible write actual selected username password.
Unfortunately, braille cells is not updated when type is happening (not presenting braille display the asterisk simbol).

If I use Orca flat review, Orca (or Unity Greeter) entire freeze. Happening similar issue if I activate F10 key the awailable indicators, and leave the menue with Escape key. The braille display keeping the last selected menu item text.

Already reported this two last issue with Unity Greeter related? How can possible debugging Orca side this problems when Unity Greeter is running?
Unity Greeter what desktop file or Gsettings key storing Orca execute command?
In Gdm Orca launch command stored in the /usr/share/gdm/autostart/LoginWindow/orca-screen-reader.desktop file I think.
If I modify execute line and insert the --debug-file=any_debug_file command, Orca stores important debug informations.

Attila

[Attila Hammer (hammera)]

Hy,

I installed all upgrades my Precise system, I experiencing following now:
If Unity Greeter launched and Orca loaded, the first selected user
password entry field are focused I think, but Orca doesn't spokening
this. If I press TAB and Shift+TAB keys, Orca spokening "type actual
user password", for example:
"Type Attila Hammer password".
If I press TAB and SHIFT+TAB keys and begin typing my password, Orca
spokening asterisk simbols, not letters.
If I not press Tab and Shift+TAB keys and typing password for my actual
selected user name, the password is typed, but Orca spokening password
characters, not asterisk simbol.

Following positive change are happened:
If Unity Greeter launched and Orca loaded and I press Up or Down arrow
keys, the selected usernames spokening Orca with following form:
"Give Attila Hammer password"
Give Alan Bell password"
If I begin typing this situation my password, Orca spokening asterisk
simbols, not normal characters.
This is the right working method with LightDm user list function?

Attila

[Attila Hammer (hammera)]

Hy,

Because I changed hardcoded Orca command with unity-greeter source
package in src/menubar.vala file, I have possibility to create a
debug.out file, sending with attachment.
Hopefuly this debug.out file help fixing this bug.

Debug.out file clear showing what happening if I not moving other user
in the user list. This situation Orca spokening my password letters, not
asterisk simbols.
Joanie, in Unity Greeter the default selected user in the user list is
not focused, or Orca not known the password entry text field?
Only spokened output is "bejelentkező képernyő keret" before I begin
typing my password.

Attila

[Attila Hammer (hammera)]

Hy,

Joanie, can you try looking your magical test script what happening when
Unity Greeter starts with normal mode if Orca running?
If I run unity-greeter --test-mode command, the user list default
focused, password entry field is right detected and Orca spokening
asterisk simbols when I typing my phantom password. This is not
happening with normal mode.
If you tells me some instructions how can I possible generating test
results with normal login screen if Orca running with your test script,
I welcome doing this.

Attila

[Attila Hammer (hammera)]

Hy,

Joanie, I looked your script what happening with Unity Greeter after
Orca starts.
I doed following:
1. I used your attached script with you sent an other report, I sending
attachment. I moved real orca process with /usr/bin/orca-orig, and
copyed listener.py file with /usr/bin/orca.
Of course I give execute privileges the new script.
2. I logged out, and logged in.

Look the generated output, sorry the hungarian locale messages:
================ Wed Apr 4 08:51:20 2012 ================
window:create(0, 0, Bejelentkező képernyő)
 source: [frame | Bejelentkező képernyő]
 host_application: [application | unity-greeter]
object:state-changed:iconified(0, 0, 0)
 source: [frame | Bejelentkező képernyő]
 host_application: [application | unity-greeter]
window:activate(0, 0, Bejelentkező képernyő)
 source: [frame | Bejelentkező képernyő]
 host_application: [application | unity-greeter]
object:state-changed:focused(1, 0, 0)
 source: [password text | Adja meg Hammer Attila jelszavát]
 host_application: [application | unity-greeter]
object:state-changed:focused(1, 0, 0)
 source: [password text | Adja meg Hammer Attila jelszavát]
 host_application: [application | unity-greeter]
object:state-changed:focused(1, 0, 0)
 source: [password text | Adja meg Hammer Attila jelszavát]
 host_application: [application | unity-greeter]
object:state-changed:focused(1, 0, 0)
 source: [password text | Adja meg Hammer Attila jelszavát]
 host_application: [application | unity-greeter]
object:state-changed:focused(1, 0, 0)
 source: [password text | Adja meg Hammer Attila jelszavát]
 host_application: [application | unity-greeter]
object:state-changed:focused(1, 0, 0)
 source: [password text | Adja meg Hammer Attila jelszavát]
 host_application: [application | unity-greeter]
object:state-changed:focused(1, 0, 0)
 source: [password text | Adja meg Hammer Attila jelszavát]
 host_application: [application | unity-greeter]
object:state-changed:focused(1, 0, 0)
 source: [password text | Adja meg Hammer Attila jelszavát]
 host_application: [application | unity-greeter]
object:state-changed:active(1, 0, 0)
 source: [frame | Bejelentkező képernyő]
 host_application: [application | unity-greeter]
 >>> KEY PRESSED: x
<<< KEY RELEASED: x
 >>> KEY PRESSED: x
<<< KEY RELEASED: x
 >>> KEY PRESSED: x
<<< KEY RELEASED: x
 >>> KEY PRESSED: x
<<< KEY RELEASED: x
 >>> KEY PRESSED: x
<<< KEY RELEASED: x
 >>> KEY PRESSED: Return
<<< KEY RELEASED: Return

Of course, I distorted my password letters with x letters.
Need handling this problem with Unity Greeter, or need reporting a bug
in Bugzilla for Orca related?
If I see right, the default selected user in user list is more time try
changing focused state before changed active state.

Attila

[Joanmarie (joanmarie-diggs-deactivatedaccount)]

My magical test script doesn't shed any light on the matter. But I have been looking over Orca's debug.out output -- further enhanced with even more info. The order of events is this:

1. Orca is started up.

2. Orca goes through its initialization which includes starting up speech, braille, registering event listeners, registering keyboard listeners, looking for the active window, presenting the active window to the user (in this case that would be the frame named 'Login Screen'), and finally it starts up the registry.

3. The first accessible event we get in Orca upon starting the registry is for the first key press. In other words, Orca is not receiving a 'hey, the password text object has just claimed focus!'

The reason that arrowing down and up makes the problem go away is because Orca gets focus-related events at that point. Because unity-greeter has told Orca focus is in a password field, it does not echo keystrokes and share your password with anyone in earshot.

As for why the events are not showing up in Orca but are in my test script, I'm not certain:

* Maybe timing?? My test script does absolutely nothing but start up and print stuff out. Orca's doing a lot more than that.

* Perhaps instead it is a side effect of how Orca is getting started up??

Getting to the bottom of that, however, is key.