MySQL Bugs: #49602: edit configuration raises unhandled exception

Bug #49602	edit configuration raises unhandled exception
Submitted:	10 Dec 2009 18:50	Modified:	21 Jan 2010 17:47
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.10	OS:	Windows (7 - 64 bit)
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
When trying to edit configuration an exception occurs.

How to repeat:
see image

Suggested fix:
no idea

clicking 'Configuration' tab returns exception

Attachment: conf.jpg (image/jpeg, text), 51.08 KiB.

.. and additionally when the connection was configured/defined I was told that the my.ini could be read by WB.

Peter,

many thanks for writing a bug report.

Your bug here is a duplicate of bug #49060.

We fixed this already in Workbench 5.2.10.

Are you really sure you used that version?

We aren't able to repeat this.

If you really have this failure on Workbench 5.2.10 then please let us know the server version.

yes .. 5.2.10

Attachment: about.jpg (image/jpeg, text), 23.67 KiB.

I just reproduced it with a fresh program start. It happens both when double-clicking a connection name pointing to a running server and a not-running server.

I am not familiar with logging and debugging options. I only intend to use WB for server management and nothing else (and only because MA is not supported any more), so I don't intend to spend time to study the program in depth. However if you can guide me how to produce debug output I can do this.

btw: I think I should have told that I am able to continue after closing the error dialogue.

changed synopsis:
"can't edit configuration" >> "edit configuration raises unhandled exception"

I did not notice yesterday that I am able to continue after closing the msqbox. On my system the 'edit configuration' pages paint very slow. So I closed the tab before anything was painted (I will have to wait some seconds before something happens). But anyway the original synopsis was not a precise description.

I couldn't repeat on Windows Vista Home Premium 64-bit. Probably one more bug specific to hardware/OS.

.. or maybe because this is not a 'fresh' installation, but an upgrade?  I have had a few previous 5.2 installations (but I do remember how many and what exact versions). I can try uninstall+delete everything related to program+do a fresh install if it is relevant. (or provide debug information - with guidance on 'how-to')

Peter,

unfortunately yes. It would be a great help if you do a fresh install.

Nobody here is able to repeat this and there is a high chance that problem exist on upgrade but not on fresh installation.

After a fresh install of 5.2.10 it is not reproducible.
(fresh install =
* remvoe from 'add/remove programs
* delete folder in C:\program files
* delete folder C:\Users\Peter\AppData\Roaming\MySQL\Workbench
* install now using .msi)

I studied the folder structure on my system.

There is both a "C:\Program Files (x86)\MySQL\MySQL Workbench 5.1 OSS" and a "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 OSS" folder .. bot *only one* "C:\Users\Peter\AppData\Roaming\MySQL\Workbench" (ie. no seperate 'roaming' folder for 5.1 and 5.2).
.. what seems to cause problems when having both 5.2.x and older version(s) installed. My best guess only.

Peter,

many thanks for your feedback.

I will give this to our developers, so that they can check it.

peter, would it be possible to attach the my.cnf file you have been using with that problem - that might give us some leads to get onto that problem.
thanks in advance

it is the most basic file created by the configuration wizard for Windows .. I will attach it.

my.ini

Attachment: my.ini (application/octet-stream, text), 8.79 KiB.

I can't repeat. The reason of this bug was likely fixed.

does not appear in current build anymore.
fix will be included in 5.2.13

Changelog entry for #49060 (duplicate) has been updated accordingly.