Description of problem: I only installed F22 last week, but have noticed a couple of times a day coming back to the computer to find it hasn't locked like it should, instead showing Unable to Lock: lock was blocked by an application Version-Release number of selected component (if applicable): How reproducible: 20-50% of the times screen locking should be called Steps to Reproduce: 1. walk away 2. come back 3. Actual results: Expected results: Additional info: I'm running the standard Gnome install - haven't had the chance to fiddle with cinnamon/etc syslog shows the following - which may help. Jun 9 14:23:56 jhaar-nzc-ll gnome-session: Gjs-Message: JS LOG: pushModal: invocation of begin_modal failed Jun 9 14:23:56 jhaar-nzc-ll gnome-session: Gjs-Message: JS LOG: pushModal: invocation of begin_modal failed Jun 9 14:23:56 jhaar-nzc-ll gnome-session: Gjs-Message: JS LOG: error: Unable to lock: Lock was blocked by an application I must agree with the writer of this webpage who had the same problem in F19. It would really help if the error said exactly what was blocking it! http://osdir.com/ml/fedora-users/2013-10/msg00492.html Finally, I marked it urgent because frankly it's a security hole. You can't just vaguely try to lock the screen - it has to work. This laptop had Ubuntu-14.04 on it before and F20 before that - and neither had this issue.
Six months have passed and this security hole is still present in a fully up-to-date F22 system I walk away from my desktop for hours and come back to find it never locked... Just saying...
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.