After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 551546 - crash in Chess:
crash in Chess:
Status: RESOLVED DUPLICATE of bug 546694
Product: gnome-games-superseded
Classification: Deprecated
Component: glchess
2.20.x
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-09 17:49 UTC by davidrios
Modified: 2008-09-12 08:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description davidrios 2008-09-09 17:49:00 UTC
Version: 2.20.1

What were you doing when the application crashed?



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 ---------------------
  • File "/usr/lib/python2.5/site-packages/glchess/config.py", line 134 in set
    function(_GCONF_DIR + name, value)
GError: No database available to save your configuration: Unable to store a value at key '/apps/glchess/show_toolbar', as the configuration server has no writable databases. There are some common caus
Unable to make data directory /home/kiosk/.gnome2/glchess/: Permission denied
This is glChess 2.20.1
Loading AI configuration from /usr/share/glchess/ai.xml
Detected AI: GNU Chess at /usr/games/gnome-gnuchess
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/glchess/gtkui/gtkui.py", line 801, in _on_show_toolbar_clicked
    glchess.config.set('show_toolbar', value)
  • File "/usr/lib/python2.5/site-packages/glchess/config.py", line 134 in set
    function(_GCONF_DIR + name, value)
GError: No database available to save your configuration: Unable to store a value at key '/apps/glchess/show_toolbar', as the configuration server has no writable databases. There are some common caus
--------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/glchess/gtkui/gtkui.py", line 801, in _on_show_toolbar_clicked
    glchess.config.set('show_toolbar', value)
  • File "/usr/lib/python2.5/site-packages/glchess/config.py", line 134 in set
    function(_GCONF_DIR + name, value)
GError: No database available to save your configuration: Unable to store a value at key '/apps/glchess/show_toolbar', as the configuration server has no writable databases. There are some common caus
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
Comment 1 Gianluca Borello 2008-09-12 08:54:49 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 546694 ***