Comment 40 for bug 49579

closing a leak does not always mean inserting a plug, sometimes it just
means lessening the leak to a trickle, one that you can afford to pay for.
In this case, a trickle will do for now.

On Tue, Oct 9, 2012 at 9:07 AM, Marco Trevisan (Treviño) <mail@3v1n0.net>wrote:

> Probably we could workaround this problem in unity-panel service, by
> closing a menu when a such request has been done by UPower, however this
> would not fix the problems with other application menus.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (827068).
> 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 “gnome-screensaver” package in Ubuntu:
> Triaged
> Status in “gnome-screensaver” source package in Precise:
> 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
>

--
Sincerely,
    Josh