empathy assert failure: empathy:ERROR:empathy-tp-chat.c:1391:empathy_tp_chat_acknowledge_message: assertion failed: (m != NULL)

[A. Leon]

Binary package hint: empathy

I am worried that users are going to be defaulted to a chat client that crashes so very often. In this occasion, I'm filling a weird bug that send empathy to the crash. I was chatting with a bud on the gtalk protocol I think its XMPP.

Steps to reproduce:

1. Start Empathy
2. Add Account out of gtalk (XMPP)
3. Add a Buddy and start chatting
4. Close chat window
5. Go take a hike
6. Come back
7. Chat again with that bud.
8. And crash happens

Hope I can gave you all stuff needed for the bug confirmation.

Please fix :(

ProblemType: Crash
Architecture: i386
AssertionMessage: empathy:ERROR:empathy-tp-chat.c:1391:empathy_tp_chat_acknowledge_message: assertion failed: (m != NULL)
CrashCounter: 1
Date: Wed Oct 21 16:45:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
Package: empathy 2.28.1-1ubuntu1
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
Signal: 6
SourcePackage: empathy
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 g_assertion_message () from /lib/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/libglib-2.0.so.0
Title: empathy assert failure: empathy:ERROR:empathy-tp-chat.c:1391:empathy_tp_chat_acknowledge_message: assertion failed: (m != NULL)
Uname: Linux 2.6.31-14-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #453398, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.