|
Bugzilla – Full Text Bug Listing |
| Summary: | gnome-screensaver doesn't recognize my password | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Émeric Maschino <emeric.maschino> |
| Component: | GNOME | Assignee: | Rodrigo Moya <rodrigo> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | aj, andreas.hanke, aristeu, david.wright, dimstar, forgotten_PZ4wA53Xsq, jhn_gleeson, kukuk, linux, mmeeks, security-team |
| Version: | RC 5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | The log produced by gnome-screensaver while trying to unlock. | ||
|
Description
Émeric Maschino
2006-09-08 07:40:56 UTC
*** Bug 204373 has been marked as a duplicate of this bug. *** *** Bug 204367 has been marked as a duplicate of this bug. *** I guess this is happening in 10.2 (that is, gnome 2.15/2.16), right? Maybe we are not patching correctly the PAM config file.. The situation is even worse with today's Alpha 4 Plus updates: my password isn't recognized at the GDM login screen. To access my GNOME desktop, I had to switch in runlevel 3 and start an X session with startx. If it can help: - gnome-screensaver-2.15.7-4 - gnome-session-2.15.92-4 - gdm-2.15.10-5. Comment 4 (not the initial report) is a duplicate of bug 205621. 10.2 Alpha 4 recognizes my password for GDM, but screen saver does not. Had to ssh in and kill the gnome-screensaver process. (In reply to comment #4) > The situation is even worse with today's Alpha 4 Plus updates: my password > isn't recognized at the GDM login screen. To access my GNOME desktop, I had to > switch in runlevel 3 and start an X session with startx. See #206963 for a quick hack to login. But this doesn't solve the screensaver problem. increasing Severity for the screensaver problem This still happens with Alpha4plus as of today. *** Bug 208684 has been marked as a duplicate of this bug. *** *** Bug 209931 has been marked as a duplicate of this bug. *** *** Bug 210177 has been marked as a duplicate of this bug. *** This still happens with STABLE from today. I have this behaviour just experienced with an installation of ALPHA5 today. *** Bug 211866 has been marked as a duplicate of this bug. *** No success for me in trying to replicate this bug, because the screensaver just fades and locks the screen for ever, without showing ever the unlock dialog. So, while I install alpha5 to see if I'm luckier, could anyone having this bug do the following: $ killall -9 gnome-screensaver $ gnome-screensaver --no-daemon --debug > log.txt 2>&1 and send me the log.txt file after you tried to unlock the dialog and it failed? Created attachment 101399 [details]
The log produced by gnome-screensaver while trying to unlock.
#17: Please find the attached log; hopefully it helps. > [error_watch] gs-window-x11.c:736 (10:24:28): command error output:[ auth_message_handler] gnome-screensaver-dialog.c:247 (10:24:28): Got no response > > [error_watch] gs-window-x11.c:736 (10:24:28): command error output: [auth_message_handler] gnome-screensaver-dialog.c:215 (10:24:28): Got message style 3: 'Permissions on the password database may be too restrictive.' > > [error_watch] gs-window-x11.c:736 (10:24:28): command error output: [auth_message_handler] gnome-screensaver-dialog.c:247 (10:24:28): Got no response > > [error_watch] gs-window-x11.c:736 (10:24:28): command error output: [do_auth_check] gnome-screensaver-dialog.c:283 (10:24:28): Verify user returned: FALSE > > [error_watch] gs-window-x11.c:736 (10:24:28): command error output: [do_auth_check] gnome-screensaver-dialog.c:286 (10:24:28): Verify user returned error: Incorrect password. seems the PAM conversation is getting nowhere, with errors being returned. I've seen people getting this 'Permissions on the password database may be too restrictive.' message because of the 'Paranoid' mode being selected in Yast (Security and Users -> Local Security'). Is that the case? I checked, and 10.2 comes with the 'Easy' mode by default, so I guess it won't be the case. Local security settings are on defaults, the File security is 'easy'. Ok, so the cause of the problem is the /etc/shadow file not being readable by gnome-screensaver. If you set it to readable by everyone, it unlocks correctly :-( I see this file had the same permissions, that is: -rw-r----- 1 root shadow 885 2006-08-29 13:56 /etc/shadow in SLED10, where it works, so, what has changed? you need to pass --enable-authentication-scheme=helper to configure yay, that was it, this was added to g-screensaver, and if not used, it was not using the helper program, like in SLED10. Thanks Ludwig, package submitted to autobuild *** Bug 212264 has been marked as a duplicate of this bug. *** This just happened again, on a new RC5 installation. Never using gnome, thus I didn't notice that before. For information: I just installed 10.2 Final and can confirm that this bug is NOT existing just after the installation from DVD. Cannot reproduce ATM. Guess this was a configuration glitch. Sorry for the fuzz. Changing to component GNOME. Sorry for the spam. |