update-apt-xapian-index crashed with SIGSEGV in pkgCacheGenerator::pkgCacheGenerator()

[mohaemed amine ben mabrouk]

problem in ubuntu start

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apt-xapian-index 0.44ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Feb 25 23:29:50 2012
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: This
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb743b681: movdqu %xmm0,(%esi)
 PC (0xb743b681) ok
 source "%xmm0" ok
 destination "(%esi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: apt-xapian-index
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 pkgCacheGenerator::pkgCacheGenerator(DynamicMMap*, OpProgress*) () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
 pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
 pkgCacheFile::BuildCaches(OpProgress*, bool) () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
 pkgCacheFile::Open(OpProgress*, bool) () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
Title: update-apt-xapian-index crashed with SIGSEGV in pkgCacheGenerator::pkgCacheGenerator()
UpgradeStatus: Upgraded to precise on 2012-02-13 (13 days ago)
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 #913962, 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.