Bug #42550 MySQL Workbench crashes on startup
Submitted: 2 Feb 2009 18:00 Modified: 5 Feb 2009 14:23
Reporter: Giuseppe Maxia Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.1.7 OS:MacOS
Assigned to: CPU Architecture:Any
Tags: crash, library, start

[2 Feb 2009 18:00] Giuseppe Maxia
Description:
MySQL Workbench 5.1.7 for MacOSX crashes on startup.
The reason is that it looks for libmysqlclient.15, which is not on /usr/local/mysql/lib

Process:         MySQLWorkbench [14915]
Path:            /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier:      com.sun.MySQLWorkbench
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [95]

Date/Time:       2009-02-02 18:53:52.120 +0100
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  0

Dyld Error Message:
  Library not loaded: /usr/local/mysql/lib/libmysqlclient.15.dylib
  Referenced from: /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
  Reason: image not found

How to repeat:
launch Workbench on a machine where MySQL server is not installed, or where you have installed MySQL 5.1.

Suggested fix:
Provide the client library with MySQL Workbench. You can't assume that there will be a specific client library already installed.
[2 Feb 2009 18:09] Susanne Ebrecht
Guiseppe,

many thanks for writing a bug report. 
The problem is already known and the workaround is to install mysql in /usr/local.
[2 Feb 2009 18:19] Giuseppe Maxia
Installing MySQL in /usr/local/mysql is not a workaround.
MySQL is already installed in /usr/local/mysql. Only, it's MySQL 5.1, and the client library is libmysqlclient.16, not libmysqlclient.15, as WB expects.
That's why I said that WB should take care of the library in its own environment.
[2 Feb 2009 18:24] Susanne Ebrecht
Giuseppe,

sorry, I misunderstood the problem.

Of course Workbench should find the libs when they are in default folders.

Change triage to critical.
[2 Feb 2009 20:02] Giuseppe Maxia
After installing MySQL 5.0.67, it still crashes. Another library was not found

Process:         MySQLWorkbench [16870]
Path:            /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier:      com.sun.MySQLWorkbench
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [95]

Date/Time:       2009-02-02 21:00:47.223 +0100
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  0

Dyld Error Message:
  Library not loaded: /usr/local/lib/libglib-2.0.0.dylib
  Referenced from: /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
  Reason: image not found
[2 Feb 2009 21:01] Johannes Taxacher
new package has been uploaded. 
direct link: ftp://ftp.mysql.com/pub/mysql/download/gui-tools/mysql-workbench-oss-5.1.7b-osx10.5-i686.d...

no source-code has been changed (therefore we didn't name 5.1.8)
[5 Feb 2009 14:23] Tony Bedford
An entry was added to the 5.1.7 changelog:

MySQL Workbench 5.1.7 for MacOSX crashed on startup. The reason was that it was looking for libmysqlclient.15, which was not found in /usr/local/mysql/lib. The error generated was:

Process:         MySQLWorkbench [14915]
Path:            /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier:      com.sun.MySQLWorkbench
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [95]

Date/Time:       2009-02-02 18:53:52.120 +0100
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  0

Dyld Error Message:
  Library not loaded: /usr/local/mysql/lib/libmysqlclient.15.dylib
  Referenced from: /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
  Reason: image not found

Note that MySQL was installed, but the specific version of client library required was not present.