| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit f899264b0723f2d6099dedaeec0cfa1b76134e8e.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It seems like 1.13 is still a bit too cutting-edge for some (including
Debian wheezy and gnome-continuous).
Drop the dependency back to 1.11.2 and add back ACLOCAL_AMFLAGS (but
without ACLOCAL_FLAGS).
We can reevaluate after jessie is released.
|
|
|
|
|
|
| |
Since we dropped ACLOCAL_AMFLAGS in Makefile.am we should depend on automake
1.13 (since this is the version that supports using AC_CONFIG_MACRO_DIRS
directly).
|
|
|
|
|
|
|
| |
ACLOCAL_PATH has replaced this for some time now.
Bump automake dependency to 1.11.2 (this is the first automake that
knows about ACLOCAL_PATH).
|
|
|
|
| |
dconf is tested as working with Vala 0.18.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/gvdb/reader/corrupted/7% was failing when run with random seed
R02S2a7b9704dbb5ea704b0d724329af0fbf.
This is a fuzz test, and it turns out that this particular seed ended up
producing a file that was valid, but contained a self-referential table.
The testcase happily recursed though this table's subtable (itself) and
so on, until it ran out of stack space, causing a crash.
This bug would not impact realworld users of gvdb: these users only ever
recurse through tables a finite number of times. For dconf, subtables
are not used at all. For GSettings, each schema is a subtable, but from
within that subtable we only lookup values.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to the usual way async in dconf works, we can start getting replies
immediately (without returning to the mainloop). For this reason, we
must be sure that we do not modify the OutstandingWatch structure at any
point after we've issued even one call because the results may already
be coming in.
For this reason, we must add up the 'pending' count in a separate loop
run before we start making the calls.
https://bugzilla.gnome.org/show_bug.cgi?id=724929
|
| |
|
|
|
|
|
|
|
| |
file-db databases don't have an associated D-Bus bus type, so don't try
to install match rules for them.
https://bugzilla.gnome.org/show_bug.cgi?id=723553
|
| |
|
|
|
|
|
| |
Running find without path is not allowed on FreeBSD.
https://bugzilla.gnome.org/show_bug.cgi?id=723998
|
| |
|
|
|
|
|
| |
The man page was not updated when the compile command was
added. Fix that.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This allows manually compiling dconf databases outside of /etc. This is meant
to be used from the build system of projects that want to install dconf
databases (like gdm) to easily build the database in-tree.
https://bugzilla.gnome.org/show_bug.cgi?id=672303
|
|
|
|
|
|
|
| |
Add some more padding to 'dconf help' output to accomodate coming
additions.
https://bugzilla.gnome.org/show_bug.cgi?id=672303
|
|
|
|
|
|
|
|
| |
Instead of just ignoring errors when trying to parse keyfiles in a .d
directory, fail the compile outright. 'dconf update' will print the
error and attempt to move on to the next .d directory in line.
https://bugzilla.gnome.org/show_bug.cgi?id=672303
|
| |
|
|
|
|
|
|
|
|
| |
This is a new database type that is simply an absolute path to a gvdb
anywhere on the filesystem. Change notification is not supported.
This is intended to be used by things like gdm that wish to install
databases (somewhere in /usr) as part of the software.
|
|
|
|
|
| |
If we can't find a given profile in /etc then look for it in the
XDG_DATA_DIRS.
|
|
|
|
| |
Add a separator between Find and About
|
|
|
|
|
|
|
|
|
|
| |
We use -ldl in some of our testcases to mock out some system calls via
interposing, using dlsym() to chain up.
Make sure we only use this if we really need to. Many systems have
dlsym() in the C library and no -ldl.
https://bugzilla.gnome.org/show_bug.cgi?id=720072
|
| |
|
|
|
|
|
|
|
|
| |
Add a testcase to exercise the engine's processing of signals, including
its ability to reject bad data.
This testcase already found several issues with the engine which have
already been fixed in previous commits.
|
|
|
|
|
|
|
| |
Check incoming signals for non-sense before bubbling them up to higher
layers. This will avoid dconf APIs feeding invalid key names to
applications during change notifications in the case that we're fed
invalid data over D-Bus.
|
|
|
|
|
|
|
|
|
| |
Testing uncovered a case of a shadowed variable in the signal handling
code of the engine: the object path on which a signal arrived was being
shadowed by the 'path' variable used when deserialising the content of
the signal, causing the signal to fail to be delivered.
Rename the D-Bus path variable to 'object_path' to avoid the issue.
|
|
|
|
|
|
|
|
|
|
|
| |
Testing revealed that we were transmitting any change signal that came
in from the bus up to user code, even if the engine in question was not
interested in receiving the signal.
This is a problem in the case that two DConfClient objects exist for
different profiles. In that case, we'd get crosstalk between the
subscriptions that each client had made and change notifications would
appear in both clients even if the change only affected one.
|
|
|
|
|
| |
Wire through the writability notifications from the engine to the
correct signals on GSettingsBackend.
|
|
|
|
|
| |
Wire through WritabilityNotify signals from the engine. This has been
unimplemented for a very long time...
|
|
|
|
|
|
| |
Stop setting the DCONF_PROFILE environment variable while threads are
running. Leave only one case where we set it explicitly to check that
the variable itself is working correctly.
|
|
|
|
|
|
|
| |
Allow specifying a profile when calling dconf_engine_new(). This will
allow us to avoid setting/unsetting the DCONF_PROFILE environment in
testcases from contexts where other threads may be reading from the
environment.
|
|
|
|
| |
And fix some leaks in an existing test.
|
|
|
|
|
|
|
| |
Always call dconf_engine_call_handle_get_expected_type() from the mock
dbus backend, even if the handle is NULL. This matches the behaviour of
the real D-Bus backends and would have caught the bug fixed in the last
commit.
|
|
|
|
|
|
| |
We use a NULL handle in case we don't care about the return value. In that
case, we certainly don't care about the return type either, so use NULL for
expected_type in this case.
|
| |
|