unlock keyring "steals" focus (no cursor in overlying window)

[Christian Stöveken]

When logging in the two windows "Unlock Keyring" and "Authenticate" appear.
"Unlock Keyring" is behind the "Authenticate" (mount /dev/sda2) window, but has the cursor in its input field.

You can't get the cursor into the "Authenticate" input field (or any other) and can't switch to "Unlock Keyring" using "Alt+Tab".
You either have to type your "Unlock Keyring" password blind or bring it to the front by selecting it in the taskbar.
After that you can enter the password in the "Authenticate" window.

1)
Description: Ubuntu karmic (development branch)
Release: 9.10

3)
I expect the cursor to be in the foremost window's input field.
4)
The cursor is in the input field of "Unlock Keyring" although it's in the back.

[arky (arky)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in gnome-keyring.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[Christian Stöveken (excogitation)]

The bug was reproducible at the time - I don't know if it's still present since I don't own that laptop and now don't have the same setup anymore (autologon could have been a contributing factor) - I still don't think that's the way to get rid of bugs.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[Thomas-Thomas (thomas-thomas)]

It occurs here, too, and reproducible. The entry-dialog pops up right after login.
The problem is, that gnome-keyring is stupidly grabbing the entry focus, regardless if it has the window focus. The only solution is to enter a password.
I can see that there is a good intention behind this (avoid that people mistakenly enter the keyring password into another window), but this behaviour is very unexpected in X context, and as such it is extremely annoying, especially if other dialogs appear at the same time or slightly later, as it often happens after login.

This bug is also described here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630616

[Petr Gladkikh (petrglad)]

Yes the problem is reproducible every time (with Unity, XFCE and Cinnamon desktops). In addition to comment #5, the problem apparent to user is also that the dialog can be minimized and while it sits secretly in dash or some taskbar the whole desktop looks not functioning - windows do not react to mouse clicks and keybord shortcuts have no effect.

[Petr Gladkikh (petrglad)]

A kind of workaround is to disable autologin so password is always entered at login time and the dialog does not come up. But on my home computer I would prefer to login without entering password.

[Petr Gladkikh (petrglad)]

This issue lingering for quite a while so I would propose to solve it by replacing keyring unlocking dialog with one that shadows whole screen leaving only dialog at top. Such dialog is already used elsewhere.

This is not ideal solution since reduces ease of autologin (password is asked anyway however skippable) but at least behavior is obvious and straightforward.

[Raphaël Droz (raphael-droz)]

Duplicate of https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549 ?