Description of problem: If the user is forced to change their password and takes longer than 40 seconds to fill in the boxes then kdm deadlocks, leaving the system unusable. Version-Release number of selected component (if applicable): kdm-4.9.5-1.fc17.x86_64 How reproducible: 100% Steps to Reproduce: 1. Expire a user's password (test was done with sssd and a LDAP/Kerberos server) 2. Attempt to log in as that user on the kdm login screen 3. Get "password has expired" box, press OK 4. Wait 40 seconds Actual results: Text cursor stops flashing; all further input on keyboard and mouse is ignored. Expected results: Don't deadlock. :-)
Confirmed in Fedora 18 with SSSD/FreeIPA. Doesn't happen with regular user accounts.
There's a deadlock caused by setting KGVerify::coreState to coreIdle somewhere. I haven't found where yet... If it's set to coreIdle, KGreeter::slotLoadPrevWM() can send its commands to the core which is expecting a string this time, causing both to wait for each other's valid information when the timeout (FULL_GREET_TO - 40s) runs out.
I take that back, the password changing code is seriously bugged: It freezes even for regular accounts. When the dialog is cancelled by the user after one unsuccessful change (e.g. when the password was too short), it's not possible to log in and whole KDM has to be restarted. Once it occured to me that I wasn't able to input anything in the dialog at all and when I closed it, the rest of the changing conversation was going on in the main password prompt. (Though I'm not able to reproduce this)
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.
Still valid
*** Bug 1036933 has been marked as a duplicate of this bug. ***
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.
User reported happens on f23, re-opening mbriza, you commented looking into it way back when (~2013), can you comment on the odds of this being fixable in the foreseeable future? (we may have to admit failure and mark CANTFIX/WONTFIX)
I'm the one running into this. Unfortunately sddm doesn't even cope with expiring, expired or mustchange passwords so I'm stuck with KDM for the forseeable future. If there's anything I can test (even "try tweaking this code here") then I'm willing to give it a try.
There's some arcane ancient code in kdm inherited from xdm and then hacked to work with a KDE front-end. I don't think there's anybody able and willing to fix this problem these days. Maybe somebody could delve into the code and try to understand its working but I think that's too huge an effort for this project. And sorry, I don't remember anything really, it's been too long.
I'm trying to figure out if there's any alternative. SDDM doesn't handle this case as far as I know, or at least it didn't the last time I looked at it. Maybe I should look into moving to GDM, although I'd really like to stay in KDE-land as much as possible.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.