Ubuntu
apt-xapian-index package

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

Bug #814644 reported by Nizar Kerkeni on 2011-07-22

This bug report is a duplicate of: Bug #810552: update-apt-xapian-index crashed with ValueError in index(): invalid null reference in method 'Document_add_value', argument 3 of type 'std::string const &'. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	apt-xapian-index (Ubuntu)	New	Undecided	Unassigned

Bug Description

crashed after logging to unity session.

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: Fri Jul 22 14:44:41 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--update', '-q']
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: Upgraded to oneiric on 2011-07-08 (14 days ago)
UserGroups:

Tags:

Revision history for this message

Nizar Kerkeni (nizarus) wrote on 2011-07-22:

Traceback.txt Edit (781 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-08-24: This bug is a duplicate

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