Bug 668241 - Poor UX in interaction with suspend/resume 'Time has expired'
Poor UX in interaction with suspend/resume 'Time has expired'
Product: Fedora
Classification: Fedora
Component: gnome-screensaver (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-01-09 06:10 EST by cam
Modified: 2012-08-16 16:28 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-16 16:28:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description cam 2011-01-09 06:10:07 EST
The screen is locked after periods of inactivity, or immediately if the machine suspends and resumes. There seems to be some occasional odd behaviour on resume.

Sometimes the background appears, a second later the password dialog appears and this seems normal.

The odd behaviour is that the background and dialog box appear immediately with the password field blank. The user feedback field has a message about 'Time has expired' and there is a short delay where the dialog box is unresponsive; it is closed automatically and reopened, then the user can proceed as per the first case described above. If there is no user input the screen blanks waiting for further input. This interaction and delay is annoying and gives a poor user experience.

Version-Release number of selected component (if applicable):
gnome-shell-2.31.5-7.fc14.i686 in use
Also using xorg-x11-drv-nouveau-0.0.16-11.20100826git065576d.fc14.i686

How reproducible:
Intermittent but common, possibly 30% of resumes.

Steps to Reproduce:
1.configure to lock on suspend
Actual results:
Possibly there is some processing before suspend is complete, eg keypress or keycode detected that triggers the timer on the dialog to start; on resume sufficient time has elapsed before any input and a timeout condition is erroneously detected.

Expected results:
Consistent behaviour (normal behaviour is OK).
Timely presentation of a working unlock dialog (delays are bad).
Removal of jargon 'Time has expired' is not a useful or meaningful message to the user, and in combination with a forced delay and period of non-responsiveness it is frustrating. Is there some way of auto-cancelling the dialog and giving the user a warning that this is happening, much like the expiring clock on desktop notifications?

Additional info:
This was seen on a medium powered machine (netbook with 3Gb RAM, SSD, Atom N270) and may be different on other faster or slower machines.
Comment 1 Fedora Admin XMLRPC Client 2011-06-21 11:59:46 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Fedora End Of Life 2012-08-16 16:28:14 EDT
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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: 

Note You need to log in before you can comment on or make changes to this bug.