Screen does not lock after suspend

Same with Hibernate..

Assigning this to gnome-session

(16:31:46) chrisccoulson: What should be responsible for locking the screen when a user suspends their machine from gnome-session now?
(16:32:21) chrisccoulson: gnome-session used to ask g-p-m to suspend the machine, which used to lock the screen, but that doesn't happen anymore now gnome-session uses dk-power directly
(16:33:46) hughsie: chrisccoulson: gnome-session needs to tell gnome-screensaver to lock

With gnome-screensaver now functional, so is locking upon resuming (by association). So, I guess this is fixed?

Seems wonky to rely on the screensaver options for such a security need. It isn't intuitive. Just because MS Windows goes that route doesn't make it the best way for sure.

I can confirm this with current Karmic. Changing the lock settings in gconf-editor have no effect. The screen is never locked after resume.

I can confirm this is still true as of Alpha 5. Why is this only medium importance when this is a security vulnerability? People who are used to previous behavior could still accidentally suspend without locking the screen first (even when knowing about this bug) from habit.

I tried gconf-editor and set /apps/gnome-power-manager/lock/use_screensaver_settings checked (my screen saver locks the screen), but this didn't help.

I'm up-to-date per Update Manager as of tonight (but my system is having a problem with grub-pc so I'm still booting to 2.6.31-9-generic rather than the -10's).

http://git.gnome.org/cgit/gnome-session/commit/?id=fc11487acb6584f7c9deb705e8bdf46aeee0aa75 appears to be an upstream commit for this from hughsie

I'm using Jaunty 9.04. Sometimes, after Resuming from Suspend, the computer will boot directly to the desktop without asking for a password. Should I file a bug report for Jaunty users?