Hide Forgot
+++ This bug was initially created as a clone of Bug #709918 +++ Still reproducible in F19. The workaround, mentioned below, still works. +++ This bug was initially created as a clone of Bug #646056 +++ IT is also reproducible on F14. Description of problem: If your Active Directory password is about to expire, winbind passes that information into PAM - and gdm login attempts misread it as some form of failure - and you get bounced back to the login prompt Steps to Reproduce: 1. have account about to expire, so that AD starts nagging you to change your password 2. try logging in via gdm 3. see "your password is about to expire..." message in gdm window for a few seconds before it rejects your valid login attempt Actual results: can't log in. Expected results: valid password, should be logged in --- Additional comment from Fedora Admin XMLRPC Client on 2011-06-21 11:32:40 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Fedora Admin XMLRPC Client on 2011-06-21 11:34:40 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Fedora Admin XMLRPC Client on 2011-06-21 11:37:27 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Fedora Admin XMLRPC Client on 2011-06-21 11:40:38 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Fedora Admin XMLRPC Client on 2011-06-21 11:50:13 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Fedora Admin XMLRPC Client on 2011-06-21 11:52:38 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Fedora Admin XMLRPC Client on 2011-06-21 11:55:06 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Fedora Admin XMLRPC Client on 2011-06-21 11:56:26 EDT --- This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. --- Additional comment from Adam on 2011-07-24 17:45:33 EDT --- I'm also currently running into this bug. As a workaround, I have been logging in on a console to change my password. Below is a snip of the stack trace in the GDM logs when a user tries to log in while their password is in the expiry period. Specifically, it looks like GDM is failing when it receives the message via PAM that the password will expire soon. pam: gdm-password[10906]: pam_winbind(gdm-password:auth): user 'user1' granted access ** ERROR:gdm-session-worker.c:817:gdm_session_worker_process_pam_message: code should not be reached gdm[10907]: ******************* START ********************************** gdm[10907]: [Thread debugging using libthread_db enabled] gdm[10907]: 0x0018e416 in __kernel_vsyscall () gdm[10907]: #0 0x0018e416 in __kernel_vsyscall () gdm[10907]: #1 0x4533af63 in __waitpid_nocancel () from /lib/libpthread.so.0 gdm[10907]: #2 0x0805568d in ?? () gdm[10907]: #3 0x08055aa9 in ?? () gdm[10907]: #4 <signal handler called> gdm[10907]: #5 0x0018e416 in __kernel_vsyscall () gdm[10907]: #6 0x451ce26f in raise () from /lib/libc.so.6 gdm[10907]: #7 0x451cfba5 in abort () from /lib/libc.so.6 gdm[10907]: #8 0x4544669f in g_assertion_message () from /lib/libglib-2.0.so.0 gdm[10907]: #9 0x0804f06f in ?? () gdm[10907]: #10 0x005ae3d5 in ?? () from /lib/security/pam_winbind.so gdm[10907]: #11 0x005ae46a in ?? () from /lib/security/pam_winbind.so gdm[10907]: #12 0x005af074 in ?? () from /lib/security/pam_winbind.so gdm[10907]: #13 0x005af1ed in ?? () from /lib/security/pam_winbind.so gdm[10907]: #14 0x005b036a in ?? () from /lib/security/pam_winbind.so gdm[10907]: #15 0x005b0aee in pam_sm_authenticate () from /lib/security/pam_winbind.so gdm[10907]: #16 0x4601f615 in ?? () from /lib/libpam.so.0 gdm[10907]: #17 0x4601ed14 in pam_authenticate () from /lib/libpam.so.0 gdm[10907]: #18 0x080509bb in ?? () gdm[10907]: #19 0x4541c5d1 in ?? () from /lib/libglib-2.0.so.0 gdm[10907]: #20 0x454205bf in g_main_context_dispatch () from /lib/libglib-2.0.so.0 gdm[10907]: #21 0x45420d30 in ?? () from /lib/libglib-2.0.so.0 gdm[10907]: #22 0x45421457 in g_main_loop_run () from /lib/libglib-2.0.so.0 gdm[10907]: #23 0x0804bdff in ?? () gdm[10907]: #24 0x451b9413 in __libc_start_main () from /lib/libc.so.6 gdm[10907]: #25 0x0804beb5 in ?? () gdm[10907]: Backtrace stopped: Not enough registers or memory available to unwind further gdm[10907]: gdm[10907]: Thread 1 (Thread 0xb78658d0 (LWP 10906)): gdm[10907]: #0 0x0018e416 in __kernel_vsyscall () gdm[10907]: No symbol table info available. gdm[10907]: #1 0x4533af63 in __waitpid_nocancel () from /lib/libpthread.so.0 gdm[10907]: No symbol table info available. gdm[10907]: #2 0x0805568d in ?? () gdm[10907]: No symbol table info available. gdm[10907]: #3 0x08055aa9 in ?? () gdm[10907]: No symbol table info available. gdm[10907]: #4 <signal handler called> gdm[10907]: No symbol table info available. gdm[10907]: #5 0x0018e416 in __kernel_vsyscall () gdm[10907]: No symbol table info available. gdm[10907]: #6 0x451ce26f in raise () from /lib/libc.so.6 gdm[10907]: No symbol table info available. gdm[10907]: 5 in abort () from /lib/libc.so.6 gdm[10907]: No symbol table info available. gdm[10907]: #8 0x4544669f in g_assertion_message () from /lib/libglib-2.0.so.0 gdm[10907]: No symbol table info available. gdm[10907]: #9 0x0804f06f in ?? () gdm[10907]: No symbol table info available. gdm[10907]: /security/pam_winbind.so gdm[10907]: No symbol table info available. gdm[10907]: #11 0x005ae46a in ?? () from /lib/security/pam_winbind.so gdm[10907]: No symbol table info available. gdm[10907]: #12 0x005af074 in ?? () from /lib/security/pam_winbind.so gdm[10907]: No symbol table info available. gdm[10907]: ?? () from /lib/security/pam_winbind.so gdm[10907]: No symbol table info available. gdm[10907]: #14 0x005b036a in ?? () from /lib/security/pam_winbind.so gdm[10907]: No symbol table info available. gdm[10907]: #15 0x005b0aee in pam_sm_authenticate () from /lib/security/pam_winbind.so gdm[10907]: fo available. gdm[10907]: #16 0x4601f615 in ?? () from /lib/libpam.so.0 gdm[10907]: No symbol table info available. gdm[10907]: #17 0x4601ed14 in pam_authenticate () from /lib/libpam.so.0 gdm[10907]: No symbol table info available. gdm[10907]: #18 0x080509bb in ?? () gdm[10907]: No symbol table info available. gdm[10907]: in ?? () from /lib/libglib-2.0.so.0 gdm[10907]: No symbol table info available. gdm[10907]: #20 0x454205bf in g_main_context_dispatch () from /lib/libglib-2.0.so.0 gdm[10907]: No symbol table info available. gdm[10907]: #21 0x45420d30 in ?? () from /lib/libglib-2.0.so.0 gdm[10907]: No symbol table info available. gdm[10907]: #22 0x45421457 in g_main_loop_run () from /lib/libglib-2.0.so.0 gdm[10907]: No symbol table info available. gdm[10907]: #23 0x0804bdff in ?? () gdm[10907]: No symbol table info available. gdm[10907]: #24 0x451b9413 in __libc_start_main () from /lib/libc.so.6 gdm[10907]: No symbol table info available. gdm[10907]: b5 in ?? () gdm[10907]: No symbol table info available. gdm[10907]: Backtrace stopped: Not enough registers or memory available to unwind further gdm[10907]: A debugging session is active. gdm[10907]: gdm[10907]: Inferior 1 [process 10906] will be detached. gdm[10907]: gdm[10907]: inal] gdm[10907]: ******************* END ********************************** pam: gdm-password[10913]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user1 --- Additional comment from Adam on 2011-07-24 17:50:20 EDT --- Sorry for the double comment. I forgot to mention that I'm still experiencing this bug in Fedora 15, with all current patches applied. Also, console login works without a hitch (with the password expiry message displayed). --- Additional comment from Robert Foreman on 2011-12-23 10:16:48 EST --- Updated version to 16. Confirmed still happening --- Additional comment from Himanshu Bansal on 2012-02-21 12:04:56 EST --- workaround is to put "warn_pwd_expire = 1" in /etc/security/pam_winbind.conf file. --- Additional comment from Mark Chandler on 2012-05-03 22:23:56 EDT --- I've also experienced this problem (as recently as today). I'm on F16. I'll try the workaround. --- Additional comment from Fedora End Of Life on 2013-01-16 12:14:13 EST --- 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 --- Additional comment from Fedora End Of Life on 2013-02-13 16:42:12 EST --- Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.