empathy crashed with SIGSEGV

[YannUbuntu]

Binary package hint: empathy

Happened when trying a video call with a Ubuntu10.04 Empathy Jabber user.

I have Ubuntu10.04 EmpathyPPA

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.1.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
CheckboxSubmission: 7bf4676ac92338d1d362954586c33b04
CheckboxSystem: bd9978d0ff03d4f55482fc24a6cdac35
Date: Sun Jun 27 21:25:43 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100328)
ProcCmdline: empathy
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/gstreamer-0.10/libgstvideo4linux2.so
 ?? () from /usr/lib/libgstbase-0.10.so.0
 ?? () from /usr/lib/libgstbase-0.10.so.0
 ?? () from /usr/lib/libgstbase-0.10.so.0
Title: empathy crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare src

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 gst_push_src_create (bsrc=0x998e208,
 gst_base_src_get_range (src=<value optimized out>,
 gst_base_src_loop (pad=0x99a00d0) at gstbasesrc.c:2334
 gst_task_func (task=0x9892de0) at gsttask.c:238

[Brian Curtis (bcurtiswx)]

Thanks for your bug report and helping to make Ubuntu better. This seems to be a problem with the v4l plugin with gstreamer and I have switched the associated package. Since you were using a PPA version of empathy we can not verify this bug. Could you please try the non PPA version and let us know if this is still an issue?

[Vallery Lancey (muscovy)]

Are you sure gstreamer0.10 was effected?

[Pedro Villavicencio (pedro)]

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