synaptic crashed with SIGABRT in raise()

[Robert Ward]

Same as Bug #889565 Posting new as it is for new OS 12.04 Alpha1 it will probably be merged with 889565, but i thought you might want to see the addons. Did sudo synaptic, did straight synaptic without admin previlages to see if this was the issue. also did LC_ALL=C synaptic with same error

(synaptic:3076): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(synaptic:3076): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(synaptic:3076): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(synaptic:3076): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
terminate called after throwing an instance of 'std::out_of_range'
  what(): vector::_M_range_check
Aborted (core dumped)

good luck

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synaptic 0.75.2ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Nov 30 10:55:18 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111128)
ProcCmdline: synaptic
Signal: 6
SourcePackage: synaptic
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: synaptic crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #839219, 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.