MySQL Bugs: #69888: Workbench Users/Privs Add Acct: 'NoneType' object has no attribute 'nextRow'

Bug #69888	Workbench Users/Privs Add Acct: 'NoneType' object has no attribute 'nextRow'
Submitted:	1 Aug 2013 3:23	Modified:	6 Mar 2014 2:09
Reporter:	CHap Harrison	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.47	OS:	MacOS (10.8.4)
Assigned to:		CPU Architecture:	Any
Tags:	add Account, Unhandled exception, workbench

Description:
Adding an account in Workbench fails with Unhandled Exception alert box.

How to repeat:
MySQLWorkbench:
from Home, select Server Administration
click Users and Privileges
click Add Account
fill in acct info with Login Name = foobar, Auth = Standard, Limit Connectivity = %, and passwords
click Apply

Alert box appears reading Unhandled Exception: 'NoneType' object has no attribute 'nextRow'

Same error when I click on one of the existing accounts to edit it

Please try the latest version of the 6.0 series

Wish I could.  I went to dev.mysql.com where 6.0.5 was supposedly available, clicked the link, and got a message that the file did not exist.  If you can send me a working link i'd be glad to try again.

Please try again 6.0.5 is now available for Mac OS X. Thanks.

Downloaded 6.0.6.  Same error.

Please attach the wb.log file that you can get to from the Help menu.

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

Losing connection when adding user: wb.log

Attachment: wb.log (application/octet-stream, text), 12.31 KiB.

I have the same problem

Same for me, see log except below.
Sequal Pro also loses connection upon adding new or edit existing user so looks like a db issue of some sort.

15:51:38 [INF][wb_admin_grt.pyc]: AdministratorContext: Server version (5, 6, 15) is supported
15:51:57 [WRN][wb_admin_control.pyc]: Error executing SQL CREATE USER 'globemilk'@'%' IDENTIFIED BY '12345': Error executing 'CREATE USER 'globemilk'@'%' IDENTIFIED BY '12345''
Lost connection to MySQL server during query.
SQL Error: 2013
15:51:57 [WRN][wb_admin_control.pyc]: exec_sql: Loss of connection to mysql server was detected.
15:51:57 [WRN][wb_admin_control.pyc]: Error is recoverable. Reconnecting to MySQL server.
15:51:57 [INF][     SSH tunnel]: Existing SSH tunnel found, connecting
15:51:57 [WRN][wb_admin_control.pyc]: Auto-reconnection failed: Lost connection to MySQL server at 'reading initial communication packet', system error: 0 (code 2013)
15:51:57 [INF][wb_admin_control.pyc]: sql connection is down
15:51:57 [INF][wb_admin_control.pyc]: sql connection is down
15:51:57 [INF][wb_admin_control.pyc]: sql connection is down
15:51:57 [INF][wb_admin_control.pyc]: sql connection is down
15:51:57 [ERR][       pymforms]: Unhandled exception in Python code: 'NoneType' object has no attribute 'nextRow'

Please try WB 6.0.8

That's exactly the version I am using though.

I don't think the issue is workbench related then as I am getting errors in command line as well:

mysql> GRANT SELECT,LOCK TABLES ON information_schema.* TO 'username'@'localhost';
ERROR 1044 (42000): Access denied for user 'root'@'localhost' to database ‘information_schema'

It turns out that mysql.proc was the culprit:

> 2014-01-09 09:53:50 14236 [ERROR] Incorrect definition of table mysql.proc: expected column 'returns' at position 9 to have type longblob, found type char(64).
> 09:27:54 UTC - mysqld got signal 11 ;
> This could be because you hit a bug. It is also possible that this binary
> or one of the libraries it was linked against is corrupt, improperly built,
> or misconfigured. This error can also be caused by malfunctioning hardware.
> We will try our best to scrape up some info that will hopefully help
> diagnose the problem, but since we have already crashed, 
> something is definitely wrong and this may fail.

SOLUTION: 
run mysqlcheck to look for corrupted tables
run mysql_upgrade to fix mysql.proc table

> mysql.proc.returns changed to longblob instead of char(64)

restart mysql

All is wel and we're able to add users again. 
Perhaps this will help other with the same error.

I think I found a solution. I looked over my wb.log and found SQL 2006 errors, which was caused by connection timeout.

I have increased wait_timeout in the server's my.cnf and now it works perfect.

I'll close this bug since there has been no response from the original reporter and most people commenting here have solved it by fixing unrelated server installation issues.
Please reopen if the problem persists.