GNOME Bugzilla – Bug 725707
All password prompts fail to submit the password
Last modified: 2018-05-24 11:00:35 UTC
Created attachment 270960 [details] Stuck password prompt Hi. I'm running an up-to-date Debian SID. Recently, all gnome-related password prompts have failed me, including gdm3's password field, evolutions's and seahorse's. In practice: at log-in time, I am asked to select my user account (I select it) and to enter my password. I enter the password, then click "log in". That log-in button turns greyer, and nothing else happens. I can still click in the top menu bar to see how much battery is left, or I can click "cancel", in which case I'm back at the user selection part of the login page. Now, if I log in manually (kill gdm, startx) and lauch evolution, it will say I didn't unlock the keyring, and prompts for my password. Again, clicking "unlock" leaves me with the only choice to click cancel. The same problem happens if I ask seahorse to unlock my keyring. I have not been able to investigate what the reason for the bug could be. ltrace/strace haven't been very useful... Besides that, I can use xdm, sudo, and other unrelated password-prompting tools without problem.
It would make sense to file such a bug with the Debian bug tracker. Buth can you try commenting out the pam_gnome_keyring.so lines in /etc/pam.d/* files, and see if that fixes gdm? Obviously modifying your PAM stack is risky...
I tried commenting the lines and restarting the host, but the problem persisted. I'll cut a ticket on debian's bug tracker as well, but I thought someone here may know what could cause such a bug. (I.e., assuming the prompts are calling a service/daemon, maybe this service is down and the caller waits for a reply?)
Maybe Ray knows something. Reassigning to gdm since that's how GNOME and the session should be started. I have no experience with using plain startx + gnome-keyring-daemon. I'm willing to accept patches for this combination, but I'm not interested in troubleshooting it.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/186.