GNOME Bugzilla – Bug 447435
Can not type anything into unlock keyring dialog when accessibility enabled.
Last modified: 2008-01-11 02:49:37 UTC
Please describe the problem: When accessibility is enabled, can not type password into Gnome-keyring dialog to unlock. Steps to reproduce: On Solaris neveda, Gnome_2.19 1. Launch Gaim/Pidgin, and create a account 2. Make sure check 'remember password' while input password for this account 3. Gnome keyring will start, ask user to set password for this keyring, then the Gaim account will get connected. 4. Enable accessibility 5. Logout and login 6. Start Gaim again, will pop out a dialog 'Unlock Keyring', ask you to input the password for the keyring. Actual results: Can not input anything into this dialog. The only thing you can do is click 'Deny'. But if you turn off accessibility, no problem to input the keyring password. Expected results: Can input password into this dialog. Does this happen every time? Yes Other information: This is only happened when accessibility is enabled.
Li Yuan, would you take a look at this accessibility related bug? Thanks
Odd. I can't duplicate this bug. I checked the 'Accessibility enabled' checkbox in gnome-at-properties
I can reproduce this bug with Pidgin 2.0.1 and gnome-keyring-2.19.2. Note that when the problem occurs, it is not just the gnome-keyring-ask dialog that refuses input - other running applications like gedit and gnome-terminal refused input too, which suggests that this erroneous 'embargo' on user text input is in some sense general. Also, when I cancelled the gnome-keyring-ask dialog and quit pidgin, and then restarted pidgin, the subsequently reappearing gnome-keyring-ask dialog (and other applications on my desktop) started receiving input correctly again.
I suspect the problem is in pidgin, not gnome-keyring.
This issue seems to be in relation to the gnome_keyring_find_network_password_sync() call in the gaim_account_get_password_from_keyring function() in "pidgin-2.0.1/libpurple/account.c"
Can you still duplicate this? Shall I close this bug as a pidgin bug?
Can still be reproduced.
I think this is because when applications (vino, pidgin) popup the gnome-keyring dialog, gnome-keyring blocks the application, thus application can not answer CORBA calls from at-spi-registryd, so the CORBA call never returns. Is there a way to make applications can handle CORBA calls when the gnome-keyring dialog popups?
If the application using gnome-keyring uses the 'sync' version of the gnome keyring calls, then of course it'll block. GUI applications should use the asynchronous version of the gnome-keyring calls.
Yeah, this is an application bug, not gnome-keyring bug. Close as NOTGNOME.
Thanks! Has anyone logged a bug against Pidgin for this? I just want to make sure the thing actually gets fixed. :-)
Pidgin doesn't support gnome-keyring originally, we made a internal patch to make it support gnome-keyring on opensolaris. And also we have made another patch to fix this bug :)