Hide Forgot
Description of problem: When a user has a password that is about to expire (s)he receives a warning from AD about this. When this message appears gdm fails to let the user log in. Version-Release number of selected component (if applicable): gdm-3.2.1.1-8.fc16.i686 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: It could be that the problem is really in another package. When logging in in a console window I get Your password will expire in 6 days. erroneous conversation (5) That last message could be the reason gdm decides the user shouldn't be allowed in? On a text console I can log in and change the password. After a password change the problem is gone. AD logon was set up using the following command authconfig --enablewinbind --enablewinbindauth --winbindtemplateshell=/bin/bash --enablewinbindusedefaultdomain --enablewinbindoffline --winbindjoin=myadminuser --smbsecurity=ads --smbrealm=mydomain.org --enablesssd --enablecache --enablemkhomedir --smbworkgroup=MYDOMAIN --update
This bug is still here, and it is a bit worse than I first thought. I can successfully log in on the text console and change my password as long as I am inside the network where the AD server resides. When I am 'on the road' I am using cached user data, and I can't change those it seems?
I can confirm that this bug is still here. Just install F17 today and ran into the bug.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" 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
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.