GNOME Bugzilla – Bug 559850
crash in Sudoku: firing up an old game
Last modified: 2008-11-08 13:23:22 UTC
Version: 2.24.1 What were you doing when the application crashed? firing up an old game 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: DarkRoom Icon Theme: Crux 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 (17244 sec old) --------------------- ========================================================================== Forced audio codec: mad Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) FAAD: compressed input bitrate missing, assuming 128kbit/s! AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000) Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) decoder) ========================================================================== AO: [pulse] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 848 x 480 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 1.77:1 - prescaling to correct movie aspect. VO: [xv] 848x480 => 848x480 Planar YV12 [fs] A: 0.0 V: 0.0 A-V: 0.020 ct: 0.043 1/ 1 ??% ??% ??,?% 0 0 A: 0.0 V: 0.0 A-V: -0.021 ct: 0.041 2/ 2 ??% ??% ??,?% 0 0 A: 0.1 V: 0.1 A-V: 0.037 ct: 0.0 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 209445
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 ***