Bug #61272 could not create sakila scheme
Submitted: 23 May 2011 21:26 Modified: 24 Jun 2011 7:38
Reporter: David Shvo Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.33b OS:Windows (7)
Assigned to: CPU Architecture:Any
Tags: example db, sakile

[23 May 2011 21:26] David Shvo
Description:
tried to create sakile scheme by double clicking on sakila.mwb and it asked me to fill bug repport

How to repeat:
double clicking on sakila.mwb after installing my sql win installer
workbench crashed
[23 May 2011 21:43] MySQL Verification Team
Thank you for the bug report. Which version of Workbench are you using 5.2.33?. Thanks.
[24 May 2011 5:25] David Shvo
i am using 5.2.33 CE revision 7508
[24 May 2011 6:32] Valeriy Kravchuk
Please, send the output of Help > System Info menu item.
[24 May 2011 6:55] David Shvo
MySQL Workbench CE for Windows version 5.2.33

Configuration Directory: C:\Users\SHVO\AppData\Roaming\MySQL\Workbench

Data Directory: C:\mysql\MySQL Workbench 5.2.33

Cairo Version: 1.8.8

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

OpenGL Driver Version: 2.1.0 - Build 8.15.10.2302

OS: Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit

CPU: 2x Intel(R) Pentium(R) CPU        P6200  @ 2.13GHz, 7.7 GiB RAM

Active video adapter: LogMeIn Mirror Driver

Installed video RAM: 0 MB

Current video mode: 1366 x 768 x 4294967296 colors

Used bit depth: 32

Driver version: 7.1.542.0

Installed display drivers: NULL

Current user language: Hebrew (Israel)
[24 May 2011 7:38] Valeriy Kravchuk
I do not see any problem on Windows XP, so this is related to your OS version/video adapter probably. When you'll see this error again, please, right click somewhere in the error dialo box with no text and use Copy stack trace to clipboard context menu item. Send stack trace to this report.
[24 Jun 2011 23:00] Bugs System
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".