Bug #70874 The MySQL workbench screen comes up. says report a bug and then disappears
Submitted: 11 Nov 2013 3:03 Modified: 11 Dec 2013 15:53
Reporter: Timothy Owens Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version: OS:Windows
Assigned to: CPU Architecture:Any

[11 Nov 2013 3:03] Timothy Owens
Description:
The MySQL workbench screen comes up. says report a bug and then disappears.
I was on my 4th assignment in a MySQL class and I am no longer able to access workbench.  I tried restoring my computer to an earlier time and it was no help so the problem is not on my side - it seems to be on the server.  
The only thing that seemed out of place when I closed MySQL workbench down and was unable to reopen it was that it said that a script that I was trying to save was too long to be saved.

My class assignments are due weekly and I'm only a few days away from my last day to withdraw.  Since I don't know when the matter will be resolved on the server side, I had to withdraw from the class and lost my tuition paid.  It seems like a good database but not if I'm taking a class and need a matter resolved right away in order to finish my assignments on time and not be penalized.  I really can't complain since I know the database is free and I still wouldn't mind having access to this database - if it can be fixed.  But if the server side messes up, its out of my control so I have to move to a self paced MS SQL Server certification format.  Just my two cents.

Anyway...great database and would like to learn more about it in the future if you have a way to fix the account. 

Best Regards,

Tim Owens

How to repeat:
Pull up workbench.  The report a bug screen comes up and then workbench disappears.  Cannot access it.
[11 Nov 2013 15:53] MySQL Verification Team
Please specify the exactly WorkBench version. Thanks.
[12 Dec 2013 1: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".