MySQL Bugs: #56417: "Invalid inode index" when opening SQL Editor to 5.0.77 running on RHEL5 x86

Bug #56417	"Invalid inode index" when opening SQL Editor to 5.0.77 running on RHEL5 x86_64
Submitted:	31 Aug 2010 17:21	Modified:	31 Aug 2010 17:41
Reporter:	Robby D	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.26CE R6432	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any
Tags:	crash, workaround

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
When opening the initial stored connection to the MySQL server (5.0.77) running on an RHEL5 box (x86_64 architecture), the SQL Editor encounters a bug. It will not display the schema for the database. Closing the tab, and then re-opening the connection works (no error, schema are displayed). So there is a simple workaround, but the issue is still annoying.

How to repeat:
Setup a MySQL server version 5.0.77 on an RHEL 5 box and try to open a stored connection to that server in Workbench's SQL Editor on an Windows XP SP3 machine.

duplicate of bug #52648