MySQL Bugs: #53302: Crashes on open connection

Bug #53302	Crashes on open connection
Submitted:	30 Apr 2010 5:54	Modified:	21 Jun 2010 10:25
Reporter:	Brett Trotter	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.19, 5.2.20, 5.2.21	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
This bug has been present since I started trying to use workbench 5.2.X, I believe 5.2.12, but is still present in 5.2.20.

I'm running RHEL 5.5 on an x86_64. When I first run workbench, if I click to open an existing connection, it just crashes. To prevent crashing, I have to first click open connection to start querying, select the stored connection, and click "store in keychain" (which seems to never actually save anyway). If I go through the store in keychain approach, and enter the correct password, it doesn't crash, but does ask for the password again. Subsequent connection attempts with the application open will work clicking the existing connections in the list under SQL Development.

How to repeat:
See Description.

Correction, I meant 5.2.19.

I just compiled .20 and the problem is better--- but now seems intermittent. Several times I was able to double click and go right to my connection, but 1 out of the 3 I've tried still crashes.

Now trying to Alter Table crashes it instantly (5.2.20) as well. Downgrading back to .19.

Hi Brett,
what package of workbench did you download to build/run it on your system?
thanks in advance

The Fedora SRC RPM straight off of the mysql website.

Did you ever rm -rf ~/.mysql/workbench and reconfigure connections again?

Yes-- same crash after re-creating the connection. I rm'd the dir, ran workbench, clicked new connection, and with both TCP and local, I can input the connection name, username, and hit store in keychain, enter the password incorrectly (though I believe entering correctly will sometimes crash), and hit ok, then hit test connection and it crashes without error. Hitting clear password after store password also crashes.

This behavior continues in 5.2.21.

P.S. despite being supposedly stored in the keyring, upon re-running the program, it asks for the password again, leading me to think this is a gnome keyring issue.

Maybe a separate issue but with 5.2.21 and MySQL-server-community-5.1.45-1.rhel5, when I click create table or alter table on an innodb table after successfully connecting and getting the list of tables up, it crashes....

I get the same condition on Windows XP Professional, SP3 running version 5.2.19 Beta.

Do you have a core dump for us?

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