empathy-av crashed with SIGSEGV in g_object_unref()

[John Dundas]

Binary package hint: empathy

When accepting a call Empathy-AV crashes

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.31.92-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 22 23:15:49 2010
ExecutablePath: /usr/lib/empathy/empathy-av
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/empathy/empathy-av
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_IE.utf8
SegvAnalysis:
 Segfault happened at: 0x7fcb36c1ba88 <g_object_unref+24>: cmpq $0x50,(%rax)
 PC (0x7fcb36c1ba88) ok
 source "$0x50" ok
 destination "(%rax)" (0xffffffff) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: empathy-av crashed with SIGSEGV in g_object_unref()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_object_unref (_object=0x1f6e0f0)
 empathy_call_handler_tf_channel_stream_created_cb (
 g_closure_invoke (closure=0x1e06280,
 signal_emit_unlocked_R (node=0x1ec46c0,
 g_signal_emit_valist (instance=0x1fa8010,

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace 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

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