summaryrefslogtreecommitdiffstats
path: root/meta/recipes-gnome/gnome/gconf
AgeCommit message (Collapse)Author
2018-04-13gconf: fix saving of settings when config folder doesnt existJaewon Lee
In some circumstances, gconf isn't able to save configurations because ~/.config folder aka root_dir doesn't exist. For example when saving settings using matchbox-appearance, the following error is shown: GConf Error: Configuration server couldn't be contacted: D-BUS error: Can't overwrite existing read-only value: Value for `/desktop/poky/interface/font_name' set in a read-only source at the front of your configuration path This issue was not seen before because ~/.config directory is shared between several packages and one of those packages usually creates it by the time gconf wants to use it. This patch makes sure that gconf creates the .config directory if it doesn't exist, along with the gconf directory inside it. [YOCTO #12632] Signed-off-by: Alejandro Hernandez <alejandr@xilinx.com> Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-04-22gconf: silence some spurious errorsRoss Burton
The postinstalls were producing errors like this: (gconftool-2.real:10095): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead These are harmless but distracting, so take a patch from upstream to silence them. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-02-28gconf: update to 3.2.6Saul Wold
remove automake patch as it been fixed upstream Signed-off-by: Saul Wold <sgw@linux.intel.com>