apt_check.py crashed with SIGSEGV in pkgCacheGenerator::MergeList()

[UGN]

Binary package hint: update-notifier

when i update system via synaptic i see this bug

ProblemType: Crash
Architecture: i386
Date: Wed Jan 20 09:14:42 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100107)
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-common 0.92
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 PATH=(custom, user)
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x32b775: pcmpeqb (%esi),%xmm0
 PC (0x0032b775) ok
 source "(%esi)" (0xe4291120) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 pkgCacheGenerator::MergeList(pkgCacheGenerator::ListParser&, pkgCache::VerIterator*) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
 debStatusIndex::Merge(pkgCacheGenerator&, OpProgress&) const
 ?? () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
 pkgMakeStatusCache(pkgSourceList&, OpProgress&, MMap**, bool) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
Tags: lucid
Title: apt_check.py crashed with SIGSEGV in pkgCacheGenerator::MergeList()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __strlen_sse2 () from /lib/tls/i686/cmov/libc.so.6
 pkgCacheGenerator::MergeList (this=0xbfe87368,
 debStatusIndex::Merge (this=0x8f99c58, Gen=@0xbfe87368,
 BuildCache (Gen=<value optimized out>,
 pkgMakeStatusCache (List=@0xbfe874c4, Progress=@0xbfe87560,

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 340479, so it 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.