After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 741437 - dconf update doesn't use lock file changes
dconf update doesn't use lock file changes
Status: RESOLVED DUPLICATE of bug 708258
Product: dconf
Classification: Core
Component: dconf
0.22.x
Other Linux
: Normal normal
: ---
Assigned To: dconf-maint
dconf-maint
Depends on:
Blocks:
 
 
Reported: 2014-12-12 11:36 UTC by Murray Cumming
Modified: 2014-12-12 17:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Murray Cumming 2014-12-12 11:36:52 UTC
I'm only just starting to learn how dconf works, but it doesn't seem correct that a lock stays in effect even after I've removed the key from the lock file and done dconf update, though removing the file completely does properly remove the lock.

This is on Ubuntu 14.10 with dconf 0.22.0.


For instance,

$ sudo dconf update
$ gsettings set org.gnome.shell favorite-apps "['test1']"
$
$ echo "/org/gnome/shell/favorite-apps" | sudo tee --append /etc/dconf/db/local.d/locks/00_locks
/org/gnome/shell/favorite-apps
$ sudo dconf update
$ gsettings set org.gnome.shell favorite-apps "['test2']"
The key is not writable
$ echo "" | sudo tee /etc/dconf/db/local.d/locks/00_locks

$ sudo dconf update
$ gsettings set org.gnome.shell favorite-apps "['test3']"
The key is not writable
$ more /etc/dconf/db/local.d/locks/00_locks

$ sudo rm  /etc/dconf/db/local.d/locks/00_locks 
$ sudo dconf update
$ gsettings set org.gnome.shell favorite-apps "['test4']"
$
Comment 1 David King 2014-12-12 17:08:21 UTC
Piping text to the file within the locks directory does not update the mtime of the directory, so dconf update does not pick up the change. Removing a file updates the mtime on the directory. There is already an open bug about this bahaviour.

*** This bug has been marked as a duplicate of bug 708258 ***