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 708105 - gdm does not focus user entry after lifting the screen shield
gdm does not focus user entry after lifting the screen shield
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: login-screen
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Ray Strode [halfline]
gnome-shell-maint
: 701518 712541 731637 733014 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-09-15 08:08 UTC by drago01
Modified: 2014-10-09 16:58 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenShield: focus login screen after lifting shield (2.41 KB, patch)
2014-10-06 20:54 UTC, Ray Strode [halfline] 		committed Details | Review
screenShield: fix trace back when unlocking session from another vt (3.20 KB, patch)
2014-10-08 13:43 UTC, Ray Strode [halfline] 		committed Details | Review

Description drago01 2013-09-15 08:08:58 UTC 
When you leave gdm open and walk away the screenshield comes up after a while (which is imo pointless but a different story). When I lift the shield the user entry is not focused so I have to click on the name to focus it. 

If we want to keep the shield we should atleast make sure that the user entry gets focus after the shield is to make it a bit less annoying.
Comment 1 Gergely POLONKAI 2014-07-14 21:17:27 UTC 
Although this bug report is pretty old now (and it seems to have 4 duplicates, #701518, #731637, #733014 and #712541), there *is* a solution, although not documented.

You may press Ctrl-Alt-Tab to cycle between login screen elements, including the top bar.

This, however, is only a workaround, I hope someone fixes this issue soon.
Comment 2 Jasper St. Pierre (not reading bugmail) 2014-07-14 21:27:57 UTC 
*** Bug 731637 has been marked as a duplicate of this bug. ***
Comment 3 Jasper St. Pierre (not reading bugmail) 2014-07-14 21:28:22 UTC 
*** Bug 701518 has been marked as a duplicate of this bug. ***
Comment 4 Jasper St. Pierre (not reading bugmail) 2014-07-14 21:28:38 UTC 
*** Bug 733014 has been marked as a duplicate of this bug. ***
Comment 5 Jasper St. Pierre (not reading bugmail) 2014-07-14 21:28:56 UTC 
*** Bug 712541 has been marked as a duplicate of this bug. ***
Comment 6 Ray Strode [halfline] 2014-10-06 20:54:17 UTC 
Created attachment 287881 [details] [review]
screenShield: focus login screen after lifting shield

This commit ensures the login screen gets focused after
the screen shield is raised.

The code affects the unlock screen as well, but it's
less important since the unlock screen gets destroyed
and recreated each time the curtain moves, so it
has an opportunity to take focus on its own.
Comment 7 drago01 2014-10-06 21:26:47 UTC 
Review of attachment 287881 [details] [review]:

LG, thanks for fixing that ... meant to do it for a long time but kept forgetting about it.
Comment 8 Ray Strode [halfline] 2014-10-07 14:56:06 UTC 
Attachment 287881 [details] pushed as 1d374ac - screenShield: focus login screen after lifting shield
Comment 9 Ray Strode [halfline] 2014-10-08 13:43:33 UTC 
Created attachment 288042 [details] [review]
screenShield: fix trace back when unlocking session from another vt

commit 1d374ac8bd496f6fa6f4c55ffd207bd30bd50075 introduced a bug that
prevents unlock from working when initiated from another VT
(user switching).

This commit fixes the exception raised.
Comment 10 Ray Strode [halfline] 2014-10-08 13:48:04 UTC 
Comment on attachment 288042 [details] [review]
screenShield: fix trace back when unlocking session from another vt

Attachment 288042 [details] pushed as 4e8c476 - screenShield: fix trace back when unlocking session from another vt