[Karmic] gnome-screensaver does not recognize correct password

[Claudio Moretti]

Binary package hint: gnome-screensaver

When I try to unlock the screen, my password is not recognized.
I am sure I'm typing it right, because it's since half an hour that I'm trying.
I've also tried to reboot and "dpkg-reconfigure gnome-screensaver", with no success.
I am able to login in ttys and at the login screen; to unlock my system I have to press "change user" and log back in in gdm login screen.

[Chris Coulson (chrisccoulson)]

Thank you for your bug report. Please kill your existing gnome-screensaver, and then run:

gnome-screensaver --no-daemon --debug 2>&1 | tee gnome-screensaver.log

Try locking and unlocking your screen and then attach the resulting file to this bug report. Thanks!

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

[Juergen Schroeder (js-mr)]

I have the same problem in karmic. Also in xscreensaver where I come from.
I run fvwm not gnome.
Behind the password field I see a "GBr" which I can change to "??"
I think this is the keyboard level. Yes I try both.
If I switch to "??" and kill the screensaver the xterm left the way the AltGr key is pressed continous.
I have this .xmodmap on a GB keyboard

keycode 0x4B = adiaeresis Adiaeresis
keycode 0x4C = odiaeresis Odiaeresis
keycode 0x5F = udiaeresis Udiaeresis
keycode 0x60 = ssharp XF86_Switch_VT_12
keycode 0x1E = u U NoSymbol NoSymbol udiaeresis Udiaeresis
keycode 0x20 = o O NoSymbol NoSymbol odiaeresis Odiaeresis
keycode 0x26 = a A ae AE adiaeresis Adiaeresis
keycode 0x27 = s S ssharp section ssharp section
clear Shift
clear Lock
clear Control
clear Mod1
clear Mod2
clear Mod3
clear Mod4
clear Mod5
add Shift = Shift_L Shift_R
add Lock = Caps_Lock
add Control = Control_L Control_R
add Mod1 = Alt_L 0x00CD 0 bracketright 9
add Mod2 = Num_Lock
add Mod4 = 0x00CE 0x00CF
add Mod5 = ISO_Level3_Shift Mode_switch Mode_switch ISO_Level3_Shift

This command produce an empty logfile:
 gnome-screensaver --no-daemon --debug 2>&1 | tee gnome-screensaver.log

Here is a log wich I cut&paste:
[update_geometry] gs-window-x11.c:437 (09:27:36): using geometry for monitor 0: x=1280 y=0 w=1600 h=1200
[gs_window_move_resize_window] gs-window-x11.c:470 (09:27:36): Move and/or resize window on monitor 0: x=1280 y=0 w=1600 h=1200
[gs_window_raise] gs-window-x11.c:743 (09:27:36): Raising screensaver window
[gs_window_xevent] gs-window-x11.c:814 (09:27:36): not raising our windows
[update_geometry] gs-window-x11.c:424 (09:27:36): got geometry for monitor 0: x=1280 y=0 w=1600 h=1200
[update_geometry] gs-window-x11.c:437 (09:27:36): using geometry for monitor 0: x=1280 y=0 w=1600 h=1200
[gs_window_move_resize_window] gs-window-x11.c:470 (09:27:36): Move and/or resize window on monitor 0: x=1280 y=0 w=1600 h=1200
[gs_window_raise] gs-window-x11.c:743 (09:27:36): Raising screensaver window
[gs_window_xevent] gs-window-x11.c:814 (09:27:36): not raising our windows
[error_watch] gs-window-x11.c:974 (09:27:43): command error output: [request_response] gnome-screensaver-dialog.c:153 (09:27:43): got response: -2

[error_watch] gs-window-x11.c:974 (09:27:45): command error output: [do_auth_check] gnome-screensaver-dialog.c:299 (09:27:45): Verify user returned: FALSE

[lock_command_watch] gs-window-x11.c:1463 (09:27:45): command output: NOTICE=AUTH FAILED

[error_watch] gs-window-x11.c:974 (09:27:45): command error output: [do_auth_check] gnome-screensaver-dialog.c:302 (09:27:45): Verify user returned error: Falsches Passwort.

[error_watch] gs-window-x11.c:974 (09:27:45): command error output: [auth_check_idle] gnome-screensaver-dialog.c:361 (09:27:45): Authentication failed, retrying (3)

