Bug 499312
Summary: | cannot login on gdm console nor /dev/console after suspend with winbind | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jason Haar <jhaar> |
Component: | samba | Assignee: | Guenther Deschner <gdeschner> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | azelinka, dpal, gdeschner, ssorce |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-16 18:13:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 516998 |
Description
Jason Haar
2009-05-06 04:39:38 UTC
My guess is that a initgroups() call from the operating system iterates over the winbind backend and needs to wait until winbind is able to respond. I need to investigate further though. This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping FYI I have reinstalled FC12 and still have exactly the same problem. I have opened a ticket with the Samba group, as winbind is the root problem, but pam/whatever could respond better that hanging forever https://bugzilla.samba.org/show_bug.cgi?id=6103 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. FYI, still a problem with F13 - and it triggers a regressive (?) problem in nscd too. If winbind isn't able to talk directly to its domain controllers, then any auth attempt (eg getty, gdm, screensaver, ssh) should come out of cache. F13 uses nscd - so the "cached password" should be kept by it - but I guess (as it doesn't work) it defers to winbind? Anyway, nscd talks to winbind and for whatever reason winbind doesn't return a cached OK and instead tries to talk to the unavailable domain controllers and the whole thing times out - and is then reported up the chain as a bad password. I see very fast "bad password" failures - not long drawn out ones, so I guess that initial timeout is "corrupted" into a bad password failure... This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 |