synaptic crashed with SIGSEGV in pkgRecords::Lookup()

[Igor Zubarev]

Crash when I move to point Kernel and try manually to select all 3.5 kernels.
When I select deleted 3.5 kernel with existing configs, instant crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: synaptic 0.80~exp1
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CurrentDmesg.txt:
 [ 6891.233873] show_signal_msg: 33 callbacks suppressed
 [ 6891.233887] synaptic[29702]: segfault at 7f662037a000 ip 00007f5fee7b3634 sp 00007fff152ef4c0 error 4 in libapt-pkg.so.4.12.0[7f5fee744000+11b000]
Date: Thu Feb 7 00:23:50 2013
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2012-09-11 (148 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
MarkForUpload: True
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f5fee7b3634 <_ZN10pkgRecords6LookupERKN8pkgCache15VerFileIteratorE+20>: mov (%rax),%eax
 PC (0x7f5fee7b3634) ok
 source "(%rax)" (0x7f662037a000) 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-02-04 (2 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 #1097532, 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.