Ubuntu
telepathy-gabble package

telepathy-gabble crashed with SIGSEGV in lm_connection_unregister_message_handler()

Bug #483297 reported by Removed by request on 2009-11-15

20

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	telepathy-gabble (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: telepathy-gabble

it just crashed, while program was running backround.

ProblemType: Crash
Architecture: i386
Date: Sun Nov 15 23:42:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
Package: telepathy-gabble 0.8.7-1
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
Segfault happened at: 0xf23cbf <lm_connection_unregister_message_handler+63>: mov (%ecx),%edi
PC (0x00f23cbf) ok
source "(%ecx)" (0x000000e9) not located in a known VMA region (needed readable region)!
destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-gabble
StacktraceTop:
lm_connection_unregister_message_handler ()
?? () from /usr/lib/libloudmouth-1.so.0
?? () from /usr/lib/libloudmouth-1.so.0
lm_connection_unref () from /usr/lib/libloudmouth-1.so.0
?? ()
Title: telepathy-gabble crashed with SIGSEGV in lm_connection_unregister_message_handler()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout dip fuse lpadmin plugdev sambashare

Tags:

Revision history for this message

Removed by request (removed67550) wrote on 2009-11-15:

#1

Dependencies.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (7.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (767 bytes, text/plain; charset="utf-8")
Registers.txt Edit (522 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-16: Stacktrace.txt (retraced)

#2

Stacktrace.txt (retraced) Edit (1.5 KiB, text/plain)

StacktraceTop:lm_connection_unregister_message_handler (connection=0x8ace4b8,
lm_sasl_free (sasl=0x8aba1b0) at lm-sasl.c:810
connection_do_close (connection=0x8ab8980)
lm_connection_unref (connection=0x8ab8980)
_unref_lm_connection (data=0x8ab8980) at connection.c:865

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-16: ThreadStacktrace.txt (retraced)

#3

ThreadStacktrace.txt (retraced) Edit (1.6 KiB, text/plain)

Changed in telepathy-gabble (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Revision history for this message

Omer Akram (om26er) wrote on 2010-08-30:

#4

thanks for the bug report. is this still an issue?

Changed in telepathy-gabble (Ubuntu):
status:	New → Incomplete

Revision history for this message

Omer Akram (om26er) wrote on 2010-10-07:

#5

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.

Omer Akram (om26er) on 2010-10-07

visibility:

private → public

Revision history for this message

Vish (vish) wrote on 2010-10-13:

#6

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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".

Changed in telepathy-gabble (Ubuntu):
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #485870

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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