Bug #64087 | MySQL Workbench CE 5.2.37 8576 crashed on startup in Fedora 15 | ||
---|---|---|---|
Submitted: | 20 Jan 2012 18:55 | Modified: | 20 Jan 2012 21:34 |
Reporter: | Rene Reitsma | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench | Severity: | S1 (Critical) |
Version: | MySQL Workbench CE 5.2.37 8576 | OS: | Linux |
Assigned to: | CPU Architecture: | Any |
[20 Jan 2012 18:55]
Rene Reitsma
[20 Jan 2012 19:17]
Alfredo Kojima
Try deleting /home/reitsma/.mysql/workbench/wb_options.xml before starting WB
[20 Jan 2012 19:29]
Rene Reitsma
Deleting ~/.mysql/workbench//wb_options.xml did the trick. I'm still getting some feedback: Warning! Can't use connect with timeout in paramiko 1.7.7.1 (George) Ready. ** Message: query.save_edits built-in command is being overwritten ** Message: query.discard_edits built-in command is being overwritten SystemError: null argument to internal routine But the app no longer crashes. Thanks, RR
[8 Jun 2012 15:54]
James Holland
I experienced this exact error on Xubuntu 12.04 64 bit with Workbench 5.2.39. Removing the xmls it was complaining about fixed the crashing at start up, but this warning persists. (mysql-workbench-bin:14142): WARNING **: :38: link 'e663d174-b180-11e1-bf2d-0800278a76de' <object GrtObject> key=owner could not be resolved Let me know if I can provide more information to assist with replication of this bug.