GNOME Bugzilla – Bug 523426
crash in Chess: i run chess
Last modified: 2008-03-20 12:05:48 UTC
Version: 2.20.1 What were you doing when the application crashed? i run chess 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 Feb 12 07:42:25 UTC 2008 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 (1256 sec old) --------------------- // gg_recv_packet(0f) 0f 00 00 00 40 00 00 00 92 54 9a 00 04 57 69 e8 a9 0e 06 2a ff 00 4e 69 65 20 6d 61 20 74 6f 20 6a 61 6b 20 7a 20 6e 75 64 f3 77 20 70 69 73 61 e6 20 6b 6c 61 77 69 61 74 75 72 6 // gg_watch_fd_connected() received a status change ** gg_event_free(0x85b9548); ** gg_send_message(0x8522628, 8, 1485071, 0x865d168) ** gg_send_message_richtext(0x8522628, 8, 1485071, 0x865d168, (nil), 0); ** gg_send_packet(0x8522628, 0x0b, ...) // gg_send_packet(0x0b) 0b 00 00 00 27 00 00 00 0f a9 16 00 11 88 76 01 08 00 00 00 64 6f 73 74 61 b3 65 6d 20 6d 61 6e 64 61 74 20 64 7a 69 73 69 61 6a 20 3b 5d 00 ** gg_watch_fd(0x8522628); // gg_watch_fd() GG_STATE_CONNECTED ** gg_watch_fd_connected(0x8522628, 0x8592540); ** gg_recv_packet(0x8522628); // gg_recv_packet() header recv(9,0xbffcf854,8) = 8 // gg_recv_packet() body recv(9,0x85c1e50,12) = 12 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 192879
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 ***