Ken, You might also want to investigate this page, particularly the section on locks. I doubt you’ll find one for GnuCash, but somehow that system might have an overall lock on it.
https://developer.gnome.org/dconf/unstable/dconf-overview.html Regards, Adrien > On Aug 18, 2018, at 9:42 AM, Colin Law <clan...@gmail.com> wrote: > > On Sat, 18 Aug 2018 at 15:19, Adrien Monteleone > <adrien.montele...@lusfiber.net> wrote: > I think Ken mentioned GnuCash 2.6.15 in Debian Stretch in the OP. > > I missed that. Thanks. > > Ken, dconf not working can be caused by corrupted dconf config files. This > can happen if there is power fail apparently. Try this in a terminal after > closing all apps down. > mv .config/dconf .config/dconf.save > which will move that folder out of the way, dconf should recreate it. Log > out and back in again (this may not be necessary in fact, not sure), then try > dconf-editor again and see if it saves things now. > You may well find that other apps that use dconf will have gone back to > default values. > > If doing this messes things up then you can always restore the orginal using > mv .config/dconf .config/dconf.regenerated > mv .config/dconf.save .config/dconf > If the first command says it can't find .config/dconf then that is ok, it > just means it had not been recreated. > > Colin > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
