abrt 1.0.0 detected a crash. backtrace ----- Summary: TB132d203f gconf_wrapper.py:65:get_value:GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus)) Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/gnome_sudoku/main.py", line 186, in <lambda> gobject.timeout_add_seconds(1, lambda *args: self.start_worker_thread() and True) File "/usr/lib/python2.6/site-packages/gnome_sudoku/main.py", line 387, in start_worker_thread if n_new_puzzles < self.gconf['minimum_number_of_new_puzzles']: File "/usr/lib/python2.6/site-packages/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 23, in __getitem__ return self.get_value (attr) File "/usr/lib/python2.6/site-packages/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 65, in get_value value = self._gconf_client.get (self._domain + key) GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus)) Local variables in innermost frame: self: <gnome_sudoku.gtk_goodies.gconf_wrapper.GConf instance at 0x2860ea8> key: minimum_number_of_new_puzzles cmdline: python /usr/bin/gnome-sudoku component: gnome-games executable: /usr/bin/gnome-sudoku kernel: 2.6.31.9-174.fc12.x86_64 package: gnome-games-1:2.28.1-1.fc12 uuid: 132d203f
Created attachment 380949 [details] File: backtrace
Package: gnome-games-1:2.30.1-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Sudoku was left open over night and crash reported in the morning. 2. 3. Comment ----- Interestingly although it reports a crash, sudoku still seem to be running OK
Package: gnome-games-1:2.28.2-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) Comment ----- The computer has been unused for a couple of days with gnome-sudoku opened in the background; the crash happened shortly after I started using the computer again - the game was still in the background
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.