Comment 65 for bug 49579

That entirely depends on how much your prioritize security over usefulness.
I would not want that to happen, because I don't have secure things, by and
large. I can completely understand other people disagreeing. Ubuntu isn't
about prioritizing security over all else, I feel. A shutdown is excessive
to avoid people seeing the screen for a few seconds.

On Tue, Nov 5, 2013 at 9:36 AM, Obadz <email address hidden> wrote:

> > Killing just the X session (client) holding the lock is unacceptable
> because killing a user's apps or shell is worse than the bug itself.
>
> I wholeheartedly disagree. shutdown the computer altogether would be
> less bad than granting access when the user expects otherwise..
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1215976).
> https://bugs.launchpad.net/bugs/49579
>
> Title:
> screen doesn't lock when some menu is open
>
> Status in GNOME Screensaver:
> Confirmed
> Status in OEM Priority Project:
> Won't Fix
> Status in OEM Priority Project precise series:
> Won't Fix
> Status in X.Org X server:
> Confirmed
> Status in “gnome-screensaver” package in Ubuntu:
> Triaged
> Status in “gnome-screensaver” source package in Precise:
> Confirmed
> Status in “xorg-server” package in Debian:
> Confirmed
>
> Bug description:
> Binary package hint: gnome-screensaver
>
> I'm running a fresh install of Dapper with screensaver set to 'blank
> screen', and 'lock screen when screensaver is active' enabled.
>
> If a panel menu (e.g. Applications) is open and the machine is left
> idle, the screen fails to lock. It fades out after the time period as
> expected, but the desktop reappears after a few seconds.
>
> Ben (comments / criticism welcome, this is my first bug report)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
>