mysql-workbench-bin crashed with SIGABRT at launch

[Carl Ganz]

Can't launch mysql-workbench with Bionic Beaver. Based on previous bug reports I tried removing ~/.mysql but I am still unable to open mysql-workbench.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mysql-workbench 6.3.8+dfsg-1build3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Fri Apr 6 10:56:05 2018
ExecutablePath: /usr/lib/mysql-workbench/mysql-workbench-bin
InstallationDate: Installed on 2017-11-29 (127 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/mysql-workbench/mysql-workbench-bin
Signal: 6
SourcePackage: mysql-workbench
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 Glib::FileError::throw_func(_GError*) () at /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
Title: mysql-workbench-bin crashed with SIGABRT
UpgradeStatus: Upgraded to bionic on 2018-03-23 (13 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 #1375992, 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.