Bug #73627 Workbench Administrator - InvalidPasswordError: Incorrect password for sudo
Submitted: 19 Aug 2014 0:28 Modified: 19 Sep 2014 5:21
Reporter: Jeremy Richardson Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:5.2.45 OS:MacOS (10.8.4)
Assigned to: CPU Architecture:Any

[19 Aug 2014 0:28] Jeremy Richardson
Description:
I recently tried to access the Workbench Administrator  getting the error.
Error Starting Workbench Administrator - InvalidPasswordError: Incorrect password for sudo

Recently our company changed the administrator user for the computer which I think is issue(not a 100% sure) and why its not recognizing the new password. I tried restarting the computer in case the app files needed to restart but this didn't work. I tried going into Manage Server Instances > System Profile and changing sudo command /usr/bin/sudo -p mypassword /bin/sh -c
This breaks workbench when trying to load Server Administration after the change. This command could be wrong, its just what was already there, as I didn't set it up. However, when I paste whats there now into a terminal window:
/usr/bin/sudo -p EnterPasswordHere /bin/sh -c. Its prompts EnterPasswordHere and then I enter the new sudo password and the command works. So i'd like to know what I can do to tell workbench that my sudo password has changed. 

How to repeat:
As far as I know the only thing that has changed recently is the Administrator password for the mac was changed.
[19 Aug 2014 5:21] MySQL Verification Team
Thank you for the report.

Please note that reported version 5.2.45 is very old and many bugs were fixed since. Please upgrade to current version 6.1.7 and inform us if the issue still
exists. You can download latest WB version from http://dev.mysql.com/downloads/workbench/

Thanks,
Umesh
[19 Aug 2014 5:22] MySQL Verification Team
Also, see Bug #65162
[20 Sep 2014 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".