update-apt-xapian-index crashed with ValueError in index(): invalid null reference in method 'Document_add_value', argument 3 of type 'std::string const &'

[Axel Wagner]

on lonovo thinkpad w500, core2duo 2,8Ghz, 4GB Ram, OCZ Apex SSD 256GB AHCImode, ATI Mobility FireGL V5700 512MB ATI RV635 radeondriver, 15.4" TFT display with 1920x1200 (WUXGA) resolution

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apt-xapian-index 0.43ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
Uname: Linux 3.0.0-6-generic x86_64
Architecture: amd64
Date: Sun Jul 24 01:13:41 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110723)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --batch-mode --force
ProcCwd: /
ProcEnviron:

PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--batch-mode', '--force']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with ValueError in index(): invalid null reference in method 'Document_add_value', argument 3 of type 'std::string const &'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Apport retracing service (apport)]

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