Add a gconf key for setting the time delay before to start 'gnome-screensaver' at session startup

Bug #367271 reported by Fortunato Ventre
4
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

In Intrepid I was used to enable the autologin feature in gdm, then add the 'gnome-screensaver-command --lock' in Startup Applications to lock the screen immediately after login. This way I was ready to work just inserting my user password. Furthermore, when I started up my notebook with battery and get away from it, brightness was automatically adjusted by gnome-power-manager.
In Jaunty, 'gnome-screensaver' is not immediately started at session startup, instead it's delayed by 30 seconds and there is no way to customize this delay. This makes impossibile to lock the screen.
I've attached a patch that adds a new gconf key ('/apps/gnome_settings_daemon/screensaver/start_screensaver_timeout') and makes possible to customize the delay. It defaults to 30 seconds.
Setting it to 0 causes the 'gnome-screensaver' to be immediately started as it happens in Intrepid, so the problem is fixed.

Revision history for this message
Fortunato Ventre (voria) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gnome-settings-daemon (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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