telepathy-indicator crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| telepathy-indicator (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
Who knows?
Not me.
Apport, maybe.
(Got this prompt at login, could have happened at previous shutdown)
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: telepathy-indicator 0.3.1+14.
ProcVersionSign
Uname: Linux 3.18.0-9-generic x86_64
ApportVersion: 2.15.1-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 27 16:25:26 2015
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2012-10-07 (842 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
ProcCmdline: telepathy-indicator
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x403e12: mov 0x8(%rax),%rcx
PC (0x00403e12) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-indicator
StacktraceTop:
()
__libc_start_main (main=0x403bb0, argc=1, argv=0x7fffe9a6
()
Title: telepathy-indicator crashed with SIGSEGV
UpgradeStatus: Upgraded to vivid on 2013-05-07 (631 days ago)
UserGroups:
| Iain Lane (laney) wrote | #1 |
| Apport retracing service (apport) wrote | #2 |
| Apport retracing service (apport) wrote StacktraceSource.txt | #3 |
| Apport retracing service (apport) wrote ThreadStacktrace.txt | #4 |
| Changed in telepathy-indicator (Ubuntu): | |
| importance: | Undecided → Medium |
| tags: | removed: need-amd64-retrace |
| information type: | Private → Public |
Stacktrace:
#0 0x0000000000403e12 in setup (loop=<optimized out>) at indicator-
tp_am = 0x0
error = 0x0
#1 main (argc=1, argv=0x7fffe9a6
loop = 0x2521dc0
StacktraceTop:
setup (loop=<optimized out>) at indicator-
main (argc=1, argv=0x7fffe9a6