empathy crashed with SIGSEGV in tp_connection_manager_protocol_get_param()

[Nicolas DERIVE]

Binary package hint: empathy

Reconnecting in ssl after an uncrypted login.

ProblemType: Crash
Architecture: i386
Date: Wed Sep 2 21:01:40 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
NonfreeKernelModules: nvidia
Package: empathy 2.27.91.1-2ubuntu2
ProcCmdline: empathy
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x51407e <tp_connection_manager_protocol_get_param+30>: mov (%eax),%eax
 PC (0x0051407e) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 tp_connection_manager_protocol_get_param ()
 tp_connection_manager_protocol_has_param ()
 tp_connection_manager_protocol_can_register ()
 ?? ()
 ?? ()
Title: empathy crashed with SIGSEGV in tp_connection_manager_protocol_get_param()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:tp_connection_manager_protocol_get_param ()
tp_connection_manager_protocol_has_param ()
tp_connection_manager_protocol_can_register ()
accounts_dialog_protocol_changed_cb (widget=0xa02ac08,
accounts_dialog_button_add_clicked_cb (button=0x97688f8,

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[Sebastien Bacher (seb128)]

could be the same issue than bug #446311, does anybody still get the issue with the karmic update?

[Omer Akram (om26er)]

We have been wondering if this is still an issue for you. this bug was reported against the development release of empathy so there is a probability that this would have been fixed with the updates.

[Anthony Hook (anthonyhook)]

I am not having an issue with this anymore.

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