telepathy-indicator crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| telepathy-indicator (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
open program
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-indicator 0.0.4-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelMo
Architecture: amd64
CrashCounter: 1
Date: Sat Aug 27 18:03:36 2011
ExecutablePath: /usr/bin/
ProcCmdline: telepathy-indicator
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x4019cf: mov (%rbx),%rdi
PC (0x004019cf) 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-08-26 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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 #830003, 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.