synaptic crashed with SIGSEGV in File()

[Smulle]

Synaptic crash when tryining to remove configuration for pakage that no longer is in repo
Used aptitude purge instead

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: synaptic 0.80~exp1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Wed Apr 3 09:00:50 2013
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2013-02-02 (59 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 SHELL=/bin/bash
 LANG=sv_SE.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f31a6e17994 <_ZN10pkgRecords6LookupERKN8pkgCache15VerFileIteratorE+20>: mov (%rax),%eax
 PC (0x7f31a6e17994) ok
 source "(%rax)" (0x7f37d03ca800) 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 (57 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 File (this=<optimized out>) at ../build/include/apt-pkg/cacheiterators.h:394
 pkgRecords::Lookup (this=0xe08800, Ver=...) at pkgrecords.cc:62
 RPackage::RPackage (this=0x1f56140, lister=<optimized out>, depcache=<optimized out>, records=<optimized out>, pkg=...) at rpackage.cc:82
 ?? ()
 ?? ()

[Launchpad Janitor (janitor)]

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

[Robert Roth (evfool)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.