I'm not sure about this, but I suspect that since the move from gconf to dconf, the %gconf files just reflect info that's actually held in the dconf database (by default ~/.conf/dconf/user I think) and manual changes to the file maybe don't propagate back to the db - you could try writing directly to the dconf db instead
Code:
dconf write /desktop/gnome/remote-access/prompt-enabled false
dconf update
In fact it seems like the %gconf file lags any updates to the actual db:
Code:
$ grep prompt_enabled ~/.gconf/desktop/gnome/remote_access/%gconf.xml
<entry name="prompt_enabled" mtime="1362695685" type="bool" value="true"/>
$
$ dconf write /desktop/gnome/remote-access/prompt-enabled false
$ dconf update
$ dconf read /desktop/gnome/remote-access/prompt-enabled
false
$ grep prompt_enabled ~/.gconf/desktop/gnome/remote_access/%gconf.xml
<entry name="prompt_enabled" mtime="1362695685" type="bool" value="true"/>
$ grep prompt_enabled ~/.gconf/desktop/gnome/remote_access/%gconf.xml
<entry name="prompt_enabled" mtime="1362695685" type="bool" value="true"/>
$ grep prompt_enabled ~/.gconf/desktop/gnome/remote_access/%gconf.xml
<entry name="prompt_enabled" mtime="1362695685" type="bool" value="true"/>
$ grep prompt_enabled ~/.gconf/desktop/gnome/remote_access/%gconf.xml
<entry name="prompt_enabled" mtime="1362695685" type="bool" value="true"/>
$ grep prompt_enabled ~/.gconf/desktop/gnome/remote_access/%gconf.xml
<entry name="prompt_enabled" mtime="1362695685" type="bool" value="true"/>
$ grep prompt_enabled ~/.gconf/desktop/gnome/remote_access/%gconf.xml
<entry name="prompt_enabled" mtime="1362695796" type="bool" value="false"/>
Bookmarks