telepathy-haze crashed with SIGSEGV in purple_account_request_close_with_account()

[Vitautas]

Binary package hint: telepathy-haze

wen close wine.

ProblemType: Crash
Architecture: amd64
Date: Tue Jul 28 21:26:07 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/telepathy/telepathy-haze
NonfreeKernelModules: nvidia
Package: telepathy-haze 0.3.1-1
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
 SHELL=/bin/bash
 LANG=ru_UA.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0x40e973 <time@plt+22499>: mov 0x48(%rax),%r12
 PC (0x0040e973) ok
 source "0x48(%rax)" (0x00000048) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libpurple.so.0
 purple_account_request_close_with_account ()
 _purple_connection_destroy ()
 purple_account_disconnect ()
Title: telepathy-haze crashed with SIGSEGV in purple_account_request_close_with_account()
Uname: Linux 2.6.31-4-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
purple_account_request_close_info (info=0x1a9c550)
purple_account_request_close_with_account (
_purple_connection_destroy (gc=0x19c9f50)
purple_account_disconnect (account=0x19f6bc0)

[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!