Bug 155305 - gdm early login gets stuck
gdm early login gets stuck
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
8
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-18 17:54 EDT by Bill Nottingham
Modified: 2014-03-16 22:53 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-26 12:04:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bill Nottingham 2005-04-18 17:54:00 EDT
Description of problem:

It's stuck, for lack of a better word.

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

gdm-2.6.0.8-4

How reproducible:

Happened both times so far

Steps to Reproduce:
1. Enter username
2. Enter password
3. <thunk>
  
Actual results:

Hangs

Expected results:

Logs in

Additional info:

Using kerberos/hesiod for auth & user info.
Comment 1 Bill Nottingham 2005-04-18 18:02:02 EDT
OK, after about 5-10 minutes, it popped up the 'unable to find home directory,
use '/'' dialog.

It looks like it was trying to access it before autofs made it available?
Comment 2 Ray Strode [halfline] 2005-04-19 10:28:17 EDT
is the priority of gdm-allow-login lower than the priority of all your network
services?
Comment 3 Bill Nottingham 2005-04-19 11:03:58 EDT
No, it's higher (99).
Comment 4 Ray Strode [halfline] 2005-04-19 11:36:41 EDT
Currently I believe we inform pam of the username and block until allow-login
before telling pam the password.   It could be that some pam modules block even
when setting the username or something.  If so, then we'll probably have to
change  the interface to be insensitive until the user is allowed to login. 
I'll look into it.
Comment 5 Bug Zapper 2008-11-26 01:50:04 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 6 Bill Nottingham 2008-11-26 12:04:11 EST
This code is dead.

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