MySQL Bugs: #60664: Lost connection, Server gone away only with Workbench 5.2.33

Bug #60664	Lost connection, Server gone away only with Workbench 5.2.33
Submitted:	27 Mar 2011 6:00	Modified:	13 Apr 2011 2:25
Reporter:	Dulani W	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.33b GA	OS:	MacOS (10.6.6)
Assigned to:		CPU Architecture:	Any
Tags:	Workbench Query Error Time Sleep

Description:
This is the Mac OS X version of Bug #57449.

The following errors are received on long queries (greater than 30 secs)

Error Code: 2013  Lost connection to MySQL server during query
Error Code: 2006  MySQL server has gone away

MySql server continues to process the query and it's progress can by observed using the Workbench Administration tab. Unfortunately, I think the query results are simply discarded once workbench feels that the connection is lost.

How to repeat:
It can be caused/repeated with this query: select sleep(30) or any query lasting longer than 30 seconds. 

Use SELECT sleep(30); to repeat.

On my machine, it appears to occur at around 24 seconds.  

Suggested fix:

I tried all of the fixes recommended on #57449 and elsewhere including:
1) Downloading and installing the updated .xml file provided in #57449
2) Increasing the Read Timeout value on the MySQL server.
3) Increasing the DBMS connection keep-alive interval in the preferences to: 4000.
4) Downloading and running version 5.2.28.

None of these seem to help.  Not sure what else to try.

this is a duplicate of bug #60103

How is this a duplicate of a closed bug for another OS?  This bug still exists on Mac, using Workbench version 5.2.34, and none of the suggested fixes in the "duplicate bug" fix the problem.