MySQL Bugs: #55268: Unexpected Error: "The operation completed successfully" when modifying EER dgrm

Bug #55268	Unexpected Error: "The operation completed successfully" when modifying EER dgrm
Submitted:	14 Jul 2010 18:09	Modified:	15 Aug 2010 9:42
Reporter:	Stephanie Armsworthy	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.25 CE	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any
Tags:	EER Diagram, error, modeling

Description:
When modifying an EER diagram (e.g. moving/resizing table boxes, adding/deleting relationships, deleting columns) suddenly an error dialog appears:

MySQL Workbench Unexpected Error
MySQL Workbench has encountered a problem
The operation completed successfully

We are sorry for the inconvenience [...]

The "Report Bug" button did nothing, and "Close" button closed the dialog, but a new one popped up in its place.

How to repeat:
1. Create new connection (my case, not on localhost, tables were MyISAM)
2. Create EER model from existing database (my case, 76 tables)
3. Modify resulting EER diagram by moving/resizing table boxes, adding/deleting relationships, deleting columns, etc
4. Program seemed slightly unresponsive/laggy (e.g. table box movement would not occur for 5 seconds)
5. Described error dialog popped up for what seemed to be no good reason.

Could you please provide the output of Help->System Info. Thanks in advance.

MySQL Workbench CE for Windows version 5.2.25

Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

Rendering Mode: OpenGL is not available on this system, so GDI is used for rendering.

OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)

CPU: 2x Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz, 2.0 GiB RAM

Video adapter info:

Adapter type: Intel(R) Q35 Express Chipset Family

Chip Type: Intel(R) GMA 3100

BIOS String: Intel Video BIOS

Video Memory: 393216 KB

Please provide your model file.

Also we need to know which server version are you using?
On which OS is server running?
Is server using special sql-mode?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".