MySQL Workbench don't work

[aecordoba]

I just installed openSuSE Tumbleweed. (Clean installation.)
Then I installed MySQL from MySQL site packages and the MySQL Workbench from openSuSE repository:

adrian@asia:~> rpm -qa mysql*
mysql-community-embedded-5.7.20-1.sles12.x86_64
mysql-community-client-5.7.20-1.sles12.x86_64
mysql-community-libs-5.7.20-1.sles12.x86_64
mysql-community-server-5.7.20-1.sles12.x86_64
mysql-community-common-5.7.20-1.sles12.x86_64
mysql-community-devel-5.7.20-1.sles12.x86_64
mysql-community-embedded-devel-5.7.20-1.sles12.x86_64
mysql-workbench-6.3.10-1.2.x86_64

MySQL server is running:

adrian@asia:~> ps -efa | grep mysql*
mysql     1770     1  0 13:02 ?        00:00:01 /usr/sbin/mysqld --daemonize 
--pid-file=/var/run/mysql/mysqld.pid
adrian    5876  5019  0 13:24 pts/2    00:00:00 grep --color=auto mysql*

And I can connect to the server:

adrian@asia:~> mysql -u root -p
Enter password:  
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.7.20 MySQL Community Server (GPL)

Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement
.

mysql> 

But when I want to create a new connection from MySQL Workbench, delete the default connection, or connect to the server, MySQL Workbench closes.

Do you have any idea, what is happening?

Thank you, very much.

[Knurpht]

Why did you install SLES packages on openSUSE Tumbleweed ?
https://software.opensuse.org/packag...mmunity-server
Why mysql and not the distro's mariadb packages ?
https://software.opensuse.org/package/mariadb

That would at least guarantee that these packages are built against the same environment. MySQL-Workbench is available from the TW repo itself as well.

[aecordoba]

Why did you install SLES packages on openSUSE Tumbleweed ?
https://software.opensuse.org/packag...mmunity-server
Why mysql and not the distro's mariadb packages ?
https://software.opensuse.org/package/mariadb

That would at least guarantee that these packages are built against the same environment. MySQL-Workbench is available from the TW repo itself as well.

Well... I installed these packages without any problem on Tumbleweed, Leap 42.2 and Leap 42.3. MySQL Community Server from MySQL site is a 64 bit database that work very well with databases I work.
Anyway, MySQL Server is not the problem.
The problem is the Workbench.

Thank you, for answer.

[Miuku]

I concur with Knurpht that you should use only distribution packages due to minute differences between SLE and Leap.

That being said, if you were to launch workbench from a terminal (konsole for example), it would dump the debug messages there and it would help you to track down why it's crashing (or closing). Unsurprisingly the command is mysql-workbench

[aecordoba]

I concur with Knurpht that you should use only distribution packages due to minute differences between SLE and Leap.

That being said, if you were to launch workbench from a terminal (konsole for example), it would dump the debug messages there and it would help you to track down why it's crashing (or closing). Unsurprisingly the command is mysql-workbench

This is the error:

adrian@asia:~> mysql-workbench
/usr/bin/mysql-workbench: line 25: ldconfig: command not found
Workbench can't find libproj.so, some options may be unavailable.

(mysql-workbench-bin:15657): Gtk-WARNING **: Theme parsing error: gtk.css:68:
35: The style property GtkButton:child-displacement-x is deprecated and shoul
dn't be used anymore. It will be removed in a future version

(mysql-workbench-bin:15657): Gtk-WARNING **: Theme parsing error: gtk.css:69:
35: The style property GtkButton:child-displacement-y is deprecated and shoul
dn't be used anymore. It will be removed in a future version

(mysql-workbench-bin:15657): Gtk-WARNING **: Theme parsing error: gtk.css:70:
34: The style property GtkCheckButton:indicator-size is deprecated and should
n't be used anymore. It will be removed in a future version

(mysql-workbench-bin:15657): Gtk-WARNING **: Theme parsing error: gtk.css:71:
36: The style property GtkCheckMenuItem:indicator-size is deprecated and shou
ldn't be used anymore. It will be removed in a future version

(mysql-workbench-bin:15657): Gtk-WARNING **: Theme parsing error: gtk.css:73:
46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecate
d and shouldn't be used anymore. It will be removed in a future version

(mysql-workbench-bin:15657): Gtk-WARNING **: Theme parsing error: gtk.css:76:
30: The style property GtkExpander:expander-size is deprecated and shouldn't 
be used anymore. It will be removed in a future version

(mysql-workbench-bin:15657): Gtk-WARNING **: Theme parsing error: gtk.css:83:
29: The style property GtkStatusbar:shadow-type is deprecated and shouldn't b
e used anymore. It will be removed in a future version
Ready.


(mysql-workbench-bin:15657): glibmm-ERROR **:  
unhandled exception (type std::exception) in signal handler:
what: error calling Python module function WbAdmin.autoDetectLocalInstance

adrian@asia:~> 

glibmm, of course, is installed.
I can't find the error.
Thank you, very much.

[aecordoba]

Why did you install SLES packages on openSUSE Tumbleweed ?
https://software.opensuse.org/packag...mmunity-server
Why mysql and not the distro's mariadb packages ?
https://software.opensuse.org/package/mariadb

That would at least guarantee that these packages are built against the same environment. MySQL-Workbench is available from the TW repo itself as well.

https://software.opensuse.org/packag...mmunity-server not contain MySQL Community Server for Tumbleweed.

[tsu2]

Did you search this Forum for any discussions relating to MySQL Workbench before posting your question?
If you did, you should have found the following which is only weeks old as of today

https://forums.opensuse.org/showthre...ight=workbench

If you think your problem is different somehow, then you can post accordingly, but inspect what was discussed in that thread first.

TSU