MySQL Bugs: #69475: Read Configuration File

Bug #69475	Read Configuration File - Error
Submitted:	14 Jun 2013 15:02	Modified:	27 Jun 2013 3:17
Reporter:	Robert Gebis	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.0.2 B2	OS:	MacOS
Assigned to:		CPU Architecture:	Any

Description:
After logging in to mysql server as root (set up root connection) . Now I try to click on left pane "Options File" and when I do I am prompted with another login window asking for root password. After I type my mysql root password I get prompted with new popup window stating..

"Read Configuration File"
   
Configuration file '' can not be found. New file will be created when changes are applied.

I think this refers to my.cnf file? This file is located in my /etc/ folder.

Clicking on above popup box ok button opens another popup

"Read Configuration File"

Configuration file did not contain section [mysqld], so a new one was added.
If that is not correct, please fix the section name in the Server Instance Editor and reopen the administrator.

I am sure that [mysqld] section is in my.cnf

further clicking on Ok button opens empty Administration - Option File window.

How to repeat:
1. Create new connection to local database with user name root (empty password)
2. Login to such account
3. Select "Options File" on let panel

Verified for the case that the Management params are not configured when the connection is setup.
As a workaround, select the correct OS from the connection editor, in the System Profile tab.

Posted by developer:
 
Fixed in repository. Seems to be Mac specific.
To repeat, create a local connection in the Mac, without setting up Management part. Then open the connection and select the Config File editor.

Fixed as of the upcoming MySQL Workbench 6.0.3 release, and here's the changelog entry:

On Mac OS X, the default configuration files for local server instances
were not discovered properly. Attempts to edit the "Options File" would
emit an error.

Thank you for the bug report.