Bug #89083 mysql-workbench-community-6.3.10-1 creates a segment fauly in CentOS 7
Submitted: 31 Dec 2017 18:24 Modified: 2 Jan 2018 15:25
Reporter: Roy Dew Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.3.10-1 OS:CentOS (Version 7.4.1708 64 bit)
Assigned to: CPU Architecture:Any
Tags: GtkDialog, segmentation fault

[31 Dec 2017 18:24] Roy Dew
The workbench will not load and fails with the following response:

Dec 31 12:21:56 workstation-01 journal: GtkDialog mapped without a transient parent. This is discouraged.
Dec 31 12:21:56 workstation-01 abrt-hook-ccpp: Process 3730 (mysql-workbench-bin) of user 0 killed by SIGSEGV - dumping core
Dec 31 12:21:57 workstation-01 mysql-workbench.desktop: *** Segmentation fault

How to repeat:
Run mysql-workbench from the bash shell command line or Gnome menu.
[31 Dec 2017 19:37] MySQL Verification Team
Thank you for the bug report. Duplicate of https://bugs.mysql.com/bug.php?id=87380
[1 Jan 2018 1:19] Kevin Taylor
This is how I resolved the issue on Centos 7.

# Used Version 6.3.8.
# Versions 6.2.5 - 6.3.4 did not show the results grid
# Version 6.3.9 and 6.3.10 will not open.
wget http://repo.mysql.com/yum/mysql-tools-community/el/7/x86_64/mysql-workbench-community-6.3....
yum install rpm mysql-workbench-community-6.3.8-1.el7.x86_64.rpm -y
yum install tinyxml

# Disabled because mysql-workbench 6.2.5-1 works and 6.3.10-1.el7 does not.  I do not want an update.
vi /etc/yum.repos.d/mysql-community.repo
name=MySQL Tools Community
[2 Jan 2018 15:25] Roy Dew
The workaround provided is to use version Workbench version 6.3.8. This is not a fix to the current issue with version 6.3.9 and 6.3.10.

Why release new versions of software with known critical defects which make them useless on RHEL v7, CentOS v7 and Oracle Linux v7?