Bug #95118 MYSQL Workbench not work on ubuntu 19.04 disco
Submitted: 25 Apr 2019 0:49 Modified: 3 Sep 2019 21:47
Reporter: Jeffrey Zeng Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.15, 8.0.16 OS:Ubuntu (19.04)
Assigned to: CPU Architecture:Any
Tags: disco, ubuntu 19.04, workbench

[25 Apr 2019 0:49] Jeffrey Zeng
Description:
After do-release-upgrade form 18.10 to 19.04, mysql workbench was considered as not supported component, as be removed.
not found mysql workbench available of 19.04 on download page.

How to repeat:
on ubuntu 18.10, 
run sudo do-release-upgrade
type Y during upgrading process

expect: mysql workbench works on 19.04
result: mysql workbench was removed, as fail to re-install

Suggested fix:
mysql workbench works on 19.04
[25 Apr 2019 4:50] MySQL Verification Team
Hello Jeffrey Zeng,

Thank you for the report and feedback.

regards,
Umesh
[6 May 2019 0:56] Jeffrey Zeng
is there a work around to let it work on ubuntu disco?
[12 May 2019 7:43] MySQL Verification Team
Bug #95338 marked as duplicate of this one.
[12 May 2019 21:27] MySQL Verification Team
18:17:26 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Linux/Unix version 8.0.16 CE build 14498383 (64 bit)
	Configuration Directory: /home/miguel/.mysql/workbench
	Data Directory: /usr/share/mysql-workbench
	Cairo Version: 1.16.0
	OS: Ubuntu 19.04 x86_64
	CPU: 8x Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (2971.564MHz) - 15,61GiB RAM
No video adapter info available
	Distribution: Ubuntu 19.04
[1 Jun 2019 10:30] Gilles Maitre
Hello Jeffrey,
I had the same (boring) problem. And I solved it with Docker containing Ubuntu 18.04 and the MySQL Workbench. It's working without any problem.
I can send you more infos if needed.
BR,
Gilles
[3 Sep 2019 21:47] Christine Cole
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.18 release, and here's the changelog entry:

The Ubuntu 19.04 distribution did not include MySQL Workbench support as
expected.

Thank you for the bug report.