GNOME Bugzilla – Bug 560842
crash in Sudoku: I clickt on resume sudok...
Last modified: 2008-11-14 20:34:06 UTC
Version: 2.24.1 What were you doing when the application crashed? I clickt on resume sudoku board and then i kickt game and statistik and then it cracht. Sry my bad english. Distribution: Ubuntu 8.10 (intrepid) Gnome Release: 2.24.1 2008-10-24 (Ubuntu) BugBuddy Version: 2.24.1 System: Linux 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Human-Clearlooks 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 (276967 sec old) --------------------- [11-11 15:05:41] Torbutton NOTE: Skipping no location: chrome://browser/content/browser.xul [11-11 15:05:43] Torbutton NOTE: Conflict between noncrashed and normal_exit states.. Assuming crash but no session restore.. [11-11 15:05:43] Torbutton NOTE: Crash detected, attempting recovery [11-11 15:05:43] Torbutton NOTE: Restoring cookie status [11-11 15:05:43] Torbutton NOTE: Loading non-tor jar after crash [11-11 15:05:44] Torbutton NOTE: Restoring tor state (npviewer.bin:3167): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed (npviewer.bin:3183): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed (npviewer.bin:3183): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 209787
self.toggle_timing(False)
self.tot_time_complete += end_time - self.__absolute_start_time__
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 557308 ***