Ubuntu
empathy package

empathy crashed with SIGSEGV in g_main_context_dispatch()

Bug #423521 reported by Vish
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: empathy

Crash on starting empathy...
The program kept re-spawning! it just wouldnt stop re-spawning!
telepathy-haze kept restarting again and again on its own,
I tired to stop it but , it didnt matter how many times i ran $killall telepathy-haze
Had to shutdown! to stop telepathy.

This happened when i was connecting to a yahoo account.
the contacts said that they could see me login and logout.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 417990aadff2335cd485c57bb06c8968
CheckboxSystem: 5484a8dd99f006173bd2ac53fa4837c2
CrashCounter: 1
Date: Thu Sep 3 10:20:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
Package: empathy 2.27.91.1-2ubuntu2
ProcCmdline: empathy
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x4f7ce8: movl $0x0,0x4(%eax)
 PC (0x004f7ce8) ok
 source "$0x0" ok
 destination "0x4(%eax)" (0xaaaaaaae) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
Title: empathy crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

See original description
Revision history for this message
Vish (vish) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /usr/lib/libtelepathy-glib.so.0
g_idle_dispatch (source=0x9605b40, callback=0xaaaaaaaa,
IA__g_main_context_dispatch (context=0x9271d58)
g_main_context_iterate (context=0x9271d58,
IA__g_main_loop_run (loop=0x95fe138)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in empathy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Vish (vish)
description: updated
visibility: private → public
Marco Rodrigues (gothicx)
Changed in empathy (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) 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: Confirmed → Incomplete
Revision history for this message
Vish (vish) wrote :

This bug seems fixed , I'm no longer facing this problem.

Anyone facing the problem can re-open the bug and provide the backtrace as requested in the previous comment

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

Other bug subscribers

Remote bug watches

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