GNOME Bugzilla – Bug 520101
crash in Chess: Doing updates in a virtu...
Last modified: 2008-03-03 23:35:34 UTC
Version: 2.20.1 What were you doing when the application crashed? Doing updates in a virtual machine 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 Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 (20 sec old) --------------------- ERROR: could not get file id for /usr/share//applications/services.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/shares.desktop ERROR: could not get file id for /usr/share//applications/shares.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/time.desktop ERROR: could not get file id for /usr/share//applications/time.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/users.desktop ERROR: could not get file id for /usr/share//applications/users.desktop - unable to continue indexing this file Traceback (most recent call last):
+ Trace 191155
from glchess.glchess import start_game
-------------------------------------------------- Traceback (most recent call last):
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 ***