| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=786829
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=759128
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
...and other various cleanups.
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
This will soon contain an extra enum.
https://bugzilla.gnome.org/show_bug.cgi?id=759128
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
We should have this included since we use the functions in it in our
precondition checks.
|
|
|
|
|
|
| |
Add a -d option to 'dconf read' to read the default value.
https://bugzilla.gnome.org/show_bug.cgi?id=758864
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=758864
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Add an API to read the default value of a key.
Add a testcase.
https://bugzilla.gnome.org/show_bug.cgi?id=758860
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
This makes coverity happy. It noticed that we check source for
being non-NULL every other case but not here.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=745500
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=744982
|
| |
|
| |
|
| |
|
|
|
|
|
| |
...to better match conventions in other modules, and to silence an
irrelevant warning about portability to Windows.
|
|
|
|
|
| |
...and add a <description> (as mandated by the push hook on
git.gnome.org).
|
| |
|
|
|
|
| |
Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Stock images are deprecated. Dconf-editor uses the GtkImage:stock
property in the close button in the search box. Replace it with the
GtkImage:icon-name property instead.
https://bugzilla.gnome.org/show_bug.cgi?id=739422
|
|
|
|
|
|
|
|
| |
The key_info_grid grid uses the deprecated "margin-right" property. It
should use "margin-end" which properly supports both left-to-right and
right-to-left text directions.
https://bugzilla.gnome.org/show_bug.cgi?id=739421
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|