MySQL Bugs: #15304: Stored connections cause Query Browser to quit unexpectedly

Bug #15304	Stored connections cause Query Browser to quit unexpectedly
Submitted:	29 Nov 2005 7:17	Modified:	9 Jan 2006 23:31
Reporter:	kim hunter	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.17	OS:	MacOS (Mac OS X 10.4.3)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
When connecting to a Stored Connections in the "Connect to MySQL Instance" dialog at startup, Query Browser Unexpectedly Quits,

this happens even if you are not connecting to a stored connection if you have one stored.

How to repeat:
Store a Connection and try and connect to a database.

Suggested fix:
Deleted all Stored Connection and just rely on the last connection to save you connection.

Thanks for your bug report.  I was able to reproduce this bug using 1.1.17 and OSX 10.4.2

I think I've just fallen over this 'bug' too, but on Mac OS X 10.3.9.
The problem I have occurs with both the Query Browser and MySQL Administrator.

I've discovered that if the Mac's hostname (as reported by 'hostname' in terminal) is different from the one saved, then a crash occurs when you click on the connect button.
[My hostname changes depending on network connection (as router provides name via DNS)]

The problem is reproduceable. If I return to the network location used when the connection info was saved, then I can connect OK.

I have Crash Reporter logs if anyone is interested.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html