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 692654 - Gnome shell doesn't wait for password prompt with gnome-keyring
Gnome shell doesn't wait for password prompt with gnome-keyring
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
3.6.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-01-27 20:11 UTC by James
Modified: 2021-07-05 14:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description James 2013-01-27 20:11:30 UTC
1. Open seahorse (passwords and keyring)
2. Create new keyring
3. Set password to "" (empty)
4. Click change password, here you will be prompted to enter the old "" (empty) password.

Now, if you click "continue", then this works fine and you are displayed with the enter a password twice dialog. If you press <enter>, this screen gets skipped (it immediately gets sent an enter keypress when you only pressed it once) ! No, I did not press enter too hard. Try it out.

Hope this helps pinpoint some sort of input handling bug in the shell. Filing against shell, because I don't think this happened when the dialogs were handled the traditional way in gnome 2.x

Cheers,
James
Comment 1 Giovanni Campagna 2013-01-28 22:29:04 UTC
Indeed, this is reproducible with 3.7.4 too, and even if I set a password for the keyring the first time.
But the keyring dialog is a simple modal dialog, and the same code works find in other situations (network, polkit).

Stef, could this be an issue with the Gcr DBus API?
Comment 2 Jasper St. Pierre (not reading bugmail) 2013-01-28 22:32:35 UTC
The keyring dialog, the network dialog and the polkit dialog are all subtly different in various ways, and it certainly could be a bug in the keyring modal dialog code only. It probably makes sense to merge them at some point.
Comment 3 Atri 2013-02-23 19:24:35 UTC
I am sorry if what I am reporting is a different bug, in which case I will happily open a fresh one, but in addition to being to reproduce the behaviour with seahorse as noted in the description here, I see the exact same behaviour with the polkit authorisation dialog too. It is even more of an issue with the polkit authorisation dialog as (when the application requiring polkit auth, gparted in my case, is started by hitting "enter" from the keyboard) it simply prevents me from entering any password before the dialog complains "Sorry, that didn't work. Please try again." and disappears. If the application is started using a mouse click from the shell applications overview, then the polkit dialog is fine and I can enter the password and proceed. Even simply doing "pkexec ls" from the terminal and hitting enter causes the polkit dialog to appear, quickly say "Sorry that didn't work. Please try again," and then disappear.

I am using gnome-shell 3.6.3 on openSUSE 12.3 RC1.
Comment 4 Atri 2013-02-23 19:30:06 UTC
Could this be the same bug? At least mine seems to be
https://bugzilla.gnome.org/show_bug.cgi?id=692937
Comment 5 GNOME Infrastructure Team 2021-07-05 14:17:34 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.