MySQL Bugs: #54849: still crashes on RHEL 5 when connecting to database

Bug #54849	still crashes on RHEL 5 when connecting to database
Submitted:	28 Jun 2010 6:27	Modified:	16 Jul 2010 18:58
Reporter:	Brett Trotter	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.24	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
This is an error I've reported before, but its been getting worse and worse on successive releases. 5.2.19 is about the last one I can even moderately use.

I have a crash log I'll post, but no core dump.

How to repeat:
Bottom line, now when I try to open a connection, it just crashes.

RHEL 5, x86_64, after patching out the 3 gtk related lines in my other bug.

crash log

Attachment: wb.log (text/x-log), 51.07 KiB.

old bug was #53302 http://bugs.mysql.com/bug.php?id=53302

After deleting the .mysql/workbench and trying to create a new connection I get

Cannot Connect to Database Server
Your connection attempt failed for user 'root' from your host to server at 127.0.0.1:3306:
  GNOME_KEYRING_RESULT_DENIED

Please:
1 Check that mysql is running on server 127.0.0.1
2 Check that mysql is running on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the root has rights to connect to 127.0.0.1 from your address (mysql rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from

which I've seen on the previous bug as well.

unfortunately we don't support building/running Workbench under RHEL 5.x as there are a lot of too-old-dependency problems. we do offer RHEL6 packages though.

Yeah, why support the current version of the biggest linux vendor's enterprise offering. RHEL6 is only in beta, and many won't or won't be able to switch for up to a year in the best case depending on when the release occurs within their upgrade cycles or rollout timetables. MySQL administrator isn't exactly using a lot of bleeding edge technology or 3d rendering. I'll leave it at it's too bad RHEL5 won't be supported and you can close the ticket.