GNOME Bugzilla – Bug 560943
crash in Chess: sitting in the chair
Last modified: 2008-11-16 19:18:20 UTC
Version: 2.20.1 What were you doing when the application crashed? sitting in the chair Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: EdubuntuColors Icon Theme: gartoon Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- --------------------------------- kbuildsycoca running... Launched ok, pid = 5317 ** (epiphany-browser:5319): WARNING **: Unable to connect to session bus: Failed to connect to socket /tmp/dbus-p6vEQY3EXN: Connection refused kbuildsycoca running... ICE default IO error handler doing an exit(), pid = 5314, errno = 0 Traceback (most recent call last):
+ Trace 209826
glchess.config.set('show_toolbar', value)
function(_GCONF_DIR + name, value)
-------------------------------------------------- Traceback (most recent call last):
es 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
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in version 2.24.0. You may want to ask your distribution for a software upgrade. *** This bug has been marked as a duplicate of 546694 ***