screensaver and screen locking not activating if keyring dialogue is open

Bug #643399 reported by Konrads Smelkovs
266
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

Binary package hint: xscreensaver

If password input dialogue, such as gnome keyring prompt or gksu is open, then screensaver will not automatically start if desktop is left idle for the pre-configured amount of time. This makes security of automatic screen locking inefficient in certain cases. Upon password entry or dialog cancellation, screensaver starts.
How to reproduce:
1) Configure xscreensaver with a delay of 1 minute
2) open an application asking for keyring passphrase entry or gksu dialog
3) Wait for one minute, screensaver does not kick in
4) Enter passphrase/password or cancel dialog, screensaver starts.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xscreensaver (not installed)
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Mon Sep 20 13:11:46 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xscreensaver

visibility: private → public
Revision history for this message
Alexander Gnodtke (gnodtke) wrote :

I was able to reproduce this behavior on 10.04 and on 10.10 beta.

Changed in xscreensaver (Ubuntu):
status: New → Confirmed
Changed in xscreensaver (Ubuntu):
status: Confirmed → Triaged
affects: xscreensaver (Ubuntu) → gnome-screensaver (Ubuntu)
Revision history for this message
Delta-Z (zinenko) wrote :

Still reproducible in Unity3D in 12.04.

To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.