Bug 546694 – Chess breaks when gconf is readonly

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 546694 - Chess breaks when gconf is readonly


Summary:	Chess breaks when gconf is readonly


Status:	RESOLVED FIXED

Product:	gnome-games-superseded
Classification:	Deprecated
Component:	glchess
Version:	2.23.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GNOME Games maintainers
QA Contact:	GNOME Games maintainers

URL:
Whiteboard:

Duplicates:	547212 551546 551827 552703 554626 555422 555707 556539 557296 557891 558167 558268 558953 560943 561715 562355 564743 569697 570865 573809 574398 579728 580920 (view as bug list)
Depends on:
Blocks:	444693

Reported:	2008-08-07 00:00 UTC by Thomas Andersen
Modified:	2009-04-30 23:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description Thomas Andersen 2008-08-07 00:00:13 UTC

When running with gconf in read-only mode chess (v. 2.23.6) crashes on startup.

To reproduce edit /etc/gconf/2/path and change the line:
"xml:readwrite:$(HOME)/.gconf"
to:
"xml:readonly:$(HOME)/.gconf"

Then run "gconftool-2 --shutdown" to restart the gconfd.

When chess can handle that we should move sudoku over to also use the config.py file there. I'll make a separate bug about that.


Here's the stacktrace from the crash:

Traceback (most recent call last):

+ Trace 204754

File "/var/lib/python-support/python2.5/glchess/gtkui/dialogs.py", line 671 in _on_show_history_activate
```
glchess.config.set('show_history', widget.get_active())
```
File "/var/lib/python-support/python2.5/glchess/config.py", line 145 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_history', 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

Comment 1 Thomas Andersen 2008-08-10 23:37:16 UTC

*** Bug 547212 has been marked as a duplicate of this bug. ***

Comment 2 Robert Ancell 2008-08-14 14:13:54 UTC

Fixed in head (was catching the exception in the wrong place)
http://svn.gnome.org/viewvc/gnome-games?view=revision&revision=7818

Comment 3 Gianluca Borello 2008-09-12 08:54:42 UTC

*** Bug 551827 has been marked as a duplicate of this bug. ***

Comment 4 Gianluca Borello 2008-09-12 08:54:49 UTC

*** Bug 551546 has been marked as a duplicate of this bug. ***

Comment 5 Robert Ancell 2008-09-21 11:52:35 UTC

*** Bug 552703 has been marked as a duplicate of this bug. ***

Comment 6 Robert Ancell 2008-10-08 03:14:05 UTC

*** Bug 555422 has been marked as a duplicate of this bug. ***

Comment 7 Robert Ancell 2008-10-08 03:14:35 UTC

*** Bug 554626 has been marked as a duplicate of this bug. ***

Comment 8 Gianluca Borello 2008-10-10 08:37:21 UTC

*** Bug 555707 has been marked as a duplicate of this bug. ***

Comment 9 Robert Ancell 2008-10-18 06:24:05 UTC

*** Bug 556539 has been marked as a duplicate of this bug. ***

Comment 10 Robert Ancell 2008-10-27 06:48:15 UTC

*** Bug 557296 has been marked as a duplicate of this bug. ***

Comment 11 Robert Ancell 2008-10-27 06:48:20 UTC

*** Bug 557891 has been marked as a duplicate of this bug. ***

Comment 12 Susana 2008-10-28 22:16:34 UTC

*** Bug 558167 has been marked as a duplicate of this bug. ***

Comment 13 Susana 2008-10-28 22:22:21 UTC

*** Bug 558268 has been marked as a duplicate of this bug. ***

Comment 14 Susana 2008-11-02 21:54:37 UTC

*** Bug 558953 has been marked as a duplicate of this bug. ***

Comment 15 André Klapper 2008-11-16 19:18:20 UTC

*** Bug 560943 has been marked as a duplicate of this bug. ***

Comment 16 palfrey 2008-11-26 18:18:00 UTC

*** Bug 562355 has been marked as a duplicate of this bug. ***

Comment 17 Robert Ancell 2008-11-27 01:14:10 UTC

*** Bug 561715 has been marked as a duplicate of this bug. ***

Comment 18 palfrey 2008-12-16 15:30:16 UTC

*** Bug 564743 has been marked as a duplicate of this bug. ***

Comment 19 palfrey 2009-01-29 18:11:42 UTC

*** Bug 569697 has been marked as a duplicate of this bug. ***

Comment 20 Fabio Durán Verdugo 2009-02-07 15:15:37 UTC

*** Bug 570865 has been marked as a duplicate of this bug. ***

Comment 21 Fabio Durán Verdugo 2009-03-02 20:37:09 UTC

*** Bug 573809 has been marked as a duplicate of this bug. ***

Comment 22 Fabio Durán Verdugo 2009-03-06 17:13:19 UTC

*** Bug 574398 has been marked as a duplicate of this bug. ***

Comment 23 palfrey 2009-04-21 15:34:58 UTC

*** Bug 579728 has been marked as a duplicate of this bug. ***

Comment 24 Fabio Durán Verdugo 2009-04-30 23:06:00 UTC

*** Bug 580920 has been marked as a duplicate of this bug. ***