Bug #49061 Manage Security causes error

• Submitted: 24 Nov 2009 19:56
• Modified: 25 Nov 2009 16:22
• Reporter: Todd Farmer (OCA)
• Status: Closed
• Category: MySQL Workbench
• Severity: S2 (Serious)
• Version: 5.2 r4753
• OS: Windows (XP)
• CPU Architecture: Any

[24 Nov 2009 19:56] Todd Farmer

Description:
Trying to use the "Manage Security" feature, I get an exception:

Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line 199, in openSecurityManager
    tab.wait_server_check(4)
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line 95, in wait_server_check
    while tab.configuration.last_is_running_check is None and time.time() - t < timeout:
NameError: global name 'tab' is not defined

The second time I try to do the same thing, WB crashes.

How to repeat:
Try to "Manage Security"

Suggested fix:
Don't crash, do whatever "Manage Security" is supposed to do.

[24 Nov 2009 19:58] Peter Laursen

I think this is a duplicate of another bug report (from last week I think).

[25 Nov 2009 13:54] Johannes Taxacher

this has been fixed. will be included in 5.2.9

[25 Nov 2009 16:22] Tony Bedford

An entry was added to the 5.2.9 changelog:

Clicking on the Action Item, Manage Security, on the Home screen generated the following exception:

Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line
199, in openSecurityManager
    tab.wait_server_check(4)
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line 95,
in wait_server_check
    while tab.configuration.last_is_running_check is None and time.time() - t < timeout:
NameError: global name 'tab' is not defined

Further, if this Action Item was clicked again then MySQL Workbench crashed.