mysql-workbench-bin crashed with SIGSEGV in sigc::internal::typed_slot_rep<sigc::bind_functor<-1, sigc::pointer_functor1<boost::function<bool()

[Cliff Carson]

Error occurred when closing Admin tab and returning to Home.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: mysql-workbench 5.2.40+dfsg-2
ProcVersionSignature: Ubuntu 3.7.0-6.14-generic 3.7.0
Uname: Linux 3.7.0-6-generic x86_64
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
Date: Thu Mar 7 11:31:31 2013
ExecutablePath: /usr/lib/mysql-workbench/bin/mysql-workbench-bin
InstallationDate: Installed on 2012-12-14 (83 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
MarkForUpload: True
ProcCmdline: /usr/lib/mysql-workbench/bin/mysql-workbench-bin
SegvAnalysis:
 Segfault happened at: 0x7f324cddddb0: mov 0x98(%r12),%eax
 PC (0x7f324cddddb0) ok
 source "0x98(%r12)" (0x00000098) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mysql-workbench
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
 sigc::internal::typed_slot_rep<sigc::bind_functor<-1, sigc::pointer_functor1<boost::function<bool ()>, bool>, boost::function<bool ()>, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil> >::destroy(void*) () from /usr/lib/mysql-workbench/libmforms.so.0
 sigc::slot_base::~slot_base() () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
Title: mysql-workbench-bin crashed with SIGSEGV in sigc::internal::typed_slot_rep<sigc::bind_functor<-1, sigc::pointer_functor1<boost::function<bool()
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 #1063705, 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.