password not recognized after suspend

[Aaron Blackwell]

After I suspend and resume my computer, my password is not recognized. However, if I click on change user and log in again it logs in fine. The suspend works fine as well. This only happens since my upgrade from Feisty. Suspend was fine before the upgrade.
System details:
Ubuntu 8.04, upgraded from Feisty.
Dell Inspiron 700m laptop, 1 GB ram, Intel graphics

[Pedro Villavicencio (pedro)]

Thank fory our report ,can you attach your auth.log file?

[Aaron Blackwell (pyramoose)]

After a little more experimentation, it seems the password is not recognized after any lock screen. not just suspend. I repeated the action to see if anything new shows up in auth.log, but nothing does. The only thing in auth.log is the following (repeated), which shows up after I run a sudo command in the terminal (trying to open auth.log in gedit, rather than in the log viewer).

May 11 12:15:07 ubuntu-laptop sudo: aaron : TTY=pts/1 ; PWD=/home/aaron ; USER=root ; COMMAND=/usr/bin/gedit /var/log/auth.log
May 11 12:15:07 ubuntu-laptop sudo: PAM unable to dlopen(/lib/security/pam_smbpass.so)
May 11 12:15:07 ubuntu-laptop sudo: PAM [error: /lib/security/pam_smbpass.so: cannot open shared object file: No such file or directory]
May 11 12:15:07 ubuntu-laptop sudo: PAM adding faulty module: /lib/security/pam_smbpass.so
May 11 12:15:07 ubuntu-laptop sudo: pam_unix(sudo:session): session opened for user root by aaron(uid=0)

So I installed libpam-smbpass, and that gets rid of that error and gives me the following, but doesn't change the locked screen behavior.

May 11 12:22:37 ubuntu-laptop sudo: pam_unix(sudo:session): session closed for user root
May 11 12:26:23 ubuntu-laptop sudo: aaron : TTY=pts/1 ; PWD=/home/aaron ; USER=root ; COMMAND=/usr/bin/gedit /var/log/auth.log
May 11 12:26:23 ubuntu-laptop sudo: pam_unix(sudo:session): session opened for user root by aaron(uid=0)

[Sebastien Bacher (seb128)]

are you sure you are speaking about the gdm screen (the one you to log in when booting for example) and not the gnome-screensaver password entry?

[Aaron Blackwell (pyramoose)]

It's not the initial login screen, it's the screensaver password entry that has the problem. When I click on change user on the screensaver entry screen it takes me back out to the initial login, which works fine.

[Sebastien Bacher (seb128)]

reassigning to gnome-screensaver

[Bradley M. Kuhn (bkuhn-ebb)]

We have confirmed this same behavior regarding gnome-screensaver that is described in this ticket.

When using uswsusp package for hibernate, and the default hardy suspend process, coming back out of either suspend or hibernate *seems* to work perfectly fine except for this issue. Indeed, one can even switch over to a standard TTY, log in and do everything as normal.

However, the X/GNOME session, locked now with the standard gnome-screensaver password prompt box, does not accept the user's password even when typed correctly. We've confirmed the keyboard is typing correctly (i.e., no weird numlock/capslog issue) by choosing the "leave a message for the user" option, where we can see everything typed correctly.

We have noticed this problem only on a Thinkpad X40 (believed to be model 2382-XX1). It is running hardy.

[Martin Pitt (pitti)]

I get the same behaviour on both my hardy boxes. It is really annoying... I'm tracking this down ATM.

[Martin Pitt (pitti)]

I get the same auth.log failures in PAM:

May 30 13:30:48 donald unix_chkpwd[28449]: check pass; user unknown
May 30 13:30:48 donald unix_chkpwd[28449]: password check failed for user (martin)
May 30 13:30:48 donald gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=martin
May 30 13:30:58 donald gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): conversation failed
May 30 13:30:58 donald gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): auth could not identify password for [martin]

[Martin Pitt (pitti)]

Ah, the reason for me was that /etc/shadow was not in group shadow any more, due to a bug in my backup/restore scripts. What is

  ls -l /etc/shadow

for you? If it is owned by root/root, you need to fix it again with

  sudo chgrp shadow /etc/shadow

[Aaron Blackwell (pyramoose)]

Awesome, that did the trick! Problem solved.

[Martin Pitt (pitti)]

Great!

[kevingillan (kev-aktivix)]

Just to note that the quick fix didn't work for me, although the problem sounds identical. Running ubuntu-eee 8.04 on an asus eeepc 901.

~$ ls -l /etc/shadow
-rw-r----- 1 root shadow 911 2009-01-04 12:08 /etc/shadow

(Not sure where to find my auth.log)

cheers

[kevingillan (kev-aktivix)]

To add to that, another quick fix did work for me, the one suggested here:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/163525
i.e.:

sudo chown root:shadow /sbin/unix_chkpwd
sudo chmod 2755 /sbin/unix_chkpwd

The suggestion there was that this might be a bug in libpam-modules, rather than gnome-screensaver (if it is the same bug of course).

[ehcpdeveloper (ehcpdeveloper)]

chgrp shadow /etc/shadow worked for me too.