telepathy-indicator crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-indicator (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Launching empathy on a freshly updated Oneiric Beta, caused this error
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-indicator 0.0.6-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 30 08:18:55 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: telepathy-indicator
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x401baa: mov (%rbx),%rdi
PC (0x00401baa) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-indicator
StacktraceTop:
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: telepathy-indicator crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-05 (25 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #851881, 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.