GNOME Bugzilla – Bug 672342
If in GDM the a11y login enabled for screen reader support, Orca spokening the typed password characters
Last modified: 2012-10-04 06:26:22 UTC
Dear Developers, I founded now a high important bug for Orca, with hopefuly possible resolving a next maintenance version: If in GDM the accessible login function enabled with screen reader support, after the user choosed an username and begin typing he's password, Orca not asterisk character spokening when the user typing, spokening normal characters. This is an important problem if an user have for example in an office, or a public place. I will be attaching debug.out file when I modified in gdm directory with Orca launch command desktop file. Attila
Created attachment 210049 [details] This debug file possible show why happening this problem In Ubuntu Precise have following GDM version when I maked the debug.out file: 3.0.4-ubuntu15 Attila
This is not an Orca bug. Apparently gdm-greeter is exposing the password field as ROLE_TEXT and not ROLE_PASSWORD_TEXT. (See debug output below.) If we don't know you are in a password field, we don't know that we should not echo your keypresses. :( I beleive we saw a similar bug a while back in some other gnome-shellish dialog. And I *think* that the fix came from Piñeiro. So before I move this bug to gdm-greeter, I'm CCing Piñeiro as maybe he can just fix it himself. <fingers crossed> vvvvv PROCESS OBJECT EVENT object:text-caret-moved vvvvv OBJECT EVENT: object:text-caret-moved detail=(3,0,0) app.name='gdm-simple-greeter' name='None' role='text' state='editable enabled focusable focused sensitive showing single line visible' relations='labelled by' Script for event: gdm-simple-greeter (module=orca.scripts.apps.gdm-simple-greeter.script) BRAILLE LINE: 'gdm-simple-greeter alkalma2"s $bejelentke21si ablak keret $jel59: ' VISIBLE: 'gdm-simple-greeter alkalma2"s $bejelentke21si ablak keret $jel59: ', cursor=68 TOTAL PROCESSING TIME: 0.0072 ^^^^^ PROCESS OBJECT EVENT object:text-caret-moved ^^^^^ KEYBOARDEVENT: type=1 id=114 hw_code=27 modifiers=0 event_string=(r) keyval_name=(r) is_text=True timestamp=437979 time=1332078412.353540 keyType=printable shouldEcho=True KEYBOARDEVENT: type=0 id=114 hw_code=27 modifiers=0 event_string=(r) keyval_name=(r) is_text=True timestamp=438129 time=1332078412.504243 keyType=printable shouldEcho=True KeyboardEvent.present: r
I just noticed your version of GDM. Here's mine: $ gdm --version GDM 3.2.1.1 You are using a much older version of GDM, so this bug might even be fixed via the fix I mentioned above, but due to Ubuntu's desire to mix and match old GNOME with new GNOME, you just lack that fix.
Here's the patch in question. It is a clutter patch, but it turns out it was done by Matthias Clasen; not Piñeiro. http://bugzilla-attachments.gnome.org/attachment.cgi?id=200676
(In reply to comment #1) > Created an attachment (id=210049) [details] > This debug file possible show why happening this problem > > In Ubuntu Precise have following GDM version when I maked the debug.out file: > 3.0.4-ubuntu15 Taking into account this debug file, the application debugged is gdm-simple-greeter and this program ... (In reply to comment #4) > Here's the patch in question. It is a clutter patch, but it turns out it was > done by Matthias Clasen; not Piñeiro. > http://bugzilla-attachments.gnome.org/attachment.cgi?id=200676 ... AFAIK is a gtk program not a clutter program. GNOME Shell has a GDM session, but as "Classic GNOME" is still there, there is still a GDM without using GNOME Shell. In fact, on this debug file, the only toolkit loaded is GAIL. I didn't find any Cally toolkit. Anyway, just in case, I checked which version of clutter is included on Precise, and it is 1.9.14, that already includes this patch.
I newer Understood Ubuntu developers why mix or replace GNOME components and applications with older versions. For example we already known GDM version is 3.0.4, totem is 3.0.1 in Precise, etc. Possible this choose some time related with Unity Or Unity 2D. Ubuntu awailable Gdm package containing 23 patches in the debian/patches directory. Anyway, thank you very mutch the investigation this problem related. Suggest you I try Gdm version 3.0.2 version to verify this issue and other reported Gdm related issues? Attila
Well, it turns out that the brand new GDM 3.6 login screen has the same problem. So I filed a new bug for it and am marking this one as a duplicate. I anticipate the 3.6 fix will come soon, and then yes you should use it. <smiles> *** This bug has been marked as a duplicate of bug 685469 ***