Bug #64251 workbench not working at all on window 7
Submitted: 7 Feb 2012 15:34 Modified: 9 Feb 2012 16:17
Reporter: Mujtaba Faizan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.37 CE OS:Windows (window 7)
Assigned to: CPU Architecture:Any
Tags: Workbench error, workbench not starting, workbench not working

[7 Feb 2012 15:34] Mujtaba Faizan
Description:
I install the workbench but when I try to start it its not working only report bug window displaying.

How to repeat:
its keep repeating

Suggested fix:
design new workbench for win 64bit
[7 Feb 2012 17:48] Valeriy Kravchuk
What exact version of Workbench, 5.2.x, do you use? 5.2.37 is the latest.
[7 Feb 2012 20:53] Mujtaba Faizan
hello,
I'm using 5.2.37 CE
[8 Feb 2012 1:38] MySQL Verification Team
I don't have this issue on my Windows 7 Ultimate 64-bit box:

MySQL Workbench CE for Windows version 5.2.37  revision 8576

Configuration Directory: C:\Users\miguel\AppData\Roaming\MySQL\Workbench

Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 3.3.11399 Compatibility Profile Context

OS: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit

CPU: 4x AMD Phenom(tm) 9650 Quad-Core Processor, 8.0 GiB RAM

Active video adapter (0): ATI Radeon HD 4650

Installed video RAM: 1024 MB

Current video mode: 1920 x 1080 x 4294967296 colors

Used bit depth: 32

Driver version: 8.930.0.0

Installed display drivers: aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atiumdag,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll

Current user language: Portuguese (Brazil)
[8 Feb 2012 4:46] Valeriy Kravchuk
Please, find and send the wb.log file that Workbench maintains. It may have some information about startup problem.
[8 Feb 2012 21:04] Mujtaba Faizan
00:52:25 [   Info][      wbprivate]: Starting tunnel
00:53:29 [   Info][               ]:     
00:53:30 [   Info][               ]:     
00:54:32 [   Info][               ]:     
00:54:32 [   Info][               ]:     
-------------------------
seems to be nothing in wb.log file only the above information is present. 
I'm using window 7 professional and MySql workbench used to work on this system but since I install the new version its stopped working.
[8 Feb 2012 21:09] Mujtaba Faizan
I tried to debug it with Visual Studio 2010 and when I look into the inner Exception Message I found this message. 
Font 'Bitstream Vera Sans Mono' does not support style 'Regular'.

System.ArgumentException was unhandled
  Message=Font 'Bitstream Vera Sans Mono' does not support style 'Regular'.
  Source=System.Drawing
  StackTrace:
       at System.Drawing.Font.CreateNativeFont()
       at System.Drawing.Font.Initialize(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont)
       at System.Drawing.Font.Initialize(String familyName, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont)
       at System.Drawing.Font..ctor(String familyName, Single emSize)
       at MySQL.Forms.TextBoxImpl.set_monospaced(TextBox* self, Boolean flag)
       at MySQL.MCallback2<void\,mforms::TextBox \*\,bool>.cpp_callback(TextBox* a1, Boolean a2)
       at wb.WBContextUI.init(WBContextUI* , WBFrontendCallbacks* , WBOptions* )
       at MySQL.Workbench.WbContext.init(AppImpl application, WbOptions options, VoidStrUIFormDelegate create_main_form_view)
       at MySQL.GUI.Workbench.Program.Main(String[] Args)
  InnerException: 
-------------------------------------
this might help......
[8 Feb 2012 21:22] Mujtaba Faizan
Oh I found the solution I download Bitstream Vera Sans Mono from http://www.dafont.com/bitstream-vera-mono.font and replace the current Bitstream Vera Sans Mono font with the downloaded one and start the workbench and its working now!!! :-)
[9 Feb 2012 16:17] Mike Lischke
The problem is known and related to this font. We will add some more error catching so at least WB doesn't crash, just because of an unusual font. The error will be logged (wb.log) but is of course not as visible as the exception then.

For future reference: for more useful log ouput start WB with any of the more verbose log levels:

-log-level=debug1 (or 2/3, with increasing verbosity). On Linux and Mac the option is --log-level=...