Bug 196297 - can't login graphically on fedora core 5 ldap client
Summary: can't login graphically on fedora core 5 ldap client
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 5
Hardware: All
OS: Linux
medium
urgent
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-22 14:26 UTC by Norm Green
Modified: 2008-03-18 18:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-18 18:33:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Norm Green 2006-06-22 14:26:47 UTC
Description of problem:
Can not login graphically to fedora core 5 ldap client

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. configure computer to use ldap using system-config-authentication
2. try to login graphically, fails
3. try to login command line, success.
  
Actual results:


Expected results:


Additional info: Log entries from /var/log/secure for attempts to login by valid
ldap users:
Jun 19 11:39:06 adm1lapw2k gdm[2943]: pam_unix(gdm:account): could not identify
user (from getpwnam(jcats701))
Jun 19 11:39:06 adm1lapw2k gdm[2943]: pam_succeed_if(gdm:account): error
retrieving information about user jcats701
Jun 19 11:39:18 adm1lapw2k gdm[2943]: pam_unix(gdm:account): could not identify
user (from getpwnam(ngreen))
Jun 19 11:39:18 adm1lapw2k gdm[2943]: pam_succeed_if(gdm:account): error
retrieving information about user ngreen
Jun 19 11:39:30 adm1lapw2k login: pam_unix(login:session): session opened for
user ngreen by (uid=0)
Jun 19 11:39:30 adm1lapw2k login: LOGIN ON tty1 BY ngreen
Jun 19 11:39:36 adm1lapw2k login: pam_unix(login:session): session closed for
user ngreen

Comment 1 Ray Strode [halfline] 2008-03-18 18:33:29 UTC
Hi,

We no longer support Fedora Core 5 and I am currently trying to get my open bug
count down to a more manageable state.  I'm going to close this bug as WONTFIX.
 If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?

(this is a mass message)


Note You need to log in before you can comment on or make changes to this bug.