Ubuntu
telepathy-haze package

telepathy-haze crashed with SIGSEGV in purple_connection_set_state()

Bug #946751 reported by Aleksiy on 2012-03-05

18

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	telepathy-haze (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

telepathy-haze crashed with SIGSEGV in purple_connection_set_state()

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-haze 0.5.0-1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
CasperVersion: 1.305
Date: Sun Mar 4 19:34:51 2012
ExecutablePath: /usr/lib/telepathy/telepathy-haze
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x80564da: movl $0x1,0x14(%edi)
PC (0x080564da) ok
source "$0x1" ok
destination "0x14(%edi)" (0xaaaaaabe) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
?? ()
purple_connection_set_state () from /usr/lib/libpurple.so.0
_purple_connection_destroy () from /usr/lib/libpurple.so.0
purple_account_disconnect () from /usr/lib/libpurple.so.0
?? () from /usr/lib/libpurple.so.0
Title: telepathy-haze crashed with SIGSEGV in purple_connection_set_state()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Aleksiy (aleksiyi) wrote on 2012-03-05:

#1

Dependencies.txt Edit (3.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (585 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (24.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (790 bytes, text/plain; charset="utf-8")
Registers.txt Edit (487 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")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-05:

#2

StacktraceTop:
?? ()
purple_connection_set_state (state=PURPLE_DISCONNECTED, gc=0x85e22c0) at /build/buildd/pidgin-2.10.1/./libpurple/connection.c:402
purple_connection_set_state (gc=0x85e22c0, state=PURPLE_DISCONNECTED) at /build/buildd/pidgin-2.10.1/./libpurple/connection.c:323
_purple_connection_destroy (gc=0x85e22c0) at /build/buildd/pidgin-2.10.1/./libpurple/connection.c:287
purple_account_disconnect (account=0x8759bf0) at /build/buildd/pidgin-2.10.1/./libpurple/account.c:1284

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-05: Stacktrace.txt

#3

Stacktrace.txt Edit (3.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-05: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (3.6 KiB, text/plain)

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-03-14:

#5

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in telepathy-haze (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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