synaptic crashed with SIGSEGV

[HaruSiga77]

Precise -64-bit
Synaptic version: 0.75.5~exp6
My synaptic crashes every time I reload. I have 228 repositories, sometimes more. Maybe the it overloads somewhere?

This could be the work of some malware, it overloads the program that has sudo privileges and then injects code. Or the overload may cause a security flaw on machines installed with synaptic.

It'll work afterwards when I start it, with the updated database and can install/upgrade fine. I have even un-installed USC (ubuntu software center) from my computer to see if there was conflict between the programs. The crash still happens. This started since the ~exp versions came into mainstream. Synaptic worked before then on Precise.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synaptic 0.75.5~exp6
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 23 08:37:39 2012
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120205)
ProcCmdline: synaptic
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x44f774: mov 0x8(%rdx),%rax
 PC (0x0044f774) ok
 source "0x8(%rdx)" (0x693a736c6f6f7435) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
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 #936677, 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.