MySQL Bugs: #22658: MySql Workbench:Ubuntu 64 bit:Unable to locate theme engine in module

Bug #22658	MySql Workbench:Ubuntu 64 bit:Unable to locate theme engine in module_path
Submitted:	25 Sep 2006 9:45	Modified:	22 Nov 2006 11:16
Reporter:	Nachiketa Shukla	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S1 (Critical)
Version:	1.1	OS:	Linux (Ubuntu Linux 64 bit)
Assigned to:		CPU Architecture:	Any
Tags:	startup error, theme engine, ubuntu, ubuntulooks

Description:
When I want to start mysql-workbench on ubuntu 6.06 linux 64-bit, the following error is seen:

nashukla@solo:/private/software/mysql-gui-tools-5.0$ ./mysql-workbench

(mysql-workbench-bin:8617): Gdk-WARNING **: locale not supported by Xlib

(mysql-workbench-bin:8617): Gdk-WARNING **: cannot set locale modifiers

(mysql-workbench-bin:8617): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks",
The program 'mysql-workbench-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 757 error_code 11 request_code 143 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
nashukla@solo:/private/software/mysql-gui-tools-5.0$

How to repeat:
The error is repeatable everytime I attempt to start mysql workbench on linux.

Thank you for a problem report. Please, try to repeat with the lates tversion of Workbench, 1.1.4 alpha, and inform about the results.

Got Ubuntu Edgy for x86_64 and same problem here when launching the application. Never seen the application running :(

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".