Happened in F-7 and now in rawhide. The lock screen option from the system menu
doesn't do anything. When I try to run gnome-screensaver from a shell, I get this:
***MEMORY-WARNING***: gnome-screensaver: 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...
** (gnome-screensaver:9864): WARNING **: screensaver already running in this session
i can confirm this bug in rawhide.
The g_thread_init message shown above is because of the glib2 issues reported in
many other bugs. However, even when I downgrade glib2 and gtk2 to the FC7
version and the g_thread_init issues goes away, gnome-screensaver still isn't
starting when I log in. When I start it manually it works, but it doesn't show
up in the Sessions preferences app, either in the "Startup Programs" tab or the
"Current Session" tab, so GNOME doesn't know to restart it when I log out and
log back in.
Upgrading severity. It's a security issue for the screensaver and hence
automatic screen locking not to work properly. Not quite bad enough to
categorize it as "urgent", I'd say, but certainly worse than "low".
As of today, this issue seems to have disappeared in rawhide. gnome-screensaver
is working fine. Can anyone else confirm using the latest rawhide updates?
It seems to be working for me as well.