There is no way to fix this as long as X11 is still being used. Lock
screen timing issues are usually caused by a few different things:

1- Hardware issues. Certain models of computers have known issues where
they don't generate the proper events when the laptop lid is closed or
the suspend hotkey is pressed. In those cases, the laptop will enter the
suspend state before notifying the OS, which results in the screen not
being locked when the laptop wakes up. These issues need to be addressed
with a firmware update, or with a quirk being added to whatever platform
specific driver is in the kernel. This is the type of thing that is
tested and fixed when a laptop gets certified and preloaded with Ubuntu.

2- Actual bugs in the screen locking code. This has happened in the
past, and still occurs occasionally.

3- X11 not allowing the screen lock to forcibly remove keyboard and
mouse grabs. This is the major reason why screen locking will never work
reliably as long as we haven't switched to Wayland or Mir. For the
screen to lock, it must be able to exclusively grab the keyboard or
mouse. Unfortunately, there is no way under X11 to forcibly remove a
keyboard or mouse grab that belongs to another application. When this
happens, for example when you have a menu open, or you're using software
such as Virtalbox, the screen is unable to lock before the laptop goes
into suspend mode.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1280300

Title:
  Desktop contents displayed on resume, before lock screen is shown

Status in gnome-screensaver package in Ubuntu:
  Invalid

Bug description:
  I am running 14.04. When I resume from sleep, the contents of my
  desktop (including any open windows, emails, etc) are displayed
  onscreen briefly before the unlock screen is shown. This potentially
  allows an attacker to view the contents of a locked screen.

  To reproduce:
  1) Suspend a machine, e.g. by closing the lid
  2) Resume the machine

  Expected results:
  Upon resume, the first thing shown onscreen is the screensaver unlock screen.

  Actual results:
  Upon resume, the first thing shown onscreen is the set of open windows that 
were displayed before the machine was put to sleep. After a second or two, the 
unlock screen is drawn and you have to enter a password to unlock the machine.

  This is reproducible on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 14 09:05:50 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2013-12-02 (73 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to