EER Chart Editor does not display column data and other information

When running mysql-workbench on Ubuntu 14.10, I get unexpected GUI behavior. If I double click on the table in the EER chart editor, I cannot see the list of columns and their attributes. My screen looks like this:

my local workbench screenshot

When I double click on the table in the chart editor, the expected behavior is to list each column in the table along with its attributes in the pink area. I should be able to modify, delete and add columns.

Why am I seeing this behavior and how can I fix it?

-3


source to share


2 answers


I can confirm the behavior you are seeing. It doesn't work on Ubuntu 14.10, and it works on Ubuntu 14.04. I am using mysql-workbench

Wheezy on Debian with expected behavior. So your question caught my attention because it turned out to be a mistake.

I ran it from the command line to see what was on the console. When using the EER Chart Editor with the exemplary model, I was met with a blank area where columns and their attributes should be specified. The console shows these unexpected statements:

(mysql-workbench-bin: 52041): GLib-GObject-WARNING **: trying to add interface (GtkTreeDragDest) to class (gtkmm__CustomObject_16ListModelWrapper) after class__minutes

(mysql-workbench-bin: 52041): GLib-GObject-WARNING **: trying to add interface (GtkTreeDragSource) to class (gtkmm__CustomObject_16ListModelWrapper) after class_init

(mysql-workbench-bin: 52041): Gtk-CRITICAL **: IA__gtk_tree_view_set_model: assertion model == NULL || GTK_IS_TREE_MODEL error (models)

There were many more mistakes, but I narrowed down the list. These statements tell me that an error is thrown when I create a window where the column data is specified. It's not just the column data where this happens, but in most of the panels at the bottom.

I'm working on an open source project that also had issues with Ubuntu 14.10 and it also included Glib assertions where they haven't met before. The Glib developers started adding more assertions to their code to identify software bugs. Perhaps there is something similar here. In the case of a project, I argue that these statements indicate a problem in our project code, and newer versions of Glib have made our code unsuccessful.



With that in mind, I looked at the Ubuntu startup site. There is a title bug reportWorkbench not showing tables or query results in raring

that was opened last year, but people are now identifying an issue with 14.10 (many in the last week). I believe it has something to do with what you see. I also noticed that around three dozen people reported the problem at this time. You can create an account and add yourself to the list of people having a problem.

There is good news and bad news. The MySQL Workbench developers have identified and fixed the issue in their latest builds. The MySQL error message link contains the following:

Posted by developer:

Fixed with the upcoming MySQL Workbench 6.2.4 release, and here's the changelog:

On Linux, the query result view was not populated with libglib version 2.42 and above.

Unfortunately, Ubuntu does not have a patch or work in the official repositories yet. I think you have several options:

  • Do not use mysql-workbench on Ubuntu 14.10 until the bug is fixed and a new version of mysql-workbench is released by Ubuntu.
  • Use an older version of Ubuntu (e.g. 14.04) where it works because it uses an older version of GLib
  • Download the source code and build your own MySQL Workbench 6.2.4 or later when the source is released. At the time of this writing, the source has not been officially released.
  • Download and build from source for MySQL Workbench 6.2.3 using this patch . This patch was provided in the MySQL bug report linked above.
+1


source


There isn't much to say from your image. So I will provide you with some general fixes for this problem:

  • Close and reload MySQL Workbench
  • Right click on your schema (or table) and click "Refresh"
  • Right click on the column box (red part) and click "Refresh"


Sometimes it happens, not all programs are perfect (you have loaded a good amount of data).

0


source







All Articles