Comment 30 for bug 49579

I agree with Josh 110%.

Kernel bugs are fixed and pushed upstream by Canonical folks. Why not GTK
bugs / issues? How about security issues for that matter? Waiting 5 1/2
years for a security fix is pretty sad regardless of whos fault it is or
who maintains the code. As a customer of Canonical, I don't care who
maintains the code -- I put the bug into Canonical's bug system, so I
expect someone from Canonical to follow through on it. Simple as that.

On Sun, Dec 4, 2011 at 12:57 PM, Josh Leverette <email address hidden>wrote:

> Critical bugs have always been solved in a fix first, push fix upstream
> later approach. This is a critical bug. Companies could unwillingly give
> up critical data because a screen didn't lock.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (597521).
> https://bugs.launchpad.net/bugs/49579
>
> Title:
> screen doesn't lock when panel menu is open
>
> Status in GNOME Screensaver:
> Confirmed
> Status in “gnome-screensaver” package in Ubuntu:
> Triaged
>
> 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
>