Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55877 - [mysql-workbench] cannot start workbench, libmysqlclient.so.18 not found

Attached to Project: Community Packages
Opened by nicolas (nicolas7) - Thursday, 05 October 2017, 11:34 GMT
Last edited by Christian Hesse (eworm) - Friday, 06 October 2017, 07:26 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I installed mysql-workbench with the package manager, but I cannot start it, I have this error:


Workbench can't find libproj.so, some options may be unavailable.
/usr/bin/mysql-workbench-bin: error while loading shared libraries: libmysqlclient.so.18: cannot open shared object file: No such file or directory


Indeed, I have libmysqlclient.so.20 on my system...

I tried doing a symlink libmysqlclient.so.18 -> libmysqlclient.so.20
then I am able to launch mysql-workbench but then I can't use it, they are just too many segmentation faults...

What should I do ? thank you
This task depends upon

Closed by  Christian Hesse (eworm)
Friday, 06 October 2017, 07:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  mysql-workbench 6.3.9-6
Comment by Christian Hesse (eworm) - Thursday, 05 October 2017, 13:19 GMT
To give some more insight:

The mysql-workbench package comes with a bundled libmysqlclient.so (/usr/lib/mysql-workbench/libmysqlclient.so.20). We also use bundled mysqlconnector-c++ and gdal as these have to be linked against the same libmysqlclient.so. So mysql-workbench should not know or touch system's libmysqlclient.so.18. Possibly you installed libraries from AUR that are linked against libmysqlclient.so where our official packages are not?
Comment by nicolas (nicolas7) - Thursday, 05 October 2017, 13:26 GMT
Thank you for your reply.

I did install mysql-workbench this way:
yaourt mysql-workbench

then I had to choose between these two options:

1 community/mysql-workbench 6.3.9-5 [installed]
A cross-platform, visual database design tool developed by MySQL
2 aur/mysql-workbench-git 6.3.9.r0.g1972008-1 (2) (0,00)
A cross-platform, visual database design tool developed by MySQL - git checkout


So I installed the first one : community/mysql-workbench 6.3.9-5

Then I tried to install aur/mysql-workbench-git 6.3.9.r0.g1972008-1 but I needs to download the git repo of mysql-server which is around 1.5 GB...

Should I try to install this one anyway ?

How may I find out if I installed libraries from AUR that are linked against libmysqlclient.so ?
Comment by Christian Hesse (eworm) - Thursday, 05 October 2017, 13:37 GMT
This command lists all libraries that /usr/bin/mysql-workbench-bin is linked against:

objdump -p /usr/bin/mysql-workbench-bin | grep -i needed

This should list libmysqlclient.so.20, which is found in /usr/lib/mysql-workbench/.
Check each library with the same command, probably one is linked against libmysqlclient.so.18.

Please note that you have to check (or skip) libgdal.so.20 from /usr/lib/mysql-workbench/.
Comment by nicolas (nicolas7) - Thursday, 05 October 2017, 13:59 GMT
So, I have no idea what does it mean but you are right! :)

The command : objdump -p /usr/bin/mysql-workbench-bin | grep -i needed
lists libmysqlclient.so.20, as you expected


And I tried the command on a few libs and I have a match with this one:

objdump -p /usr/lib/mysql-workbench/libwbpublic.so | grep -i needed | grep libmysql

NEEDED libmysqlclient.so.18


So what does it mean ? What can I do ?
Thank you
Comment by Christian Hesse (eworm) - Thursday, 05 October 2017, 15:06 GMT
Indeed, that looks suspicious.
Comment by Christian Hesse (eworm) - Thursday, 05 October 2017, 18:50 GMT
Should be fixed with mysql-workbench 6.3.9-6.
Comment by nicolas (nicolas7) - Friday, 06 October 2017, 07:14 GMT
Awesome, thank you very much Christian :)

Loading...