update-apt-xapian-index crashed with SIGSEGV in PyObject_GetAttr()

[verem]

ubuntu 14 10

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: apt-xapian-index 0.46ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
Date: Mon Aug 4 13:31:55 2014
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationDate: Installed on 2014-08-03 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --batch-mode --force
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f2cfe8969ef: mov (%r12),%eax
 PC (0x7f2cfe8969ef) ok
 source "(%r12)" (0x7f317a4414e0) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: apt-xapian-index
StacktraceTop:
 ?? () from /usr/lib/python2.7/dist-packages/apt_pkg.so
 ?? ()
 PyObject_GetAttr ()
 PyEval_EvalFrameEx ()
 ?? ()
Title: update-apt-xapian-index crashed with SIGSEGV in PyObject_GetAttr()
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 #1220013, 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.