telepathy-haze crashed with SIGSEGV in purple_connection_error_reason()

[ramesh]

Binary package hint: telepathy-haze

Not logging empathy

Ramesh

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/telepathy/telepathy-haze
Package: telepathy-haze 0.2.1-1
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_IN
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
 ?? ()
 purple_connection_error_reason ()
 ?? () from /usr/lib/purple-2/libyahoo.so
 ?? () from /usr/lib/purple-2/libyahoo.so
 ?? ()
Title: telepathy-haze crashed with SIGSEGV in purple_connection_error_reason()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:haze_report_disconnect_reason (gc=0x9e71450,
purple_connection_error_reason (gc=0x9e71450,
yahoo_packet_process (gc=0x9e71450,
yahoo_pending (data=0x9e71450, source=11,
purple_glib_io_invoke (source=0x9e71298,

[prata (prata)]

This appears to be semi-random. I opened account management screen (Edit > Accounts) and selected my twitter profile to make a change. As soon as I clicked in the password field for the twitter account the screen vanished and I was presented with a crash report. I have attempted to reproduce, but it seems to happen without warning and regardless of which account is selected (and sadly doesn't happen every time I open the accounts window). It did cause my yahoo account to sign off and then back on if that is of any importance. All other accounts remained functional.

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!