synaptic crashed with SIGSEGV in Section()

[Jani Uusitalo]

Seems to happen every time I update package listings now, right after all downloads have finished. It doesn't prevent upgrading however, because if I restart Synaptic after the crash, all the listing updates have been applied and downloading the upgraded packages doesn't crash Synaptic.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synaptic 0.75.5~exp6
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Wed Feb 15 10:07:44 2012
DuplicateOf: https://bugs.launchpad.net/bugs/929315
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/sbin/synaptic
SegvAnalysis:
 Segfault happened at: 0x44f774 <RPackage::section()+4>: mov 0x8(%rdx),%rax
 PC (0x0044f774) ok
 source "0x8(%rdx)" (0x0000001c) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: synaptic
Stacktrace:
 #0 Section (this=<optimized out>) at /usr/include/apt-pkg/cacheiterators.h:158
 No locals.
 #1 RPackage::section (this=0x2487cc0, this@entry=<error reading variable: Cannot access memory at address 0x7fff477ca578>) at rpackage.cc:111
         s = 0x4a0530 "\240\aH"
StacktraceTop:
 Section (this=<optimized out>) at /usr/include/apt-pkg/cacheiterators.h:158
 RPackage::section (this=0x2487cc0, this@entry=<error reading variable: Cannot access memory at address 0x7fff477ca578>) at rpackage.cc:111
ThreadStacktrace:
 .
 Thread 2 (LWP 3235):
 #0 0x00007fea6462adc3 in ?? ()
 No symbol table info available.
 .
Title: synaptic crashed with SIGSEGV in Section()
UpgradeStatus: Upgraded to precise on 2012-02-14 (1 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 #929315, 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.