Bug 684653

Summary: Screen unlocking fails after having locked screen in gnome-shell
Product: [Fedora] Fedora Reporter: Joachim Backes <joachim.backes>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-17 13:37:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joachim Backes 2011-03-14 06:46:35 UTC 
Description of problem:
I lock my screen with the rightmost top button menu "Lock screen". Now trying to unlock fails because my password is not accepted. But if I try to switch user to my own UID and then entering the password, it is accepted, and the (old) session is reopened.

Version-Release number of selected component (if applicable):
gnome-shell-2.91.91-1.fc15.x86_64

How reproducible:
always

Steps to Reproduce:
1.Login into gnome-shell
2.Lock screen as described
3.Try to unlock the screen
  
Actual results:
password is not accepted, screen remains locked

Expected results:
screen is unlocked

Additional info:
Comment 1 Joachim Backes 2011-03-16 07:46:46 UTC 
Contents of /var/log/secure in this situation:

Mar 16 08:43:37 eule unix_chkpwd[3983]: check pass; user unknown
Mar 16 08:43:42 eule unix_chkpwd[3984]: check pass; user unknown
Mar 16 08:43:42 eule unix_chkpwd[3984]: password check failed for user (backes)
Mar 16 08:43:42 eule gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=500 euid=500 tty=:0.0 ruser= rhost=  user=backes
Comment 2 Joachim Backes 2011-03-17 13:37:00 UTC 
Problem solved: /bin/su had no s-bit. After adding the s-bit to /bin/su, unlocking runs perfectly.

I can't say why that bit was missing :-(