MySQL Bugs: #63472: Unhandled exception in the Server Logs admin panel

Bug #63472	Unhandled exception in the Server Logs admin panel
Submitted:	29 Nov 2011 14:38	Modified:	28 Jan 2012 17:37
Reporter:	Philip Olson	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.36_pre11	OS:	MacOS
Assigned to:		CPU Architecture:	Any

Description:
Entering an incorrect password (when prompted, under 'Server Logs') yields an unhandled exception, which is as follows:

-------
Error:

Unhandled exception: Incorrect password for sudo
-------

It is then not possible to enter the correct password (switching tabs yields the exception without being prompted for the password), and instead, the Admin tab must be closed then reopened. 

This exception is displayed three times.

How to repeat:
These steps:
1. Open a 'Server Instance' under 'Server Administration'
2. Select 'Server Logs'
3. Enter an incorrect password at the prompt

Suggested fix:
Prompt for a correct password.

Please, explain how exactly server instance was configured. I tried both local and remote (administered via ssh) instances with 5.2.37 on Mac OS X and had not got any problems with Server Logs tab.

All default settings, local.

I was able to repeat the error, but then played with the settings and now cannot replicate the error even after changing all settings back to the original.

So my apologies. I suppose this bug report can be ignored. But entering a proper password seemingly has no affect. This probably isn't related (and a known "limitation"), but I do see the following no matter what I do (enter in a correct or incorrect sudo password):

"The current user has no permission to read /usr/local/mysql/data/water.local.err. Reading it with superuser privileges. Workbench has only limited support for this."

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".