GNOME Bugzilla – Bug 536053
Crash sending a GGZ message when not connected
Last modified: 2008-07-29 18:12:19 UTC
Version: 2.22.1.1 What were you doing when the application crashed? sending a message Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.2 2008-05-27 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-17-generic #1 SMP Thu May 1 14:31:33 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Inverted Icon Theme: gnome 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 (3595 sec old) --------------------- fixme:richedit:fnTextSrv_TxSendMessage 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSetText 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSetText 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxGetNaturalSize 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSetText 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSetText 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxGetNaturalSize 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSetText 0x7f046ed0: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x7f046ed0: STUB ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 199326
self.feedback.sendChat(text)
self.decoder.client.sendChat(text)
self.mainChannel.send("<CHAT TYPE='normal'>%s</CHAT>\n" % xml.sax.saxutils.escape(text))
self.controller.send(data, isBinary)
nSent = self.socket.send(self.buffer)
*** Bug 538256 has been marked as a duplicate of this bug. ***
This a symptom of bug 540527. 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 540527 ***
*** This bug has been marked as a duplicate of 523818 ***
*** Bug 545235 has been marked as a duplicate of this bug. ***