https://bugzilla.novell.com/show_bug.cgi?id=705409 https://bugzilla.novell.com/show_bug.cgi?id=705409#c2 Casual J. Programmer <casualprogrammer@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|casualprogrammer@opensuse.o | |rg | --- Comment #2 from Casual J. Programmer <casualprogrammer@opensuse.org> 2011-07-18 09:48:30 UTC ---
Were you running gconf-editor as root?
No
Was this after an upgrade, and did you restart your session?
Both yes The messages received in the terminal have changed since. Just now I get: 8> gconf-editor GConf Error: Configuration server couldn't be contacted: D-BUS error: Unable to store a value at key '/apps/gdm/simple-greeter/banner_message_enable', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf The message is thrown at me when I try to change an entry to default, not at the start of gconf-editor. :~> cat /etc/gconf/2/path # This file stores the addresses of config sources for GConf # When a value is stored or requested, the sources are scanned from top to # bottom, and the first one to have a value for the key (or the first one # to be writeable) is used to load/store the data. # See the GConf manual for details # Look first in systemwide mandatory settings directory xml:readonly:/etc/gconf/gconf.xml.mandatory # To read in any mandatory settings that the Sys Admin may have created # prior to a desktop system upgrade. The SysAdmin can stick read-only system # wide sources in this file. include /etc/gconf/2/local-mandatory.path # Sabayon mandatory path include "$(HOME)/.gconf.path.mandatory" # Now see where users want us to look - basically the user can stick arbitrary # sources in a ~/.gconf.path file and they're inserted here include "$(HOME)/.gconf.path" # Give users a default storage location, ~/.gconf xml:readwrite:$(HOME)/.gconf # Then look at the systemwide customizations xml:readonly:/etc/gconf/gconf.xml.defaults # Sabayon optional path include "$(HOME)/.gconf.path.defaults" # To read in any defaults settings that the Sys Admin may have created # prior to a desktop system upgrade. The SysAdmin can stick default values # system-wide in this file. include /etc/gconf/2/local-defaults.path # Then check vendor preferences xml:readonly:/etc/gconf/gconf.xml.vendor # And finally look at the defaults defined by installed schemas xml:readonly:/etc/gconf/gconf.xml.schemas -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.