GNOME Bugzilla – Bug 507711
crash in Chess: Iniciando la aplicación,...
Last modified: 2008-01-10 06:35:23 UTC
Version: 2.20.1 What were you doing when the application crashed? Iniciando la aplicación, sin más. 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 Tue Dec 18 08:02:57 UTC 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 (6743 sec old) --------------------- 25304] 18:59:19: initialized AGG buffer <0xb6aa0008>, 210000 bytes, 728x90, rowsize is 2184 bytes 25304] 18:59:19: ERROR: Unimplemented: FileAttributes tag in the SWF requests that network access is not granted to this movie (or application?). Anyway Gnash won't care; use white/black listing in yo 25304] 18:59:19: ERROR: Unimplemented: FIXME: tagtype = 83 25304] 18:59:19: ERROR: sprite::replace_display_object(): unknown cid = 5 25304] 18:59:20: ERROR: sprite::replace_display_object(): unknown cid = 4 25304] 18:59:20: ERROR: sprite::replace_display_object(): unknown cid = 5 25304] 18:59:20: ERROR: sprite::replace_display_object(): unknown cid = 4 25304] 18:59:20: ERROR: sprite::replace_display_object(): unknown cid = 5 25304] 18:59:20: ERROR: sprite::replace_display_object(): unknown cid = 4 25304] 18:59:20: ERROR: sprite::replace_display_object(): unknown cid = 5 25304] 18:59:20: ERROR: sprite::replace_display_object(): unknown cid = 4 25304] 18:59:20: ERROR: sprite::replace_display_object(): unknown cid = 5 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 184307
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 ***