Bug 1042249

After killing the session launched screensaver, I launched it in a terminal with the '--debug' option and captured the output.  I did this when it worked and when it failed to show the password dialog. The main difference between the two logs is that the log of the failed run has:-

[listener_dbus_handle_system_message] gs-listener-dbus.c:881 (19:33:57):	 obj_path=/org/freedesktop/login1/session/_31 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[gs_manager_request_unlock] gs-manager.c:1326 (19:33:57):	 Request unlock but dialog is already up
[listener_dbus_handle_system_message] gs-listener-dbus.c:881 (19:33:57):	 obj_path=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:881 (19:33:58):	 obj_path=/org/freedesktop/login1/session/_31 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[gs_manager_request_unlock] gs-manager.c:1326 (19:33:58):	 Request unlock but dialog is already up
[listener_dbus_handle_system_message] gs-listener-dbus.c:881 (19:33:58):	 obj_path=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)

Not certain if it's relevant though!

I have the same issue in that the screen is locked but the password dialog does not always show up.

Plus, sometimes what was visible on the screen just before it is locked is shown when attempting to unlock the screen, at other times what was on the screen several seconds / minutes prior to locking is shown (e.g. The Firefox, Google Chrome or Thunderbird window that was minimized), sometimes only the desktop background is shown and at other times a black screen is shown.

I haven't read up on the internals of X and display managers in quite a while but I'm speculating that the screensaver is showing part of the off-screen buffer that was previously used.

For other experiencing this problem, you can consistently unlock your screen when the password dialog doesn't show up by first hitting [esc] so that the cursor disappears then start typing your password blindly (you will notice the cursor appear when you type the first character of your password).


Version Info:

# rpm -qi cinnamon-screensaver
Name        : cinnamon-screensaver
Version     : 2.2.3
Release     : 1.fc20
Architecture: x86_64
Install Date: Thu 22 May 2014 12:19:04 PM EDT
Group       : Unspecified
Size        : 291060
License     : GPLv2+ and LGPLv2+
Signature   : RSA/SHA256, Sun 11 May 2014 04:55:22 PM EDT, Key ID 2eb161fa246110c1
Source RPM  : cinnamon-screensaver-2.2.3-1.fc20.src.rpm
Build Date  : Sun 11 May 2014 07:33:29 AM EDT
Build Host  : buildvm-27.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : http://cinnamon.linuxmint.com
Summary     : Cinnamon Screensaver

# rpm -qi cinnamon
Name        : cinnamon
Version     : 2.2.10
Release     : 1.fc20
Architecture: x86_64
Install Date: Thu 05 Jun 2014 07:38:32 PM EDT
Group       : Unspecified
Size        : 7069856
License     : GPLv2+ and LGPLv2+
Signature   : RSA/SHA256, Wed 21 May 2014 11:20:21 AM EDT, Key ID 2eb161fa246110c1
Source RPM  : cinnamon-2.2.10-1.fc20.src.rpm
Build Date  : Tue 20 May 2014 03:54:08 PM EDT
Build Host  : buildvm-27.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : http://cinnamon.linuxmint.com
Summary     : Window management and application launching for GNOME

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.