telepathy-indicator crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-indicator (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
telepathy-indicator crashed with SIGSEGV
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-indicator 0.0.6-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Mon Sep 19 12:10:15 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: telepathy-indicator
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x804966a: mov (%ebx),%eax
PC (0x0804966a) ok
source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" 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-17 (1 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev root sambashare sudo tape video www-data
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.