Bug #93108 Crash on creating ssh tunnel
Submitted: 7 Nov 2018 16:22 Modified: 7 Nov 2018 20:12
Reporter: Andrew Cornforth Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version:8.0.13 OS:Linux (Mint 19 Tara Cinnamon)
Assigned to: CPU Architecture:x86 (64 bit)
Tags: connect, keychain, linux, ssh, workbench

[7 Nov 2018 16:22] Andrew Cornforth
I recently upgrading my linux OS from Mint 18.3 to Mint 19.
The primary reason for doing this was so that I could run Workbench 8.x (requires libcairo2, not a satisfiable dependency on Mint 18.3)

However, since upgrading to workbench 8, I have been unable to connect to any of my saved connections. Logs always end at the same point, with the lines:

15:39:12 [INF][     SSH tunnel]: Starting tunnel
15:39:12 [INF][     SSH tunnel]: Existing SSH tunnel not found, opening new one
15:39:18 [INF][     SSH tunnel]: Opening SSH tunnel to xxx.xxxxxxx.com

after prompting for the password to unlock the ssh key, the software simply terminates, no errors, no additional info in logs, nothing.

I have tried connecting to all the saved connections and the only one which progress further than this point was a server that is down. In this case i get to the server monitoring page, with appropriate warnings about the server not being available. In all other cases though the software crashes instantly.

note, none of the servers i'm connecting to are running mysql8 (yet)

How to repeat:
Having searched forums, stack-exchange and oracle's site for answers, it seems this may not be a common problem, so i'm not sure it's repeatable on another system, however, the step i use to successfully recreate this issue every time are as follows:
1. open workbench
2. connect to a database
3. watch the program crash.

Suggested fix:
I have had to revert to using 6.3.8 version until this is either fixed, or the issue identified so i can take whatever steps are necessary to configure my local system to make it work
[7 Nov 2018 16:32] Andrew Cornforth
in fact it was not 6.3.8 i was using before the upgrade, it was 6.3.10 (community)

I have tested both and they both seem to work properly, can connect to the databased and run queries etc.

I'm holding on 6.3.10 for now
[7 Nov 2018 20:12] MySQL Verification Team
Thank you for the bug report. Duplicate of bug https://bugs.mysql.com/bug.php?id=92972.