telepathy-haze crashed with SIGSEGV in _purple_connection_destroy()

Bug #953180 reported by Rainer Rohde
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-haze (Ubuntu)
New
Undecided
Unassigned

Bug Description

Not sure what triggered this. At the time, I was trying to set up two accounts in Empathy: a "sametime" account and a "jabber" account

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-haze 0.5.0-1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 12 11:26:38 2012
ExecutablePath: /usr/lib/telepathy/telepathy-haze
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x411801: movl $0x1,0x28(%r12)
 PC (0x00411801) ok
 source "$0x1" ok
 destination "0x28(%r12)" (0xaaaaaaaaaaaaaad2) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
 ?? ()
 _purple_connection_destroy () from /usr/lib/libpurple.so.0
 purple_account_disconnect () from /usr/lib/libpurple.so.0
 ?? () from /usr/lib/libpurple.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: telepathy-haze crashed with SIGSEGV in _purple_connection_destroy()
UpgradeStatus: Upgraded to precise on 2012-03-02 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #938572, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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