Bug #59416 workbench crashes when adding schema privs
Submitted: 11 Jan 2011 12:51 Modified: 3 Mar 2011 14:54
Reporter: Roy Sharp Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.31CE rev 7115 OS:Microsoft Windows (7 Ultimate, XP)
Assigned to: CPU Architecture:Any
Tags: Schema Privileges, user, workbench

[11 Jan 2011 12:51] Roy Sharp
The workbench crashes when adding access to multiple schema for a user

mysql v5.0.77-4.e15_5.4 running on CentOs 5.5 VM under VMWare on same PC

How to repeat:
create a new user
switch to schema tab
add - any host, pick a schema, select some of the access rights (apply, optional)
add another - any host, pick another schema, click OK to return to the access rights list

program crashes.
[11 Jan 2011 13:42] Valeriy Kravchuk
By doing actions like you described and then trying to save and revert changes on Windows XP I've got unhandled exception first and then program crash. So, there is a problem here for sure.
[11 Feb 2011 12:00] Mike Lischke
I cannot reproduce this, neither the problem of the original poster nor a crash on revert. This might have to do with either the fact that I used MySQL 5.1. server (5.0 is not supported) and/or the fixes for user management we added due to problems with MySQL 5.5.x.

Please try again with a 5.1 or 5.5 server. If you still see the problem then please wait for the next release (due soon) and try that. If the error still occurs we will try to find a scenario to reproduce it here.
[11 Feb 2011 12:40] Roy Sharp
I think that the answer is in your post - I stated that I was using 5.0.77 and you tell me 5.0 is not supported!
[3 Mar 2011 14:54] Alfredo Kojima
Thank you for taking the time to report a problem.  Unfortunately you are not using a current version of the product you reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open".  Again, thank you for your continued support of MySQL.