[update_geometry] gs-window-x11.c:424 (09:27:45): got geometry for monitor 0: x=1280 y=0 w=1600 h=1200
[update_geometry] gs-window-x11.c:437 (09:27:45): using geometry for monitor 0: x=1280 y=0 w=1600 h=1200
[gs_wi...

[Juergen Schroeder (js-mr)]

Shit I got it.

rootc@pcub255:/root> ll /etc/shadow
-rw-r----- 1 root shadow 1,5K 2010-01-12 11:32 /etc/shadow
rootc@pcub255:/root> chmod a+r /etc/shadow

I found it in a suse forum. It is really ugly to open the permissions. Before karmic it works.

Jürgen

[Claudio Moretti (flyingstar16)]

I solved it by reinstalling my system;
But sounds VERY stupid to me to chmod a+r /etc/shadow, as every lamer with John The Ripper can decrypt your password.

And as you have this problem, we can reopen this bug and you can help more than I did :)

[Chris Coulson (chrisccoulson)]

If you're having to adjust permissions on /etc/shadow to make it work, then it's more likely that you've broken your install rather than this being a bug (probably by removing the sgid bit on /sbin/unix_chkpwd)

[Chris Coulson (chrisccoulson)]

What is the output of "ls -l /sbin/unix_chkpwd"?

[Juergen Schroeder (js-mr)]

I got the hint here:
https://bugzilla.novell.com/show_bug.cgi?id=204364#c22

Hello Caudio, maybe friday I had 2 hours to try to reinstall some gnome packages at my pc at work.

Now I'm at home with the same revision. Here genome-screensaver unlocks fine (but here I have a german keybord, here is Deu behind the passwd-field, this explains "GBr" mentioned before )

Hello Chris:
Both PCs have the same permissions
schroedj@pcub255:/home/schroedj> ls -l /sbin/unix_chkpwd
-rwxr-sr-x 1 root shadow 30400 2009-09-04 10:26 /sbin/unix_chkpwd*

But next of my features at the don't working pc at work: my UID is used over 16 years so it is only around 500 (won't change because there are a lot of nfs servers).
I know that the gnome-login-greeter also has now no option to show UIDs lower than 1000, maybe the "login-helper app" hangs there.
Will try it friday with a UID>1000.

[Chris Coulson (chrisccoulson)]

Does anything get logged in /var/log/syslog when you try to unlock the screen?

[Juergen Schroeder (js-mr)]

On Di, Jan 19, 2010 at 02:26:50 -0000 Chris Coulson wrote:
> Does anything get logged in /var/log/syslog when you try to unlock the
> screen?

Yes, i have anonimized it a bit

Jan 19 09:12:11 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 19 09:12:21 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 19 09:12:21 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=502 euid=502 tty=:0.0 ruser= rhost= user=MyUserName
Jan 19 09:12:23 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 19 09:12:35 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 19 09:12:35 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=502 euid=502 tty=:0.0 ruser= rhost= user=MyUserName
Jan 19 09:12:37 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 19 09:12:43 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 19 09:12:43 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=502 euid=502 tty=:0.0 ruser= rhost= user=MyUserName
Jan 19 09:12:45 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 19 09:13:00 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): conversation failed
Jan 19 09:13:00 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): auth could not identify password for [MyUserName]

Juergen

[Juergen Schroeder (js-mr)]

I tried it with a UID 1001:

root:> chmod o-r /etc/shadow

MyUserName:> su - jstest
works:

Jan 22 08:38:48 xpcubXYZ su[10286]: Successful su for jstest by MyUserName
Jan 22 08:38:48 xpcubXYZ su[10286]: + /dev/pts/0 MyUserName:jstest
Jan 22 08:38:48 xpcubXYZ su[10286]: pam_unix(su:session): session opened for user jstest by MyUserName(uid=502)
Jan 22 08:38:55 xpcubXYZ su[10286]: pam_unix(su:session): session closed for user jstest

But jstest can't unlock the screensaver:
Jan 22 08:40:19 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 22 08:40:22 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 22 08:40:22 xpcubXYZ gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure;
        logname= uid=1001 euid=1001 tty=:1.0 ruser= rhost= user=jstest

Sometimes I will reinstall the gnome parts. Which one neccessary?

 Juergen