Ah, figured it out. Turns out a 3rd party package (not in the Ubuntu
repos) had added a line for its own PAM module into the configuration,
but with incorrect arguments. Now that's cleared up and things are
working normally.
And now I have a clue about how PAM works, yay!
** Changed in: pam (Ubun
Hi Brian,
There is only one module listed here in your common-auth file that will
prompt for a password. Do you have other password-prompting modules
configured directly in /etc/pam.d/gdm?
--
GDM asks for password twice during login
https://bugs.launchpad.net/bugs/262910
You received this bug n
Sorry for the late reply,
Firstly, I'm not sure I'm seeing the same thing as Peter. I haven't had
any other application ask for the password twice (e.g. any of the
'unlock' buttons in GNOME, or gksu[do]).
Secondly, here are the non-comment lines from my /etc/pam.d/common-auth:
auth[success=1
Peter, Brian, please post the contents of your /etc/pam.d/common-auth
files when this error happens.
--
GDM asks for password twice during login
https://bugs.launchpad.net/bugs/262910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
reassigning to pam that doesn't look like a gdm issue, Steve do you have
any idea about that one?
** Changed in: pam (Ubuntu)
Sourcepackagename: gdm => pam
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
--
GDM asks for password twice during login
https://bugs.launchpad.net/bug
I got same isuue.
Real problem is not the GDM, but changes in pam.d as any application, which
required authentication, requested entering password twice.
Sollution is to add in /etc/pam.d/common-auth clausule 'try_first_pass':
authrequisite pam_unix.so nullok_secure try_first_pass
I'm
no real idea for debugging no, do you have anything in the auth.log,
message and syslog log?
--
GDM asks for password twice during login
https://bugs.launchpad.net/bugs/262910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
I have been running Intrepid since Alpha 1 and keep the system up to
date. This first started occurring several weeks ago, I neglected to
report it then, assuming it was a wider-spread issue and would be
quickly resolved. Unfortunately that means that I have no leads on what
specific update caused
thank you for your bug report, you seem to be the only one to have the
issue, did you start getting it after an upgrade or a configuration
change, do you anything specific to your configuration?
** Changed in: gdm (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Deskt
