MySQL Bugs: #66349: SQL Editor does not open (as closed Bug #61560)

Bug #66349	SQL Editor does not open (as closed Bug #61560)
Submitted:	13 Aug 2012 10:56	Modified:	15 Aug 2012 8:47
Reporter:	Gordon Scott	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.41 CE revision 9724	OS:	Windows ( 7 x64)
Assigned to:		CPU Architecture:	Any

Description:
I have a problem that looks to me exactly like the closed Bug #61560.

The SQL editor does not open for Table Editing or Query.

How to repeat:
I try from Workbench to open the SQL Editor via Edit Data Tables, I get the pop-up for parameters, then password, then schema+table, then password again, then the pop-up:
-------------------
Opening SQL Editor
As SQL editor instance for '' is opening and should be available in a moment.
Please stand by...
-------------------

MtSQL Workbench shows "Connecting..." in the status line, but it appears I shall wait forever for the editor.

Right-click on the instance and "Query Database" is similar but includes the connection name "Local instance MySQL55" between the quotes.

Opening with a Command Line Client works OK.

Thank you for the bug report. I have this behavior on one machine after verify the bug http://bugs.mysql.com/bug.php?id=66232.

FYI, as I was constructing the tables, I did move columns around, so I have done something similar and quite possibly exposed the same issue. At present I have no data in my tables.

Thank you for the feedback. I did a mistake in my prior edit instead of Verified status I did Feedback (now corrected).

I'm having the exact same bug with 5.2.41 CE revision 9724.
My connection was working fine but I unchecked "Safe Updates" which required a reconnect. Since then I have been unable to connect.  Yes, I tried checking "Safe Updates" back....

Sorry my version is 5.2.41 CE revision 9727

Someone else also opened a bug report on this:

http://bugs.mysql.com/bug.php?id=66358

Restarting the application did not fix the issue...
But.... rebooting the PC did.

Duplicate of bug #66358

Strictly the other bug report is a duplicate of this.

That bug report advises to try 5.2.42.

5.2.42 is working for me.

I  just installed the latest version and now have the same problem