| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On systems using systemd --user and
dbus-daemon --session --systemd-activation, this means that dconf
is correctly placed in its own cgroup, instead of being part of
dbus.service's cgroup. This allows it to be controlled by
systemctl --user, have resource limits set and so on.
On other systems (in particular those where systemd is not used at all),
the SystemdService field is ignored and dbus-daemon will continue to
start dconf-service as its own child process ("traditional activation"),
making this change harmless to apply.
Resolves: https://gitlab.gnome.org/GNOME/dconf/-/issues/24
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|\
| |
| |
| |
| | |
Increment version number for 0.39 unstable series
See merge request GNOME/dconf!62
|
|/ |
|
|\
| |
| |
| |
| | |
Release 0.38.0
See merge request GNOME/dconf!61
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While working with Dconf I noticed in the bash CLI
I was unable to autocomplete when typing "dconf compile"
This fix will make it so the user is able to auto complete
the compile option in bash.
I have tested it on my Manjaro and PopOS! machines
and it's working expected.
As this is my first contribution please look twice so I have
not missed anything.
Signed-off-by: Andreas Polnas <andreas.polnas93@hotmail.com>
|
|\
| |
| |
| |
| | |
build: Install bash-completion relative to datadir
See merge request GNOME/dconf!58
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since bash-completion 2.9, it was no longer possible to override
the completionsdir through prefix. [1] In 2.10, the overridability
was re-estabilished but this time through datadir variable. [2]
This should not really matter except for developers installing the project
into a custom prefix or distros using per-package prefixes like NixOS.
[1]: https://github.com/scop/bash-completion/commit/81ba2c7e7dfbaefbafa1e8615727c9612e5fb314
[2]: https://github.com/scop/bash-completion/pull/344
Co-Authored-By: Iñigo Martínez <inigomartinez@gmail.com>
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Release 0.35.1
See merge request GNOME/dconf!57
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
Service: only emit changed signals when values change
See merge request GNOME/dconf!3
|
| |
| |
| |
| | |
succeeded
|
| | |
|
| | |
|
| |
| |
| |
| | |
when appropriate
|
| | |
|
|/
|
|
| |
are only emitted if new values differ from existing values
|
|\
| |
| |
| |
| |
| |
| | |
build: Update use of link_whole for meson-0.52
Closes #59
See merge request GNOME/dconf!54
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
A regression in meson-0.52 caused uses of link_whole to expose scenarios
where duplicate symbols issues could appear. In particular
libdconf_client_dep was being link_whole'd to itself, which recursively
already included libdconf_common which was also a link_whole.
This change does not modify the available symbols in libdconf.so, and is
compatible with meson-0.52 and 0.51.
See: https://github.com/mesonbuild/meson/pull/6030
Fixes: https://gitlab.gnome.org/GNOME/dconf/issues/59
|
|
|
|
|
|
|
|
|
|
|
| |
gcc-9 is including `mangle_path` in the symbols of
gsettings/libdconfsettings.so when building with support for gcov
(--coverage). This means that our ignored symbols had to be updated.
Update abicheck.sh so the test suite passes again. Also include a
comment to explain the above and how the test works.
Fixes: https://gitlab.gnome.org/GNOME/dconf/issues/60
|
|
|
|
|
|
|
|
|
| |
When `install_dir` is set, `install` defaults to true, so there’s no
need to set it manually. This fixes a Meson warning.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
Closes: #57
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Fix dbus leaks
See merge request GNOME/dconf!51
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change fixes the dbus-leak tests by dropping the cached
GDBusConnection objects references when the bus connection is closed.
The issue was introduced with recent changes made to GLib[1]
where invoking g_test_dbus_down() will fail after a
timeout if the GDBusConnection object for the session bus leaks.
Given g_test_dbus_down() will first close the connection before checking
for leaks unreffing the object when the connection is closed should fix
the issue.
[1] https://gitlab.gnome.org/GNOME/glib/merge_requests/963
Signed-off-by: Andre Moreira Magalhaes <andre@endlessm.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change should guarantee that the object is valid while in use.
The change is part of a series of changes to fix an issue
introduced with recent changes made to GLib[1] where invoking
g_test_dbus_down() will fail after a timeout if the GDBusConnection
object for the session bus leaks.
[1] https://gitlab.gnome.org/GNOME/glib/merge_requests/963
Signed-off-by: Andre Moreira Magalhaes <andre@endlessm.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change should guarantee that the object is valid while in use.
The change is part of a series of changes to fix an issue
introduced with recent changes made to GLib[1] where invoking
g_test_dbus_down() will fail after a timeout if the GDBusConnection
object for the session bus leaks.
[1] https://gitlab.gnome.org/GNOME/glib/merge_requests/963
Signed-off-by: Andre Moreira Magalhaes <andre@endlessm.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
With recent changes made to GLib[1] invoking g_test_dbus_down()
will fail after a timeout if the GDBusConnection object for the
session bus leaks.
Note that this new test will fail as the current code will leak a
cached GDBusConnection. Fixes will be added in follow-up patches.
[1] https://gitlab.gnome.org/GNOME/glib/merge_requests/963
Signed-off-by: Andre Moreira Magalhaes <andre@endlessm.com>
|
|\
| |
| |
| |
| | |
Increment version after 0.33.1 release
See merge request GNOME/dconf!50
|
| | |
|
|\ \
| |/
| |
| |
| | |
Update NEWS file for 0.33.1 release
See merge request GNOME/dconf!49
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
build: Use weak bindings in gvdb to fix linking with LLD
Closes #47
See merge request GNOME/dconf!28
|
| |
| |
| |
| |
| |
| |
| | |
Fix linking with LLD by using weak symbols in gvdb, and update dconf
code to make it compatible with gvdb upstream changes.
Fixes https://gitlab.gnome.org/GNOME/dconf/issues/47
|
| |\
|/ / |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
build: Use weak bindings in gvdb to fix linking with LLD
Closes dconf#47
See merge request GNOME/gvdb!2
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Since tests/dconf-mock-gvdb.c has functions conflicting with the real
gvdb and it is intended for the former to override the latter in tests,
we have to make functions in gvdb library have weak bindings instead of
the default strong bindings to avoid duplicate symbol errors.
Fixes https://gitlab.gnome.org/GNOME/dconf/issues/47
|
| |\
| | |
| | |
| | |
| | | |
Minor API fixes
See merge request GNOME/gvdb!1
|
| | |
| | |
| | |
| | |
| | |
| | | |
Suggested by Georges Basile Stavracas Neto.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It should not be unsigned. The type in the on-disk format is gint32, so
we need to return something at least as wide as that. However, we
should not expose the implementation detail that the on-disk format is
specifically gint32. Use a gsize, since that’s the normal type for array
lengths — but check that we’re not on a platform where (somehow) gsize
is smaller than gint32.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| |/
| |
| |
| | |
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| |
| |
| |
| |
| |
| | |
Factor out a common method to route completion of DBus methods through.
Helps: #29
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Prepare 0.32.0 release
See merge request GNOME/dconf!48
|