Description of problem: gnome-screensaver doesn't start automatically /apps/gnome_settings_daemon/screensaver/start_screenaver value is true. Version-Release number of selected component (if applicable): 2.19.3-6.fc8 How reproducible: always Steps to Reproduce: 1. Booting login 2. Launch gnome-terminal 3. ps ax | grep gnome-screensaver Actual results: Expected results: Additional info: gnome-session-2.19.3-1.fc8 dbus-1.0.2-4.fc7 gnome-screensaver-2.19.1.1-1.fc8
logged in as root?
No, normal user.
I noticed this on my rawhide update on Friday also
If you type gnome-screensaver at the console does it start?
Booting Launch gnome-terminal $ ps ax | grep gnome-screensaver 3170 pts/0 S+ 0:00 grep gnome-screensaver $ gnome-screensaver ***MEMORY-WARNING***: gnome-screensaver[3177]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... $ ps ax | grep gnome-screensaver 3178 ? Ss 0:00 gnome-screensaver 3182 pts/0 S+ 0:00 grep gnome-screensaver gnome-screensaver starts well at the console.
Could you please set the following GConf key to true: /apps/gnome_settings_daemon/screensaver/show_startup_errors and let us know of any errors on session startup?
(In reply to comment #6) > Could you please set the following GConf key to true: > /apps/gnome_settings_daemon/screensaver/show_startup_errors $ gconftool-2 --get /apps/gnome_settings_daemon/screensaver/show_startup_errors [...] true /apps/gnome_settings_daemon/screensaver/show_startup_errors' default value is true. > let us know of any errors on session startup? No. > and let us know of any errors on session startup?
So you get a warning in the startup logs, and gnome-screensaver isn't running after a little while (ie. no output in "ps aux | grep gnome-screensaver")? If so, that would mean that gnome-screensaver is crashing, and it's a problem with gnome-screensaver.
Created attachment 156791 [details] ~/.xsession-errors doesn't has gnome-screensaver's error log. (In reply to comment #8) > So you get a warning in the startup logs, and gnome-screensaver isn't running > after a little while (ie. no output in "ps aux | grep gnome-screensaver")? Error message dialog doesn't appear in the startup. > If so, that would mean that gnome-screensaver is crashing, and it's a problem > with gnome-screensaver. Is gnome-screensaver crashing? I don't know that. I know that gnome-screensaver doesn't luanch in startup.
After installing 2.19.4-3.fc8 ( see also bug 244843 ), error dialog shows "There was an error starting up the screensaver Failed to execute child process "gnome-screensaver (No such file or directory) Screensaver functionality will not work in this session." $ rpm -qf /usr/bin/gnome-screensaver gnome-screensaver-2.19.1.1-1.fc8
Fixed in control-center-2.19.4-4.fc8