Bug #45491 Can't open the mwb file that create and edit by workbench v5.0 in XP
Submitted: 15 Jun 2009 4:23 Modified: 1 Jul 2009 10:52
Reporter: Leo SHI Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:mysql-workbench-oss-5.1.13-1-i386 OS:Linux (Ubuntu9.04)
Assigned to: Maksym Yehorov CPU Architecture:Any
Tags: CHECKED, crash, dump, liunx, regression, ubuntu

[15 Jun 2009 4:23] Leo SHI
Description:
I install the mysql-workbench-oss-5.1.13-1-i386 in my ubuntu9.04(kernel 2.6.30),when I open my old mvb file(create and edit by workbench v5.0 in XP),the window of workbench closed self.If I install the mysql-workbench-oss-5.1.12-i386(Beta),everything in order.

How to repeat:
mysql-workbench-oss-5.1.13-1-i386 in Ubuntu open the mwb file that create and edit by workbench v5.0 in XP
[15 Jun 2009 9:39] Valeriy Kravchuk
I can open this file without any problem with 5.2.1 on Mac, for example.
[15 Jun 2009 9:58] Leo SHI
I only have XP and Ubuntu.I'll try it in XP with new version,but I still have not idea about ubuntu
[15 Jun 2009 10:02] Valeriy Kravchuk
Verified just as described with 64-bit .deb package of 5.1.13 on 64-bit Ubuntu 9.04.
[16 Jun 2009 1:40] Leo SHI
I try it in XP with mysql-workbench-oss-5.1.13-rc-win32.msi,got a alert about a problem(I will upload screenshot),then I save the file,reboot to Ubuntu,everthing is OK!
But I do not understand what's mean about the alert.Is that mean there is a table named 'property',but I can't see it,and it has not relation with any table?
May get a official explain? thanks a lot.
[16 Jun 2009 1:41] Leo SHI
alert in XP

Attachment: alert.JPG (image/jpeg, text), 14.51 KiB.

[30 Jun 2009 12:38] Maksym Yehorov
Fixed in rev #4219
[30 Jun 2009 19:02] Johannes Taxacher
this is fixed. fix will be included in 5.1.17
[1 Jul 2009 10:52] Tony Bedford
An entry was added to the 5.1.17 changelog:

MySQL Workbench 5.1.13 running on Ubuntu Linux crashed when it attempted to load a model file created using MySQL Workbench 5.0 on Windows XP. The same model file did load correctly using MySQL Workbench 5.1.12.