summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Add morph file to disable man pagesbaserock/gnomeJavier Jardón2014-07-201-0/+5
|
* Updated Greek translationTom Tryfonidis2014-07-091-10/+11
|
* Updated Swedish translationAnders Jonsson2014-04-301-29/+55
|
* Updated Indonesian translationDirgita2014-04-221-8/+10
|
* Updated POTFILES.in and POTFILES.skipPiotr Drąg2014-04-092-7/+7
|
* dconf-editor: Make DBus-activatableMatthias Clasen2014-04-083-3/+14
| | | | | | | | | This commit installs a service file, renames the desktop file to follow the bus name, and adds the DBusActivatable key to the desktop file, following https://wiki.gnome.org/HowDoI/DBusApplicationLaunching https://bugzilla.gnome.org/show_bug.cgi?id=727862
* service: Don't hang during shutdownMarek Kasik2014-04-041-1/+6
| | | | | | | Remember whether a signal was signalled to dconf-service so we don't call g_application_release() more than once. https://bugzilla.gnome.org/show_bug.cgi?id=727549
* doap: update URLsPiotr Drąg2014-03-301-8/+11
|
* dconf 0.20.00.20.0Ryan Lortie2014-03-242-1/+6
|
* Updated Czech translationMarek Černocký2014-03-201-1/+1
|
* dconf 0.19.920.19.92Ryan Lortie2014-03-172-1/+10
|
* build: drop back to automake 1.11.2Ryan Lortie2014-03-132-1/+3
| | | | | | | | | | 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.
* Bump automake dependency to 1.13Ryan Lortie2014-03-131-1/+1
| | | | | | 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).
* Stop using ACLOCAL_FLAGSRyan Lortie2014-03-133-4/+2
| | | | | | | 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).
* configure: depend on a released ValaRyan Lortie2014-03-121-1/+1
| | | | dconf is tested as working with Vala 0.18.
* dconf 0.19.910.19.91Ryan Lortie2014-03-032-1/+8
|
* gvdb test: avoid infinite recursionRyan Lortie2014-02-211-4/+8
| | | | | | | | | | | | | | | | /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.
* engine: fix race in match rule addingRyan Lortie2014-02-211-7/+11
| | | | | | | | | | | | | 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
* dconf 0.19.900.19.90Ryan Lortie2014-02-172-1/+19
|
* file-db: don't install match rules on no busRyan Lortie2014-02-111-8/+15
| | | | | | | 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
* Updated Ukrainian translationDaniel Korostil2014-02-101-25/+35
|
* Fix "make clean" problem on FreeBSDTing-Wei Lan2014-02-101-2/+2
| | | | | Running find without path is not allowed on FreeBSD. https://bugzilla.gnome.org/show_bug.cgi?id=723998
* dconf compile: always write little endianRyan Lortie2014-02-052-2/+11
|
* Update dconf(1)Matthias Clasen2014-01-311-0/+17
| | | | | The man page was not updated when the compile command was added. Fix that.
* Updated FSF's addressDaniel Mustieles2014-01-3143-129/+43
|
* Updated Aragonese translationJorge Pérez Pérez2014-01-311-16/+16
|
* editor: Provide appdataRobert Ancell2014-01-233-0/+21
|
* Fix a mistake in Chinese simplified translation that may block compilingWylmer Wang2014-01-181-2/+2
|
* dconf 0.19.30.19.3Ryan Lortie2014-01-132-1/+32
|
* dconf(1): add 'dconf compile' commandRyan Lortie2014-01-132-0/+29
| | | | | | | | 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
* dconf(1): some whitespace changesRyan Lortie2014-01-131-16/+16
| | | | | | | Add some more padding to 'dconf help' output to accomodate coming additions. https://bugzilla.gnome.org/show_bug.cgi?id=672303
* dconf update: change error handlingRyan Lortie2014-01-131-52/+44
| | | | | | | | 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
* tests: test the new file-db engine sourceRyan Lortie2014-01-131-1/+58
|
* engine: add support for 'file-db'Ryan Lortie2014-01-135-7/+92
| | | | | | | | 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.
* profiles: allow profiles in XDG_DATA_DIRSRyan Lortie2014-01-131-11/+55
| | | | | If we can't find a given profile in /etc then look for it in the XDG_DATA_DIRS.
* editor: app menu: standardize Help/About/QuitMichael Catanzaro2013-12-291-0/+2
| | | | Add a separator between Find and About
* portability: only link to -ldl if neededRyan Lortie2013-12-082-2/+5
| | | | | | | | | | 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
* tests: add testcase for dconf_engine_sync()Ryan Lortie2013-11-281-0/+103
|
* tests: test engine processing of signalsRyan Lortie2013-11-271-0/+112
| | | | | | | | 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.
* engine: reject junk signalsRyan Lortie2013-11-271-0/+36
| | | | | | | 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.
* engine: fix a case of variable shadowingRyan Lortie2013-11-271-3/+3
| | | | | | | | | 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.
* engine: filter change signals properlyRyan Lortie2013-11-271-2/+23
| | | | | | | | | | | 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.
* gsettings: handle writability notificationRyan Lortie2013-11-271-0/+15
| | | | | Wire through the writability notifications from the engine to the correct signals on GSettingsBackend.
* engine: add support for WritabilityNotifyRyan Lortie2013-11-266-4/+28
| | | | | Wire through WritabilityNotify signals from the engine. This has been unimplemented for a very long time...
* tests: stop setting environment variablesRyan Lortie2013-11-261-16/+5
| | | | | | 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.
* engine: add 'profile' argument to constructorRyan Lortie2013-11-266-13/+15
| | | | | | | 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.
* tests: add more engine testsRyan Lortie2013-11-251-5/+176
| | | | And fix some leaks in an existing test.
* tests: always use expected_type from mock dbusRyan Lortie2013-11-251-2/+11
| | | | | | | 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.
* engine: allow NULL handleRyan Lortie2013-11-251-1/+4
| | | | | | 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.
* tests: fix ridiculous typoRyan Lortie2013-11-253-6/+6
|
View Lorry Controller Status