Bug #44267 | When exiting with unsaved changes, "cancel" closes application | ||
---|---|---|---|
Submitted: | 14 Apr 2009 16:39 | Modified: | 8 Jun 2009 12:30 |
Reporter: | Daniel Hallgren | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.1.10 | OS: | Linux (Ubuntu 8.10 x86) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
Tags: | CHECKED |
[14 Apr 2009 16:39]
Daniel Hallgren
[15 Apr 2009 0:56]
MySQL Verification Team
Thank you for the bug report. The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 31982 error_code 169 request_code 152 minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
[3 Jun 2009 21:23]
Johannes Taxacher
this is fixed. will be included in 5.1.13
[8 Jun 2009 12:30]
Tony Bedford
An entry was added to the 5.1.13 changelog: When exiting MySQL Workbench with unsaved changes, you are given the choices Save, Don't Save and Cancel. When Cancel was clicked, MySQL Workbench exited without saving, rather than returning to the application without making any changes. This only happened when clicking the main application Close button, in the upper right corner. It did not happen if the application was exited by selecting File, Exit from the main menu.