GNOME Bugzilla – Bug 467515
crash in Chess:
Last modified: 2007-08-17 02:38:54 UTC
Version: 2.19.90 What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-08-14 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: Tango 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 (35718 sec old) --------------------- Opening audio decoder: [liba52] AC3 decoding with liba52 Using SSE optimized IMDCT transform Using MMX optimized resampler AUDIO: 48000 Hz, 2 ch, s16le, 192.0 kbit/12.50% (ratio: 24000->192000) Selected audio codec: [a52] afm: liba52 (AC3-liba52) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 640 x 480 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 1.33:1 - prescaling to correct movie aspect. VO: [x11] 640x480 => 640x480 Planar YV12 SwScaler: using unscaled yuv420p -> rgb32 special converter A: 0.0 V: 0.0 A-V: 0.028 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.1 V: 0.0 A-V: 0.018 ct: 0.002 2/ 2 ??% ??% ??,?% 0 0 A: 0.1 V: 0.1 A-V: 0.015 ct: 0.0 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 155811
start_game()
app = main.Application()
self.ui = UI(self)
self.controller = gtkui.GtkUI(self)
self.defaultViewController = self.notebook.setDefault(None)
self.defaultView = chessview.GtkView(self.ui, '', feedback)
tooltip.tip_window.ensure_style()
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 459740 ***