summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* WIP1454-gvdb-corruptionPhilip Withnall2018-08-014-12/+41
| | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
* WIPPhilip Withnall2018-08-013-2/+51
| | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
* service: Allow opening corrupt GVDB files when writingPhilip Withnall2018-08-011-1/+31
| | | | | | | | | | | | | | | | | If a GVDB file cannot be opened due to being corrupt, move it out of the way, warn, and open a new blank database instead. This prevents the situation where a corrupt database stops the entire desktop session from loading. Note that the dconf_gvdb_utils_read_file() code path is only taken inside DConfWriter. The DConf engine sources (such as dconf-engine-source-system.c) open the GVDB tables separately, and already all handle errors gracefully. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1454
* docs: Update documentation for GVDB ‘submodule’Philip Withnall2018-08-011-4/+5
| | | | | | | | This is non-optimal. In fact, it’s quite painful. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* gvdb: Update to latest GVDB code from GLib masterPhilip Withnall2018-08-015-15/+31
| | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
* service: Port from g_type_class_add_private() to G_ADD_PRIVATE()Philip Withnall2018-08-011-3/+2
| | | | | | The former has been deprecated for a long time. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* Merge branch 'patch-1' into 'master'Philip Withnall2018-08-011-1/+1
|\ | | | | | | | | dconf-update.vala: correct error message grammar See merge request GNOME/dconf!6
| * dconf-update.vala: correct error message grammarKenyon Ralph2018-07-261-1/+1
|/
* Merge branch 'patch/ow' into 'master'Ray Strode2018-07-133-14/+151
|\ | | | | | | | | Engine: track in progress watch handles to avoid spurious changed signals for the root path See merge request GNOME/dconf!1
| * Engine: track in progress watch handles to avoid spurious changed signals ↵Daniel Playfair Cal2018-07-133-14/+151
|/ | | | for the root path
* Don't create the user config dir as world readableSebastien Bacher2018-04-172-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=792677
* Revert "Disable another failing test"Michael Catanzaro2018-03-131-2/+1
| | | | This reverts commit a9cc9f30b8cc340428cb781797dacd60b39f1de6.
* Prepare 0.28.00.28.0Michael Catanzaro2018-03-132-1/+6
|
* Disable another failing testMichael Catanzaro2018-03-131-1/+2
| | | | Interestingly, it's a different failing test than last time. Yippee!
* Remove .gitignore filesIñigo Martínez2017-10-2212-83/+0
| | | | | | | | | | meson does not allow to build source code inside the source code tree, for this reason there is no need for .gitignore files to ignore built files. This patch removes .gitignore files which are no longer needed. https://bugzilla.gnome.org/show_bug.cgi?id=784910
* Update the README fileIñigo Martínez2017-10-221-17/+9
| | | | | | | | | | | The README file still shows information about the dconf editor, which is no longer part of dconf, and also about the steps to build dconf using autotools. This patch removes any mention of dconf-editor and also replaces the autotools' build steps for their meson's equivalents. https://bugzilla.gnome.org/show_bug.cgi?id=784910
* Revert "Disable broken test"Michael Catanzaro2017-10-171-2/+1
| | | | | | | This reverts commit ab2692a967c6a19e532014391d402fa428131ccc. I figure whoever cares for dconf in the future will probably want to know that this test is broken.
* Prepare 0.27.10.27.1Michael Catanzaro2017-10-172-1/+6
|
* Disable broken testMichael Catanzaro2017-10-171-1/+2
| | | | | I've verified this test is broken in the 0.24 release as well, so it's not a regression in dconf itself.
* build: Remove autotoolsIñigo Martínez2017-10-1716-622/+0
| | | | | | | To avoid the burden of maintaining multiple build systems, this patch removes autotools support. https://bugzilla.gnome.org/show_bug.cgi?id=784910
* build: Port to meson build systemIñigo Martínez2017-10-1727-6/+589
| | | | | | | | meson is a build system focused on speed an ease of use, which helps speeding up the software development. This patch adds meson support along autotools. https://bugzilla.gnome.org/show_bug.cgi?id=784910
* build: changed abicheck.sh scriptIñigo Martínez2017-10-172-1/+4
| | | | | | | | | | abicheck.sh script has been changed to check the libdconfsettings library from GSETTINGS_LIB environment variable. This helps when checking the library in different locations. 'shebang' has also been added. https://bugzilla.gnome.org/show_bug.cgi?id=784910
* 3.26.10.26.1dconf-0.26Matthias Clasen2017-10-032-1/+6
|
* Fix a typo in manpagePiotr Drąg2017-08-291-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=786829
* gdbus: Work around threading deadlock in glibColin Walters2016-11-181-0/+4
| | | | | | See https://bugzilla.gnome.org/show_bug.cgi?id=674885 for more details. What dconf is doing right now provokes this more easily by involving *another* thread in the mix.
* dconf 0.26.00.26.0Allison Ryan Lortie2016-03-232-1/+6
|
* dconf 0.25.10.25.1Allison Ryan Lortie2015-12-162-1/+35
|
* DConfClient: Add "writability-changed" signalXavier Claessens2015-12-161-0/+27
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=759128
* client: restrict list_locks to work on dirsAllison Ryan Lortie2015-12-162-4/+4
| | | | | | | This was always the intention, and is even documented that way in the gtk-doc block above. I'm not sure why I used paths. In any case, this API has never been released, so the change is safe.
* DConfChangeset: add missing 'static' on functionAllison Ryan Lortie2015-12-161-1/+1
|
* docs: add new APIsAllison Ryan Lortie2015-12-163-0/+40
| | | | ...and other various cleanups.
* client: replace _read_default() with _read_full()Allison Ryan Lortie2015-12-165-24/+52
| | | | | | | | | This API has never appeared in a released version of dconf (even unstable). Replace it with a more generally-useful form. Update the test cases, dconf commandline tool and vapi accordingly. https://bugzilla.gnome.org/show_bug.cgi?id=759128
* engine: some internal const-correctness changesAllison Ryan Lortie2015-12-162-6/+6
| | | | | | | There is no reason that the read_through queue should not be 'const', so expose it as such. https://bugzilla.gnome.org/show_bug.cgi?id=759128
* engine: add DCONF_READ_DEFAULT_VALUE flagAllison Ryan Lortie2015-12-164-46/+20
| | | | | | | | Add a flag that allows checking the default value without constructing a read_through queue. Make use of this new flag to simplify code in a couple of places. https://bugzilla.gnome.org/show_bug.cgi?id=759128
* engine: merge _read and _read_user_value()Allison Ryan Lortie2015-12-166-85/+51
| | | | | | | Delete the separate dconf_engine_read_user_value() and merge its functionality into dconf_engine_read() by adding a flags field. https://bugzilla.gnome.org/show_bug.cgi?id=759128
* common: rename dconf-error.h to dconf-enums.hAllison Ryan Lortie2015-12-167-6/+6
| | | | | | This will soon contain an extra enum. https://bugzilla.gnome.org/show_bug.cgi?id=759128
* Remove libdbus-1 supportAllison Ryan Lortie2015-12-1610-696/+1
| | | | | | | | Stop building the dconf-dbus-1 client library. Nobody is using it anymore and we will soon be taking a non-conditional dependency on libgio in any case. It is now only possible to use dconf with GDBus.
* Modernise the headers of dconf-clientAllison Ryan Lortie2015-11-304-9/+8
| | | | | | | Add support for g_autoptr() on DConfClient and DConfChangeset. Switch to using G_DECLARE_FINAL_TYPE in the declaration of DConfClient. https://bugzilla.gnome.org/show_bug.cgi?id=758871
* dconf-client: include dconf-paths headerAllison Ryan Lortie2015-11-301-0/+1
| | | | | We should have this included since we use the functions in it in our precondition checks.
* dconf(1): add -d option to 'dconf read'Allison Ryan Lortie2015-11-301-4/+18
| | | | | | Add a -d option to 'dconf read' to read the default value. https://bugzilla.gnome.org/show_bug.cgi?id=758864
* dconf(1) tool: add list-locks commandAllison Ryan Lortie2015-11-301-12/+29
| | | | | | | Add a list-locks command to the dconf commandline tool to list the locks that are present in the current configuration. https://bugzilla.gnome.org/show_bug.cgi?id=758864
* vapi: add new API read_default() to vapiAllison Ryan Lortie2015-11-301-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=758864
* engine, client: add list_locks() operationAllison Ryan Lortie2015-11-306-0/+111
| | | | | | | Add an API to dconf-engine (and exposed via DConfClient) for getting a list of locks that are present in a given dconf profile. https://bugzilla.gnome.org/show_bug.cgi?id=758864
* DConfClient: add read_default() APIAllison Ryan Lortie2015-11-303-0/+60
| | | | | | | | Add an API to read the default value of a key. Add a testcase. https://bugzilla.gnome.org/show_bug.cgi?id=758860
* DConfChangeset: implement dir resets properlyAllison Ryan Lortie2015-11-302-15/+69
| | | | | | | | | | | | | | | | | | If a dir is reset against a DConfChangeset then the result ought to be that all keys under that dir read as NULL (until such a time as they are set to a new value). This is consistent with the (existing) behaviour that a key will read as NULL if it, itself, was reset. In order to make that efficient, we create a separate GHashTable to serve as a cache of all of the directories that have been reset and iterate it whenever we do a key lookup that doesn't have a direct hit. We update (and expand) the test case to reflect this new reality -- the tests actually had a case that relied on the inconsistent behaviour. https://bugzilla.gnome.org/show_bug.cgi?id=744678
* engine: add support for runtime profile selectionAllison Ryan Lortie2015-11-111-12/+77
| | | | | | | | | | | | | | | | | | | | | | | | Add support to dconf-engine for opening "runtime" profiles. These profiles are intended to be symbolic links or plain files that will live either in XDG_RUNTIME_DIR/dconf/profile or /run/dconf/user/$(uid). This is intended to allow for a PAM module that makes complex decisions about application of a specific policy to a user and sets up the profile at login time, thus preventing the need for this complex decision to be a part of every program that uses dconf. This PAM module would not be part of dconf, but would rather be a part of a dconf-aware system administrator framework. In the case that the profile file is found in /run/dconf, then it will not be possible for the user to override the profile selection, including via the DCONF_PROFILE environment variable. This provides a mechanism for lockdown that is slightly more difficult for a user to circumvent. In theory, this is pointless since it can still be defeated with LD_PRELOAD, but in practice this raises the bar quite a bit. https://bugzilla.gnome.org/show_bug.cgi?id=751417
* tests: Add an assertiondconf-0.24Matthias Clasen2015-07-171-0/+1
| | | | | This makes coverity happy. It noticed that we check source for being non-NULL every other case but not here.
* dconf 0.24.00.24.0Ryan Lortie2015-03-232-1/+6
|
* dconf 0.23.20.23.2Ryan Lortie2015-03-162-1/+8
|
* docs: remove dconf-editor xinclude from toplevelRyan Lortie2015-03-161-1/+0
|
View Lorry Controller Status