Bug #24628 Had to create a symlink for /tmp/mysql.sock pointing to my mysql.sock
Submitted: 27 Nov 2006 18:05 Modified: 27 Nov 2006 19:16
Reporter: Eduardo Kienetz Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Workbench Preview Severity:S3 (Non-critical)
Version:1.1.5alpha/1.1.6rc OS:Linux (Linux)
Assigned to: CPU Architecture:Any
Tags: mysql.sock, socket, symlink

[27 Nov 2006 18:05] Eduardo Kienetz
Description:
I've tried to use MySQL Workbench but it wouldn't connect to my MySQL server running locally. When I ran MySQL Admnistrator I noticed it has an option to point to the mysql.sock file if not /tmp/mysql.sock . By doing that MySQL Administrator worked and so I saved the connection info believing MySQL Workbench would read it. Since MySQL Workbench didn't read that info, I had to create a symbolic link from /tmp/mysql.sock to my /var/run/mysql/mysql.sock (Slackware 11 default). So basically that option at MySQL Adminstrator gave me the hint to create the link. 

How to repeat:
Just try to use MySQL Workbench on Slackware 11's default mysql install :)

Suggested fix:
MySQL Workbench should also have the option to set the path to the mysql.sock file so we don't need to create a symlink.
[27 Nov 2006 19:16] MySQL Verification Team
Thank you for the bug report.