Hi,

 

I’ve managed to install most Gnome2 libraries, and some apps (notably Nautilus, which is for me the point to install the Gnome2 stuff in the first place!) and at the moment, it all goes without horrible dependancy-problems (some months ago there were still dependancies in plenty of Gnome 1.4 libs… apologies for not making time then, for reporting this)

 

Anyways, Nautilus runs, in a way, but I cannot change any settings. When trying the gconf-editor tool idem: cannot change any settings.

GConf complains for some reason that it is not able to find any writable databases.

 

What should I do to fix this?

 

The file /etc/gconf/2/path is default. I’ve created an empty directory ‘.gconf’ in my home directory, but don’t know what to fill it with.

 

The error I get from gconf2 is:

 

No database available to save your configuration: Unable to store a value at key '/apps/nautilus/desktop/volumes_visible', 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

No database available to save your configuration: Unable to store a value at key '/apps/gconf-editor/recents', 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

 

 

 

However, most problems do not apply: no stale lock-files; no NFS; only 1 gconf/ORBit running.

 

Is there a problem with locking? Should I somehow initialize my .gconf directory?

 

Any help appreciated!

 

Cheers,

 

--Tim