indicator-session-service crashed with SIGSEGV in _start()

[Barry Warsaw]

Upon dist-upgrade in vivid channel

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: indicator-session 12.10.5+15.04.20150228-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
Date: Tue Mar 10 11:45:59 2015
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
InstallationDate: Installed on 2013-12-06 (458 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x41243a <_start+1290>: movzbl (%r8),%eax
 PC (0x0041243a) ok
 source "(%r8)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-session
Stacktrace:
 #0 0x000000000041243a in _start ()
 No symbol table info available.
StacktraceTop: _start ()
Title: indicator-session-service crashed with SIGSEGV in _start()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

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 #1382654, 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.