MySQL Bugs: #25827: problem launching MySql Workbench

Bug #25827	problem launching MySql Workbench
Submitted:	24 Jan 2007 13:43	Modified:	26 Jan 2007 9:28
Reporter:	Nicolas Reinecke	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S2 (Serious)
Version:	1.1.9alpha	OS:	Linux (Linux)
Assigned to:		CPU Architecture:	Any

Description:
MySql gui tools 5.0r9, Fedora Core 6

gui: "The GRT environment for the Workbench could not be initialized.
Please verify your installation."

terminal:
"$ mysql-workbench
** (mysql-workbench-bin:17659): WARNING **: Error getting color presets."

DEBUG=1 mysql-workbench
** Message: MySQL Generic Runtime Environment 2.0.12

** Message: 
Type 'help' or '?' for help. Type 'quit' to exit the shell.

** Message: Lua Shell initialized.

** Message: Registered 14 struct definitions

** Message: Loading Lua modules...
** Message: Registered 10 Lua modules

** Message: Initializing C++ loader...
** Message: Registered 0 struct definitions

** Message: Registration ok
** Message: Could not load lua module /usr/share/mysql-gui/workbench/lua/WorkbenchImport.lua: /usr/share/mysql-gui/workbench/lua/WorkbenchImport.lua:58: malformed number near `1.5'

** Message: Could not load lua module /usr/share/mysql-gui/workbench/lua/Workbench.lua: /usr/share/mysql-gui/workbench/lua/Workbench.lua:1686: malformed number near `9999999999.0'

** Message: Registered 1 modules

** Message: Invalid function calling Workbench.registerEditors
** Message: Invalid function calling Workbench.getColorPresets

** (mysql-workbench-bin:17844): WARNING **: Error getting color presets.
** Message: Invalid function calling Workbench.initWorkbench

also reported at Bug #18028, #19380

How to repeat:
$ LANG=de_DE mysql-workbench -> error
$ LANG=de_DE.UTF-8 mysql-workbench -> error
$ LANG=C mysql-workbench -> works

$ LANG=DE mysql-workbench

(mysql-workbench-bin:17765): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Marked as duplicate of bug #19380