| Bug #48988 | Output window is not opening | ||
|---|---|---|---|
| Submitted: | 23 Nov 2009 12:44 | Modified: | 25 Mar 2010 16:48 |
| Reporter: | Geert Vanderkelen | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 5.2.8 | OS: | MacOS (10.6.2) |
| Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[23 Nov 2009 14:05]
Johannes Taxacher
output window only visible in the context of a model document
[3 Mar 2010 12:56]
Alfredo Kojima
This has been fixed
[3 Mar 2010 15:34]
William Warby
Is there currently any workaround for this? I see the bug has been fixed but it's not clear when the fix will make it into a release and meanwhile I can't connect to any of my servers and can't find out why, so I'm snookered and have had to revert to MySQL Administrator. I tried to find a file containing the output but failed.
[3 Mar 2010 15:40]
Alfredo Kojima
You can create an empty model and open the Output view there. You can also view some debug messages in Console.app
[25 Mar 2010 14:13]
Johannes Taxacher
output window has been changed to appear as a separate main tab (along with home, admin/query-sessions ...). fixed in repository
[25 Mar 2010 16:48]
Tony Bedford
A 'change' entry has been added to the 5.2.17 changelog: The Output window only appeared in the Model context. MySQL Workbench has been changed so that the Output window now has its own tab on the main screen.

Description: In Workbench Server Administration: When there is an error connecting to the target database, there is a message saying to open the 'output' for details. But 'View > Advanced > Output Window' is not showing/opening anything (keystroke neither). How to repeat: * Open 'Manage Server Profiles' * Open an instance > System Profile > Server Stats * Put something "wrong" in 'get_mem_total' e.g. System Type is MacOSX, just put get_mem_total = sysctl hw.memsize * Close the window, then open the instance. * Status bar says: "Coult not connect to target database: error calling WbAdmin.openAdministrator: see output for details"