empathy-chat crashed with SIGSEGV in g_str_hash()

Bug #958827 reported by Борис Михаилов
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Don't know about which time it closed.
It was either while I was checking how would Ubuntu feel in my native language or when my router restarted.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.91-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
Uname: Linux 3.2.0-19-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sun Mar 18 22:32:33 2012
ExecutablePath: /usr/lib/empathy/empathy-chat
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/empathy/empathy-chat
SegvAnalysis:
 Segfault happened at: 0xb513ceea <g_str_hash+10>: movzbl (%ecx),%edx
 PC (0xb513ceea) ok
 source "(%ecx)" (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/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgee.so.2
 ?? () from /usr/lib/i386-linux-gnu/libgee.so.2
 gee_abstract_map_has_key () from /usr/lib/i386-linux-gnu/libgee.so.2
 gee_map_has_key () from /usr/lib/i386-linux-gnu/libgee.so.2
Title: empathy-chat crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to precise on 2012-03-14 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Борис Михаилов (boriseto) wrote :
description: updated
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 #917302, 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-i386-retrace
Revision history for this message
Борис Михаилов (boriseto) wrote :

Thank you for fixing it, but the other bug (that mine problem is duplicate of) is private, so I can't access it to check if I can provide any more info.

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.