telepathy-gabble crashed with SIGSEGV in g_main_context_dispatch()

Bug #609393 reported by kyleabaker
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-gabble (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: telepathy-gabble

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu maverick (development branch)
Release: 10.10

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
telepathy-gabble:
  Installed: 0.9.15-1
  Candidate: 0.9.15-1
  Version table:
 *** 0.9.15-1 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
Not crash.

4) What happened instead
Crashed while trying to get Facebook chat enabled (by appending "@chat.facebook.com" to the username even though the account setup instructions don't mention this).

I disabled and reenabled the account to try to get it to work (which it finally did), but it crashed first.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: telepathy-gabble 0.9.15-1
ProcVersionSignature: Ubuntu 2.6.35-10.15-generic 2.6.35-rc5
Uname: Linux 2.6.35-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Jul 24 01:35:26 2010
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100602.2)
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x48f5d5: mov 0x20(%r12),%rdi
 PC (0x0048f5d5) ok
 source "0x20(%r12)" (0xaaaaaaaaaaaaaaca) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-gabble
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
 g_main_context_dispatch ()
Title: telepathy-gabble crashed with SIGSEGV in g_main_context_dispatch()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
kyleabaker (kyleabaker) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 send_stanza_cb (source=0xd71670, res=0xd9e360,
 wocky_xmpp_connection_write_cb (source=0xd78490,
 async_ready_callback_wrapper (
 g_socket_output_stream_write_ready (
 g_main_context_dispatch (context=0x9d19d0)

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 telepathy-gabble (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Omer Akram (om26er)
visibility: private → public
Revision history for this message
Vish (vish) 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 telepathy-gabble (Ubuntu):
status: New → Incomplete
Revision history for this message
Vish (vish) wrote :

Also, Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for telepathy-gabble (Ubuntu) because there has been no activity for 60 days.]

Changed in telepathy-gabble (Ubuntu):
status: Incomplete → Expired
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.