GNOME Bugzilla – Bug 559745
crash in Sudoku:
Last modified: 2008-11-07 14:13:33 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: Glider Icon Theme: gnome 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 --------------------- Building dependency tree... 0%Building dependency tree... 0%Building dependency tree... 50%Building dependency tree... 50%Building dependency tree... 77%Building dependency tree Reading state information... 0%Reading state information... 0%Reading state information... Done Reading package lists... 0%Reading package lists... 100%Reading package lists... Done Building dependency tree... 0%Building dependency tree... 0%Building dependency tree... 50%Building dependency tree... 50%Building dependency tree... 79%Building dependency tree Reading state information... 0%Reading state information... 0%Reading state information... Done kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1401d9b) kdeinit4: preparing to launch /usr/games/gnome-sudoku kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1401da2) Traceback (most recent call last):
+ Trace 209397
self.toggle_timing(False)
self.tot_time_complete += end_time - self.__absolute_start_time__
-------------------------------------------------- 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 557308 ***