https://bugzilla.novell.com/show_bug.cgi?id=439075 Summary: gconf-editor: can't set settings as "default". Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: robin.listas@telefonica.net QAContact: qa@suse.de Found By: --- OS: 11.1 Beta 3 - not in the list above Right-click on a setting in gconf-editor, for instance, "sleep_computer_ac = 0" under "/apps/gnome-power-manager/timeout/sleep_computer_ac", try "set as default" or "set as mandatory". I get a box with a "forbidden" icon: The application "gconf-editor" attempted to change an aspect of your configuration that your system administrator or operating system vendor does not allow you to change. Some of the settings you have selected may not take effect, or may not be restored next time you use the application. Details: No database available to save your configuration: Unable to store a value at key '/apps/gnome-power-manager/timeout/sleep_computer_ac', 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 I can not test this as root, due to Bug 439074. However, a friend has tried via graphical login as root and said she can not, either, she gets the same error. I can not currently try login as root myself because that means closing my only current session as user (ie, kill firefox with bugzilla opened). -- 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.