MySQL Bugs: #119869: unable to open MySQL workbench

Bug #119869	unable to open MySQL workbench
Submitted:	10 Feb 6:35	Modified:	26 Feb 8:48
Reporter:	Mohamed Kownian	Email Updates:
Status:	Won't Fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I am unable to open MySQL workbench, I am getting the pop up when i try to open it. Attached the screenshot

Error message:
We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team

How to repeat:
I am unable to open MySQL workbench, I am getting the pop up when i try to open it. Attached the screenshot

Error message:
We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team

Error message

Attachment: sql workbench error.png (image/png, text), 318.74 KiB.

How to Repeat:
1. Open MySQL
2. On MySQL connections, click on open connection then error pop up message appears (attached screenshot)

when i open application it gives this error message first

Attachment: sql workbench image error.png (image/png, text), 229.56 KiB.

Could you please provide an update on this.

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.