GNOME Bugzilla – Bug 741437
dconf update doesn't use lock file changes
Last modified: 2014-12-12 17:08:21 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']" $
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 ***