GNOME Bugzilla – Bug 587784
crash in Chess: game on-line
Last modified: 2009-07-05 05:45:48 UTC
Version: 2.24.3 What were you doing when the application crashed? game on-line Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.25-170.2.72.fc10.i686 #1 SMP Sun Jun 21 19:03:24 EDT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora 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 --------------------- self._cont_handler.endElement(name)
+ Trace 216323
self.handler.endElement(name)
self.parser.endElement(name)
method()
self.decoder.feedback.onConnected()
language = os.environ['LANG']
-------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/glchess/gtkui/gtkui.py", line 315, in __readData return self.feedback.onReadFileDescriptor(fd) File "/usr/lib/python2.5/site-packages/glchess/main.py", line 354, in onReadFileDescriptor result = handler.read() File "/usr/lib/python2.5/site-packages/glchess/network.py", line 154, in read self.feedback.registerIncomingData(data) File "/usr/lib/python2.5/site-packages/glchess/ggz/client.py", line 178, in registerIncomingData data = self.decoder.feed(data) File "/usr/lib/python2.5/site-packages/glchess/ggz/protocol.py", line 654, in feed self.xparser.feed(chunk) File "/usr/lib/python2.5/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "/usr/lib/python2.5/site-packages/_xmlplus/sax/expatreader.py", line 314, in end_element self._cont_handler.endElement(name)
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 572943 ***