MySQL Workbench

Appendix D How To Report Bugs or Problems

The following is a list of tips and information that is helpful for reporting a MySQL Workbench bug.

A useful bug report includes:

Bugs that cannot be reproduced are difficult and nearly impossible to fix, so it is important to provide the steps necessary to reproduce the bug.

Where to report a bug

Visit and use one of the MySQL Workbench bug categories.

Log Levels

There are six different log levels, with increasing levels of verbosity: error, warning, info, debug1, debug2, and debug3. By default, the error, warning and info levels are enabled. There is also a "none" level that disables logging.


Please enable the debug3 level before generating a log for the report.

The enabled error log levels can be configured using an environment variable, or by using a command line parameter.

Both the environment variable and command line variants accept a single error level, but enabling a more verbose option will implicitly enable the levels below it. For example, passing in "info" will also enable the "error" and "warning" levels.


If both the command line and environment variable are set, the command line takes precedence.

For example:

# Microsoft Windows
shell> cd "C:\Program Files (x86)\MySQL\MySQL Workbench CE 8.0.17\"
shell> MySQLWorkbench.exe -log-level=debug3

# macOS
shell> cd /Applications
shell> MySQLWorkbench --log-level=debug3

# Linux (Ubuntu)
shell> cd /usr/bin
shell> mysqlworkbench --log-level=debug3

If the info level is enabled, the system information and all paths used in the application are also logged. On Microsoft Windows, this also means that the log file contains the full set of current environment variables that are active for the program.

Operating System Specific Notes

Microsoft Windows