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 710456 - when switching users, the password input screen is shown rather than the user switcher
when switching users, the password input screen is shown rather than the user...
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: login-screen
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: Ray Strode [halfline]
gnome-shell-maint
: 719298 719427 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-10-18 13:47 UTC by Ryan Lerch
Modified: 2013-11-27 21:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
authPrompt: propagate gdm "reset" signal after user switching (2.68 KB, patch)
2013-11-26 03:38 UTC, Ray Strode [halfline]
committed Details | Review

Description Ryan Lerch 2013-10-18 13:47:40 UTC
Steps to reproduce:
1. log into to user1.
2. switch to user2 and log in
3. use gnome-shell to switch to user1.

this results in the password entry screen for user2 being shown, and the spinner in the bottom right near the login button spinning. pressing cancel here returns you back to the user switcher.

Expected Results:
the user switcher is shown.
Comment 1 Ray Strode [halfline] 2013-11-26 03:38:35 UTC
downstream report:

https://bugzilla.redhat.com/show_bug.cgi?id=1034031
Comment 2 Ray Strode [halfline] 2013-11-26 03:38:43 UTC
Created attachment 262808 [details] [review]
authPrompt: propagate gdm "reset" signal after user switching

After a user types in their password at the login screen, one
of two things can happen

1) a new session is started
2) an existing session is switched to

In the latter case, GDM sends a reset signal to the login screen,
so it knows to go back to the user list and wait to be summoned
again.

Unfortunately, all reset signals are ignored after verification
success.  The reason is because the reset handler was copied from
the unlock dialog as part of a deduplication effort in commit
7e7295f259febf34c89659a9bcb05f9924fa1976 and the unlock dialog
handler at the time also emitted a "failed" signal on reset
(which wouldn't make sense to emit after success).

These days "failed" is handled in a different way.

This commit changes the code to let reset signals through after
successful verification.
Comment 3 drago01 2013-11-26 12:02:07 UTC
Review of attachment 262808 [details] [review]:

LG.
Comment 4 Ray Strode [halfline] 2013-11-26 17:50:27 UTC
*** Bug 719298 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2013-11-27 21:18:12 UTC
*** Bug 719427 has been marked as a duplicate of this bug. ***