GNOME Bugzilla – Bug 486118
crash in Chess: just starting
Last modified: 2007-10-13 07:52:43 UTC
Version: 2.20.0.1 What were you doing when the application crashed? just starting Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango 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 (6 sec old) --------------------- ERROR: could not get file id for /usr/share//applications/ooo-writer.desktop - unable to continue indexing this file ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19 ERROR: CreateService uri is /usr/share//applications/ooo-impress.desktop ERROR: could not get file id for /usr/share//applications/ooo-impress.desktop - unable to continue indexing this file ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19 ERROR: CreateService uri is /usr/share//applications/ooo-draw.desktop ERROR: could not get file id for /usr/share//applications/ooo-draw.desktop - unable to continue indexing this file ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19 ERROR: CreateService uri is /usr/share//applications/ooo-base.desktop ERROR: could not get file id for /usr/share//applications/ooo-base.desktop - unable to continue indexing this file Traceback (most recent call last):
+ Trace 169803
from glchess.glchess import start_game
-------------------------------------------------- Traceback (most recent call last):
Thank you for reporting this bug. It looks like this is the same issue as bug 412690.
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 the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 412690 ***