Comment 9 for bug 854717

I temporarily chmod 0'ed the session, application, sound, and power indicator libs in /usr/lib/indicators3/6/, and that caused g-s-d to start up properly. I still have a gnome-screensaver process running, I don't know where that is coming from (perhaps from g-s-d itself), but that doesn't seem to be the one which triggers the early g-s-d. So I suppose one of the indicators invokes g-s-d as well, races with the other instance, and fails.