GNOME Bugzilla – Bug 467126
crash in Chess: Opening it
Last modified: 2007-08-16 17:59:32 UTC
Version: 2.19.90 What were you doing when the application crashed? Opening it 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: Mist 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 (950 sec old) --------------------- Opening audio decoder: [libmad] libmad mpeg audio decoder AUDIO: 24000 Hz, 2 ch, s16le, 56.0 kbit/7.29% (ratio: 7000->96000) Selected audio codec: [mad] afm: libmad (libMAD MPEG layer 1-2-3) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 512 x 384 (preferred colorspace: Planar YV12) Could not find matching colorspace - retrying with -vf scale... Opening video filter: [scale] VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. SwScaler: using unscaled yuv420p -> rgb32 special converter VO: [gl] 512x384 => 512x384 BGRA A: 0.1 V: 0.0 A-V: 0.075 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.1 V: 0.0 A-V: 0.058 ct: 0.000 2/ 2 ??% ??% ??,?% 0 0 A: 0.1 V: 0.1 A-V: 0.044 ct: 0.0 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 155511
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 ***