empathy-av crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #649474 reported by Ari Torres
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: empathy

i tried to start a video call with a friend in windows 7 and it crashes

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Mon Sep 27 20:35:09 2010
ExecutablePath: /usr/lib/empathy/empathy-av
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100923)
ProcCmdline: /usr/lib/empathy/empathy-av
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb5d93bc3: cmpl $0x3,0xc(%eax)
 PC (0xb5d93bc3) ok
 source "$0x3" ok
 destination "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/libsoup-2.4.so.1
 g_cclosure_marshal_VOID__VOID () 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_cclosure_marshal_VOID__VOID()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ari Torres (kuvanito) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 io_disconnected (sock=0x8783770, msg=0x87884e8) at soup-message-io.c:216
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_regex_get_type () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_handler_find () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in empathy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Omer Akram (om26er) wrote :

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

Changed in empathy (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Omer Akram (om26er) wrote :

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!

Revision history for this message
Omer Akram (om26er) wrote :

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!

Changed in empathy (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
DarkRedman (darkredman-deactivatedaccount) wrote :

I've the same bug with Ubuntu Oneiric Ocelot beta 2 i386.

Changed in empathy (Ubuntu):
status: Invalid → New
Revision history for this message
Omer Akram (om26er) wrote :

please report a new bug for the issue you are facing. no point in opening an old closed bug. Code changes alot from release to release

Changed in empathy (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.