GNOME Bugzilla – Bug 498070
crash in Chess: i was updating the syste...
Last modified: 2007-11-19 04:26:09 UTC
Version: 2.20.1 What were you doing when the application crashed? i was updating the system Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 (8436 sec old) --------------------- Forced audio codec: mad Trying to force audio codec driver family ffmpeg... Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 2 ch, s16le, 32.0 kbit/2.27% (ratio: 4005->176400) Selected audio codec: [ffcook] afm: ffmpeg (FFmpeg COOK audio decoder) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 320 x 240 (preferred colorspace: Planar I420) VDec: using Planar I420 as output csp (no 0) Movie-Aspect is 1.33:1 - prescaling to correct movie aspect. VO: [x11] 320x240 => 320x240 Planar I420 SwScaler: using unscaled yuv420p -> rgb32 special converter A: 0.1 V: 0.0 A-V: 0.068 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.1 V: 0.0 A-V: 0.075 ct: 0.003 2/ 2 ??% ??% ??,?% 0 0 A: 0.1 V: 0.1 A-V: -0.004 ct: -0.0 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 178623
from glchess.glchess import start_game
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 412690 ***