empathy crashed with SIGSEGV

[Joshua Lückers]

Binary package hint: empathy

Tried closing a chat window, result in a force close and this error afterwards.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.31.5.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Tue Aug 3 22:02:46 2010
Disassembly: => 0x7f7df3bf7a5f: Cannot access memory at address 0x7f7df3bf7a5f
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100630.2)
ProcCmdline: empathy
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7df3bf7a5f: Cannot access memory at address 0x7f7df3bf7a5f
 PC (0x7f7df3bf7a5f) ok
 SP (0x7fff467477d0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: empathy
Stacktrace:
 #0 0x00007f7df3bf7a5f in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff467477d0
StacktraceTop: ?? ()
Title: empathy crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00007f7df3bf7a5f in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff467477d0
StacktraceTop: ?? ()
ThreadStacktrace:

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Mohamed Amine Ilidrissi (ilidrissi.amine)]

Any news about this bug? Try to follow the instructions in the wiki page Pedro referred you to. 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!