Bug 195014
Summary: | gdm autologin asks for password | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan-Thomas Czornack <jantho> |
Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | 777tahder, bugzilla, peterb, trondeg, wheeee |
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: | 2008-03-18 18:34:12 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: |
Description
Jan-Thomas Czornack
2006-06-14 13:32:38 UTC
upstream bug, http://bugzilla.gnome.org/show_bug.cgi?id=344191 should be fixed in 2.14.9 My security log show the following during auto-login :
< 2.14.4: pam_unix(gdm-autologin:session)
> 2.14.8: pam_unix(gdm:session)
Looking at /etc/pam.d/gdm and /etc/pam.d/gdm-autologin, it explains why gdm now
asks for password.
This should have been picked up in regression testing... I have non-techie members of my family using Fedora Core desktops, which I updated to FC5 remotely, and this was a bit of a shock to them. (In reply to comment #3) > This should have been picked up in regression testing... I have non-techie > members of my family using Fedora Core desktops, which I updated to FC5 > remotely, and this was a bit of a shock to them. Fedora has no official formal regression testing or QA testing, but if it did, you might be correct. When will 2.14.9 come out? I've requested it be moved from updates-testing to updates this morning, so it should show up sometime today or tomorrow. 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) |