| Bug #49037 | Workbench hangs on variable setting when canceling password request | ||
|---|---|---|---|
| Submitted: | 24 Nov 2009 16:18 | Modified: | 26 Nov 2009 10:33 |
| Reporter: | Giuseppe Maxia | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S1 (Critical) |
| Version: | 5.2.8 | OS: | MacOS |
| Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
| Tags: | cancel, hang, password, setting, variables, workbench | ||
[24 Nov 2009 16:20]
Giuseppe Maxia
Probably related to Bug#49004 "Unhandled exception when clicking on 'Logs' button"
[24 Nov 2009 16:46]
Giuseppe Maxia
After 40 minutes, still hanging.
[24 Nov 2009 18:49]
Giuseppe Maxia
After 2 hours and 40 minutes, still hanging. I stopped it.
Restarted from the command line. The problem seems to be here:
File "/Applications/MySQLWorkbench_5_2_8.app/Contents/PlugIns/wb_admin_config_file_be.py", line 121, in apply_clicked
self.accept_action() # call action passed from caller(client)
TypeError: 'NoneType' object is not callable
[25 Nov 2009 19:32]
Johannes Taxacher
fixed in repository. will be included in 5.2.9
[26 Nov 2009 10:33]
Tony Bedford
An entry has been added to the 5.2.9 changelog: n the Configuration tab of the Server Administrator screen, if log file configuration changes were applied, MySQL Workbench hung if the password request dialog was cancelled.

Description: When setting variables in the administrator editor, if you click CANCEL on the password request, Workbench hangs, and becomes unusable. How to repeat: Using MySQL 5.1 and WB 5.28. 1) open the administrator editor 2) Click on "configuration" 3) click on "log files" 4) check a few options 5) click "apply" 6) click "view file" 7) click "apply" 8) in the password dialog, click "CANCEL" You will get a popup saying "Unhandled exception: 'NoneType' object is not callable". After that, the application hangs, and is unusable forever, and doesn't quit. ("forever" = more than 10 minutes, or way more than any 21st century user is willing to wait) Suggested fix: Handle the exception