On 12/28/09 10:18 PM, Albert Lee wrote: > > Er that's quite a huge leap of logic, suspend/resume doesn't have much to > do with application behaviour. > > You had stray gconfd-2 processes running as root which means you > accidentally ran something earlier as root, you should have killed those > and fixed any directories they may have touched. > > If you read gconftool-2 --help: > --direct Bypass server, and access > the configuration database directly. Requires that gconfd is not running. > > It's possible that a running gconfd-2 process was preventing --direct from > working; the is is also hinted in the long error message you got. >
gconf is a nightmre on my machine. Now, the error messages are always displayed, even after rebooting... gdm at ultra20:~$ gconftool-2 --direct --config-source xml:readwrite:/var/lib/gdm/.gconf.mandatory -t bool -s /apps/gdm/simple-greeter/disable_user_list false (gconftool-2:871): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Error setting value: Unable to store a value at key '/apps/gdm/simple-greeter/disable_user_list', 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 noticed these errors, don't know if it is relevant: Dec 29 12:55:00 ultra20 console-kit-daemon[2992]: [ID 702911 daemon.crit] GLib-GObject-CRITICAL: file gobject.c: line 2384: assertion `G_IS_OBJECT (object)' failed Dec 29 12:55:00 ultra20 last message repeated 1 time Dec 29 12:55:00 ultra20 gdm-binary[4406]: [ID 702911 daemon.warning] WARNING: Unable lookup numeric info: non-recoverable name resolution failure Dec 29 12:55:02 ultra20 console-kit-daemon[2992]: [ID 702911 daemon.warning] GLib-GObject-WARNING: g_object_set_property: construct property "seat-id" for object `CkSession' can't be set after construction Dec 29 12:55:02 ultra20 gnome-session[4449]: [ID 702911 daemon.warning] WARNING: IceListenForConnections returned 2 non-local listeners: inet/ultra20:46177,inet6/ultra20:40239 henry at ultra20:~# svcs \*gcon\* has anybody succeeded in configuring gdm? thanks, gerard
