Bug 577342 – crash in Sudoku: Launching the game

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 577342 - crash in Sudoku: Launching the game


Summary:	crash in Sudoku: Launching the game


Status:	RESOLVED DUPLICATE of bug 444693

Product:	gnome-games-superseded
Classification:	Deprecated
Component:	gnome-sudoku
Version:	2.22.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Games maintainers
QA Contact:	GNOME Games maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-03-30 19:20 UTC by restaurant_ace
Modified:	2009-03-30 19:25 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description restaurant_ace 2009-03-30 19:20:06 UTC

Version: 2.22.3

What were you doing when the application crashed?
Launching the game


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.3 2008-07-09 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

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 ---------------------
    main.start_game()

+ Trace 214016

File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 1039 in start_game
```
u = UI()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 176 in __init__
```
self.setup_gui()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 231 in setup_gui
```
self.initialize_prefs()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 505 in initialize_prefs
```
self.gconf[k]=v
```
File "/var/lib/python-support/python2.5/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 30 in __setitem__
```
self.set_value (key, val)
```
File "/var/lib/python-support/python2.5/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 83 in set_value
```
apply (func, (self._domain + key, value))
```

GError: No database available to save your configuration: Unable to store a value at key '/apps/gnome-sudoku/show_tracker', as the configuration server has no writable databases. There are some common

--------------------------------------------------
Traceback (most recent call last):
  File "/usr/games/gnome-sudoku", line 55, in <module>
    start_game()
  File "/var/lib/python-support/python2.5/gnome_sudoku/gnome_sudoku.py", line 21, in start_game
    main.start_game()

+ Trace 214016

File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 1039 in start_game
```
u = UI()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 176 in __init__
```
self.setup_gui()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 231 in setup_gui
```
self.initialize_prefs()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 505 in initialize_prefs
```
self.gconf[k]=v
```
File "/var/lib/python-support/python2.5/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 30 in __setitem__
```
self.set_value (key, val)
```
File "/var/lib/python-support/python2.5/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 83 in set_value
```
apply (func, (self._domain + key, value))
```

 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 2009-03-30 19:25: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 444693 ***