Bug #45308 | Unable to edit tables, view etc, no suitable editor | ||
---|---|---|---|
Submitted: | 3 Jun 2009 15:47 | Modified: | 9 Jul 2009 10:24 |
Reporter: | Aaron Hagopian | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.2.1 / 5.1.12 Beta3 | OS: | Linux |
Assigned to: | Maksym Yehorov | CPU Architecture: | Any |
[3 Jun 2009 15:47]
Aaron Hagopian
[3 Jun 2009 16:11]
Maksym Yehorov
Aaron, thanks for the bug report. Could you please attach all output of workbench from the command line? thanks!
[3 Jun 2009 16:22]
Aaron Hagopian
Output when run from the command line: [ahagopian@schwartz ~]$ mysql-workbench ** (mysql-workbench-bin:25947): WARNING **: :1625: link 'com.mysql.wb.menu.tools.debug' <object app.MenuItem> key=owner could not be resolved ** (mysql-workbench-bin:25947): WARNING **: :1634: link 'com.mysql.wb.menu.tools.debug' <object app.MenuItem> key=owner could not be resolved ** (mysql-workbench-bin:25947): WARNING **: /home/ahagopian/.mysql/workbench/wb_options.xml:321: link 'b036730c-5055-11de-856d-00137287d8b0' <object GrtObject> key=owner could not be resolved
[3 Jun 2009 17:04]
Maksym Yehorov
The point is that Workbench's plugins are installed into /usr/lib64/mysql-workbench, but script in this release searches for them in /usr/lib/mysql-workbench. The issue will be fixed in the next release. For temp workaround you may use symlink from /usr/lib64/mysql-workbench to /usr/lib/mysql-workbench. thanks!
[3 Jun 2009 17:19]
Aaron Hagopian
The symlink makes this version usuable, thanks.
[3 Jun 2009 20:10]
MySQL Verification Team
I couldn't repeat in Ubuntu 9.04 64-bit and 5.2.1.
[3 Jun 2009 20:33]
Maksym Yehorov
The issue is specific to fedora 10 x86_64. Correct version of mysql-workbench script will be available from 5.1.13.
[3 Jun 2009 20:36]
Maksym Yehorov
The issue is specific to fedora 10 x86_64. Correct version of mysql-workbench script will be available from 5.1.13.
[24 Jun 2009 20:08]
Johannes Taxacher
would it be possible to try it again with our currently release version (5.1.14) to check if all issues have been fixed?. thx
[29 Jun 2009 15:08]
Aaron Hagopian
Just tried 5.1.15 and its working as expected. You can close this bug. Thanks
[9 Jul 2009 10:24]
Susanne Ebrecht
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/