GNOME Bugzilla – Bug 559943
crash in Sudoku:
Last modified: 2008-11-09 00:00:52 UTC
Version: 2.24.1 What were you doing when the application crashed? 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:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Aurora Snow 1 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 (2789 sec old) --------------------- <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8a11c80)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8a11d98)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8834d20)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8834c08)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x883f520)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8a11d28)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x882b550)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8834d58)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8a11e50)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8834c40)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8834cb0)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8834c78)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x8a11cb8)> <gtk.gdk.Pixbuf object at 0x87713c4 (GdkPixbuf at 0x89d4488) ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 209491
self.sudoku_tracker.save_game(self)
jar = jar_game(ui)
ui.timer.finish_timing()
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 ***