empathy-chat crashed with SIGSEGV in g_str_hash()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| empathy (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I don't exactly know what caused it. I had my empathy windows open (connected to Google Talk) off to the side and I noticed it went disconnected, then the window crashed. It came back with no issue.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.92-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 21 15:22:22 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f8c454748a0 <g_str_hash>: movzbl (%rdi),%edx
PC (0x7f8c454748a0) 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_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: empathy-chat crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to precise on 2012-03-19 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Sean Stoops (brutimus) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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.