telepathy-haze crashed with SIGSEGV in purple_conversation_destroy()

Bug #618064 reported by Felix Yan
40
This bug affects 4 people
Affects Status Importance Assigned to Milestone
telepathy-haze (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: telepathy-haze

telepathy-haze crashed with SIGSEGV in purple_conversation_destroy()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: telepathy-haze 0.4.0-1
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Aug 14 15:16:48 2010
ExecutablePath: /usr/lib/telepathy/telepathy-haze
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x4153a2: mov (%rdx),%rdi
 PC (0x004153a2) ok
 source "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
 ?? ()
 purple_conversation_destroy ()
 purple_accounts_delete ()
 ?? ()
 g_object_unref ()
Title: telepathy-haze crashed with SIGSEGV in purple_conversation_destroy()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Felix Yan (felixonmars) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 haze_destroy_conversation (conv=0x2436db0)
 purple_conversation_destroy ()
 purple_accounts_delete ()
 haze_connection_finalize (object=0x1fa4020)
 g_object_get_qdata (object=0x7f5d51a66f80,

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-haze (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, is anybody still getting this issue using the current version? Could you describe how to trigger it?

visibility: private → public
Changed in telepathy-haze (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in telepathy-haze (Ubuntu):
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.