GNOME Bugzilla – Bug 461852
crash in Chess:
Last modified: 2007-08-02 00:59:05 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.5 2007-07-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-8-386 #1 Thu Jul 12 15:31:33 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaCandy Icon Theme: Tangerine 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 (988 sec old) --------------------- A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" A handler is already registered for the path starting with path[0] = "org" ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 151631
start_game()
app = main.Application()
self.ui = UI(self)
self.controller = gtkui.GtkUI(self)
tooltip.tip_window.ensure_style()
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 459740 ***