[Bug 216951] New: the gnome-screensaver will not unlock
https://bugzilla.novell.com/show_bug.cgi?id=216951 Summary: the gnome-screensaver will not unlock Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: wshackle@yahoo.com QAContact: qa@suse.de I have a system where users can log in but if the screen locks it can never be unlocked. I am not sure what has happened to the system but it is clearly testing for something very strange instead of the password and failing, without giving the user or even adding something to /var/log/messages to give any clue as to what the problem is. Each attempt to unlock a screen always produces two entries in /var/log/messages one for the user and one for root. But it always fails whether you give the user passwd or the root password. Oct 31 16:05:54 archimedes-304 unix2_chkpwd[12716]: pam_authenticate(gnome-screensaver, shackle): Authentication failure Oct 31 16:05:59 archimedes-304 unix2_chkpwd[12717]: pam_authenticate(gnome-screensaver, root): Authentication failure The same password works reliably when logging in every other way, (console, GDM, ssh etc) /etc/pam.d/gnome-screensaver is unmodified. In fact rpm -V pam pam_modules gnome-screensaver shows no modified files for any of these packages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=216951 jpr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Comment #1 from jpr@novell.com 2006-11-01 11:47 MST ------- *** This bug has been marked as a duplicate of bug 216816 *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com