MySQL Bugs: #93012: Workbench 8.0.13 will not start up

Bug #93012	Workbench 8.0.13 will not start up
Submitted:	30 Oct 2018 15:12	Modified:	1 Nov 2018 21:06
Reporter:	william hunton	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	8.0.13	OS:	Windows (Pro Build 10.0.17134)
Assigned to:		CPU Architecture:	Any (i7 260 gHz 64 bit)
Tags:	8.0.13, crash, start, workbench

Description:
Workbench upgrade from 8.0.12 to 8.0.13.  Reinstalled both from MSI and full download, multiple times.  Cleared cache, all references, rebooted between installations.

Product will start the first time.  Opens the workbench.  I can connect to remote DB SSH However it won't allow me to save the configuration - only shows the dropdown list for existing connections and that is the default empty DB. Does not allow me to enter a name for the connection.   

Shutdown Workbench.  

Try to restart and nothing happens.  I cannot find any errors it has thrown. Tried watching the startup process, but it seems to never even get to that command from Windows. Tried to restart from the Windows command line.  Did the same thing.      

How to repeat:
See above.  Uninstall.  Reinstall however you wish.  Follow automatic installation, complete package default settings.  Follow automatic installation, installing only Workbench 8.0.13 CE.

Thank you for the bug report. Which Server version are you trying to connect, are you able to create a connection without to be using SSH. Thanks.

@Miguel S. 
I can only connect to DB via SSH.  Those credentials are okay. 

MySQL Server release is  5.7.17

Workbench 8.0.12 worked fine last week.  Same DB.  Same connection string.

SSH connect test

Attachment: 93012.png (image/png, text), 66.51 KiB.

Icouldn't repeat on similar environment reported (WorkBench 8.0.13, Windows 10 Pro, for connection SSH see attached screenshot,connected with MySQL Server 5.7).

Could it be registry leftovers. I tried to reinstall 8.0.12.  It now behaves the same way.  I also checked port binding. 3306 was not being used.  

Appreciate any debugging tips please.

Please respond to my last question regarding the possibility that there could be left over registry issues from the repeated installations and removals that may be preventing Workbench from even initiating a startup.  

Perhaps there is some conflict between 8.0.12 and 8.0.13 that isn't cleaned up with removal and of 8.0.12 and installation of 8.0.13. 

If you cannot duplicate the issue, it probably is a local workstation "corruption" but if that occurred it *may* have occurred as a result of the upgrade. As I said, 8.0.12 was working as of 10/25/18. I am looking for other causes.  I may restore my laptop to sometime last week as a work around.   

Thanks again for your help.

Sorry I couldn't guess what is wrong on your environment, I removed 8.0.13, installed 8.0.12 and then the upgrade again not problem at all. Are you tested your ssh stuff outside WorkBench?.

I finally decided to reset my laptop.  I saved my data.  I reloaded Windows 10 pro.  I downloaded Workbench CE 8.0.12 from archives, the release that worked previously.  

The 8.0.12 release now works as it did before the 8.0.13 upgrade. Apparently there are setting conflicts buried deeply on my local machine that interfered with the upgrade to Workbench CE 8.0.13.  

Resetting the operating system and reloading my applications cleared the problems.

I believe I found the cause of the crash of Workbench CE.  It appears to be the installation of a plugin HTMLShemaReport.py.  See the .wer report attachment preceding this comment. I am unsure if it is the plugin which caused the crash or it was due to some other factor on my laptop - python 3.7 installed locally or other.