Bug #109655 MySQL Workbench crashes when no connection was found
Submitted: 16 Jan 2023 17:36 Modified: 17 Jan 2023 12:19
Reporter: Jonas D Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.31 OS:Ubuntu (22.04)
Assigned to: CPU Architecture:x86
Tags: Connection, crash

[16 Jan 2023 17:36] Jonas D
Description:
When I open a (saved) connection but the server isn't up, I land at ordinary welcome screen and can see the "no connection established" message, as expect. But after a second the whole workbench crashed - and doesn't even create an autosave.
I can see to logs:
- `sql_actions_[my_connection_namye].log`: `[1, 18:31:09] Could not connect, server may not be running.: Unable to connect to localhost`
- `wb.log`:
```18:31:09 [ERR][SQL Editor Form]: SqlEditorForm: exception in do_connect method: Exception: Unable to connect to localhost
18:31:09 [WRN][SQL Editor Form]: Unable to connect to localhost
18:31:09 [INF][SQL Editor Form]: Error 2003 connecting to server, assuming server is down and opening editor with no connection
18:31:09 [INF][SQL Editor Form]: Error 2003 connecting to server, assuming server is down and opening editor with no connection
18:31:09 [ERR][wb_admin_control.py:init:307]: Error connecting to MySQL: Unable to connect to localhost (code 2003)
18:31:09 [ERR][wb_admin_control.py:server_polling_thread:561]: Error creating SQL connection for monitoring: MySQLError('Unable to connect to localhost (code 2003)')
```

I tried to connect to MySQL and to TiDB, it happens in both cases. Testing the connection from the connection overview won't lead to a crash.

How to repeat:
1. Download and install `mysql-workbench-community_8.0.31-1ubuntu22.04_amd64.deb`.
2. Create a new connection, change none of the default values but make sure there's no db server running for the port (or change the port).
3. Connect
[17 Jan 2023 12:17] MySQL Verification Team
Hello Jonas,

Thank you for the bug report.
I tried to reproduce your issue on Ubuntu 22.04 with workbench 8.0.31 and followed exact mentioned steps but I am not seeing any issues at my end. 

Regards,
Ashwini Patil
[17 Jan 2023 12:19] Jonas D
Thanks for your reply! Seems like it is somewhat related to my individual system then. Are there any more logs I could supply?