GNOME Bugzilla – Bug 646673
remove gconf sanity check gunk
Last modified: 2011-08-28 20:56:51 UTC
We should not explicitly call gconf-sanity-check on startup. GConf hasn't used file locking for a couple of years now anyway.
Created attachment 185077 [details] [review] Remove calls to gconf-sanity-check GConf doesn't use file locking for years anyway.
Vincent, can we get this in for 3.2 ? It is obviously the right thing to do, as far as I am concerned.
The following fixes have been pushed: e5711e5 Add AM_PROG_CC_C_O 093d319 Remove calls to gconf-sanity-check
Created attachment 194990 [details] [review] Add AM_PROG_CC_C_O automake complained about its absence.
Created attachment 194991 [details] [review] Remove calls to gconf-sanity-check GConf doesn't use file locking for years anyway.