gaim crashed while connect with msn

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Happens quite randomly. Got a backtrace though:
Program received signal SIGSEGV, Segmentation fault.
0xb654a9e3 in msn_message_gen_payload () from /usr/lib/purple-2/libmsn.so
(gdb) bt
#0 0xb654a9e3 in msn_message_gen_payload () from /usr/lib/purple-2/libmsn.so
#1 0xb655a931 in ?? () from /usr/lib/purple-2/libmsn.so
#2 0x00000060 in ?? ()
#3 0xbfb61208 in ?? ()
#4 0x080fe988 in ?? ()
#5 0x00000008 in ?? ()
#6 0x00000096 in ?? ()
#7 0xb65651e0 in ?? () from /usr/lib/purple-2/libmsn.so
#8 0xbfb61218 in ?? ()
#9 0xb655b04c in msn_switchboard_send_msg () from /usr/lib/purple-2/libmsn.so
#10 0xb65582f1 in msn_slplink_send_msg () from /usr/lib/purple-2/libmsn.so
#11 0xb655843a in msn_slplink_send_msgpart () from /usr/lib/purple-2/libmsn.so
#12 0xb6558c19 in ?? () from /usr/lib/purple-2/libmsn.so
#13 0x095165c0 in ?? ()
#14 0x096f2188 in ?? ()
#15 0xbfb61788 in ?? ()
#16 0xb7745de9 in g_slice_free_chain_with_offset () from /usr/lib/libglib-2.0.so.0
#17 0xb655a29a in ?? () from /usr/lib/purple-2/libmsn.so
#18 0x097b8c90 in ?? ()
#19 0x096f2188 in ?? ()
#20 0xb76ba140 in ?? () from /lib/tls/i686/cmov/libc.so.6
#21 0x09868b50 in ?? ()
#22 0x08125730 in ?? ()
---Type <return> to continue, or q <return> to quit---
#23 0x09493510 in ?? ()
#24 0xb76c4541 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
#25 0xb655c88b in ?? () from /usr/lib/purple-2/libmsn.so
#26 0x097ff880 in ?? ()
#27 0x097e4f60 in ?? ()
#28 0xbfb617e8 in ?? ()
#29 0xb7728bb7 in ?? () from /usr/lib/libglib-2.0.so.0
#30 0x09868b50 in ?? ()
#31 0xb77b621c in ?? () from /usr/lib/libglib-2.0.so.0
#32 0xbfb617e8 in ?? ()
#33 0xb77298d6 in ?? () from /usr/lib/libglib-2.0.so.0
#34 0x097e4f60 in ?? ()
#35 0xb76c58ac in __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) info reg
eax 0x988df58 159965016
ecx 0x988df58 159965016
edx 0x60 96
ebx 0xb65651e0 -1235856928
esp 0xbfb61130 0xbfb61130
ebp 0xbfb611c8 0xbfb611c8
esi 0x95165c0 156329408
edi 0x60 96
eip 0xb654a9e3 0xb654a9e3 <msn_message_gen_payload+67>
eflags 0x10202 [ IF RF ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51

Reopend, got a stack-backtrace of gaim in gutsy. version: 1:2.2.1-1ubuntu4.1

Do you happen to have a crash report regarding gaim in your '/var/crash' directory? If so that would be a bit more useful. If you do you can submit a new bug report by just double clicking on that file in Nautilus. Thanks again!

Yes there is one, but it refuses to submit a report since libcairo2 is not current. I update and will try to do it next time gaim crashes.

It isn't clear to me why this bug should be fix committed, a comment would have been helpful when changing the status, so I am setting it back to Incomplete.

is this still an issue? can you try the same with hardy?

It did not happen recently again. As the error was quite random, I do not know if it’s gone forever, though.

it appears as by the users response, i am marking appropriately