synaptic crashed with SIGSEGV in pkgRecords::Lookup()

[Salih EMIN]

How to reproduce:
1) Open Synaptic Package manager
2) Click on "Not installed (residual config)"
3) Right click on a package

Result:
Crash

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: synaptic 0.80~exp1
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Thu Apr 11 04:00:33 2013
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2012-09-07 (215 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f68ca694994 <_ZN10pkgRecords6LookupERKN8pkgCache15VerFileIteratorE+20>: mov (%rax),%eax
 PC (0x7f68ca694994) ok
 source "(%rax)" (0x7f6ef4468000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 pkgRecords::Lookup(pkgCache::VerFileIterator const&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV in pkgRecords::Lookup()
UpgradeStatus: Upgraded to raring on 2013-04-10 (0 days ago)
UserGroups:

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[papukaija (papukaija)]

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 1097532, 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. Feel free to continue to report any other bugs you may find.

Ps. The bug 1097532 has a valgrind log attached so I made that bug a master bug even if this bug is a newer one.