empathy-chat crashed with SIGSEGV in g_str_hash()

Bug #961603 reported by Elvis Ciocoiu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Simply trying to select an open conversation tab and empathy grayed and finally crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.92-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-19.31-generic 3.2.12
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Wed Mar 21 22:22:44 2012
ExecutablePath: /usr/lib/empathy/empathy-chat
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901)
ProcCmdline: /usr/lib/empathy/empathy-chat
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fad412c18a0 <g_str_hash>: movzbl (%rdi),%edx
 PC (0x7fad412c18a0) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgee.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libgee.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libgee.so.2
 ?? () from /usr/lib/libfolks-telepathy.so.25
Title: empathy-chat crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to precise on 2012-03-19 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Elvis Ciocoiu (elvis-ciocoiu-w) wrote :
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 #961420, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.