After updating and restarting my system, this crash showed up right after the login. It happened repeatedly after updates during the last few days. It does not have any obvious effect on the running system though.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: apt-xapian-index 0.45ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 9 11:01:51 2013
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationDate: Installed on 2013-09-28 (11 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index -q -u
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/sh
SegvAnalysis:
Segfault happened at: 0x7fba2cc28b8e: mov (%rax),%eax
PC (0x7fba2cc28b8e) ok
source "(%rax)" (0x7fbed9c53c50) 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:
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.