empathy crashed with SIGSEGV in event_remove()

Bug #1150028 reported by 12th
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Empathy
Expired
Medium
empathy (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

opened the program and then the error

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: empathy 3.6.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
Uname: Linux 3.8.0-10-generic i686
ApportVersion: 2.9-0ubuntu2
Architecture: i386
Date: Wed Mar 6 19:44:53 2013
ExecutablePath: /usr/bin/empathy
InstallationDate: Installed on 2012-09-05 (181 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=ru_UA:ru
 LANG=ru_UA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x805f48a: mov 0xc(%eax),%esi
 PC (0x0805f48a) ok
 source "0xc(%eax)" (0x0001680c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic_va () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: Upgraded to raring on 2013-03-03 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
12th (nazarenko-artem) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 event_remove (event=0x8b044d8) at empathy-event-manager.c:185
 ffi_call_SYSV () at ../src/x86/sysv.S:65
 ffi_call (cif=cif@entry=0xbfe14b24, fn=fn@entry=0x8065fa0 <event_activated_cb>, rvalue=0xbfe14a90, avalue=avalue@entry=0xbfe14a50) at ../src/x86/ffi.c:413
 g_cclosure_marshal_generic_va (closure=closure@entry=0x88267e8, return_value=return_value@entry=0x0, instance=instance@entry=0x86fe068, args_list=args_list@entry=0xbfe14dbc "\260\350\241\b\330D\260\b\310Y\202\b\200\373\250\b\203'\247\266\200\373\250\bP", marshal_data=marshal_data@entry=0x0, n_params=n_params@entry=2, param_types=param_types@entry=0x88260b0) at /build/buildd/glib2.0-2.35.8/./gobject/gclosure.c:1550
 _g_closure_invoke_va (closure=0x88267e8, return_value=return_value@entry=0x0, instance=instance@entry=0x86fe068, args=args@entry=0xbfe14dbc "\260\350\241\b\330D\260\b\310Y\202\b\200\373\250\b\203'\247\266\200\373\250\bP", n_params=2, param_types=0x88260b0) at /build/buildd/glib2.0-2.35.8/./gobject/gclosure.c:840

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in empathy (Ubuntu):
importance: Undecided → Medium
summary: - empathy crashed with SIGSEGV in ffi_call_SYSV()
+ empathy crashed with SIGSEGV in event_remove()
tags: removed: need-i386-retrace
Revision history for this message
Bilal Shahid (s9iper1) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Bilal Shahid (s9iper1)
information type: Private → Public
Changed in empathy (Ubuntu):
status: New → Triaged
Revision history for this message
Bilal Shahid (s9iper1) wrote :

reporter needed your attention on upstream bug

Changed in empathy:
importance: Unknown → Medium
status: Unknown → Incomplete
Changed in empathy:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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