empathy crashed with SIGSEGV in gtk_tree_store_insert_with_values()

[Eugene Crosser]

Binary package hint: empathy

Happened when attempting to "Link" two jabber accounts. Which does not have any effect, BTW. Crash only happened after several attempts to link.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.31.90-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 5 19:42:29 2010
ExecutablePath: /usr/bin/empathy
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: empathy
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fddf504a6da <vfprintf+154>: callq 0x7fddf508d060 <strchrnul>
 PC (0x7fddf504a6da) ok
 source "0x7fddf508d060" (0x7fddf508d060) ok
 destination "(%rsp)" (0x7fffc35d0fa0) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 gtk_tree_store_insert_with_values ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: empathy crashed with SIGSEGV in gtk_tree_store_insert_with_values()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Brian Curtis (bcurtiswx)]

Thanks for your bug report and helping to make Ubuntu better. I think this crash is due to an outdated version of libfolks and empathy. Please make sure to run 'sudo apt-get update; sudo apt-get upgrade' and check to see if you can reproduce this issue.

[Omer Akram (om26er)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

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