MySQL Bugs: #20609: Unable to create view

Bug #20609	Unable to create view
Submitted:	21 Jun 2006 14:07	Modified:	5 Aug 2006 7:19
Reporter:	Mathieu Bouchard	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S2 (Serious)
Version:	1.0.6beta and svn	OS:	Linux (debian etch)
Assigned to:		CPU Architecture:	Any

Description:
When starting the workbench, the main window doesn't show and the program doesn't exit (must be stopped by CTRL+C).

I can get to the main window by commenting the line #481 in /usr/local/share/mysql-gui/workbench/lua/Workbench.lua :
local view= grtV.newObj("db.workbench.View", "Main View", "", grtV.toLua(workbench.model._id))

But after that, the workbench is totally unusable since there's no main view.

I'm using debian etch with :
glibmm v2.10.4
gtkmm v2.8.8
libpcre v6.4
mysql client libraries v5.0.22
lua v5.0.2
libglade v2.5.1
libsigc++ v2.0.16
libc v2.3.6
gcc v4.0.3
kernel v2.6.15
french locales
radeon M6 with no dri (xinerama configuration)

The program also fails at the same place on a gentoo laptop with almost the same configuration (kernel 2.6.16, gcc 4.1 and libc 2.4, english locales and a radeom M9 (Mobility 9000) with dri enabled).

During the compilation, I had to remove the java modules.

When the software is starting, I can see two windows appearing for a brief moment.

How to repeat:
# unset LANG
# unset LC_ALL
# DEBUG=1 GRT_VERBOSE=1 mysql-workbench

The output from mysql-workbench

Attachment: mysql-workbench-output.txt (text/plain), 10.27 KiB.

Hi Mathieu and thanks for your problem report.
Please try building from the subversion repository, there are instructions at:
http://forge.mysql.com/wiki/Building_MySQL_GUI_Tools_on_Linux or use packages from http://dev.mysql.com/downloads/workbench/1.0.html

Also, make sure that you don't have any old data files from a previous installation of Administrator in your system. 
Please, inform me of the outcome.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".