[Mono-bugs] [Bug 342572] Using the developer preview installer 1.2.6 mono X11 apps don' t start anymore

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=342572

User fbergman at u.washington.edu added comment
https://bugzilla.novell.com/show_bug.cgi?id=342572#c14





--- Comment #14 from Frank Bergmann <fbergman at u.washington.edu>  2007-12-07 15:02:40 MST ---
Oh ... actually, it is not that there would be a crash, when running the app we
just get: 


Unhandled Exception: System.TypeInitializationException: An exception was
thrown by the type initializer for System.Windows.Forms.XplatUI --->
System.TypeInitializationException: An exception was thrown by the type
initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException:
/Library/Frameworks/Mono.framework/Versions/1.2.6/lib/libgdiplus.dylib
  at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup
(ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&)
  at System.Drawing.GDIPlus..cctor () [0x00000] --- End of inner exception
stack trace ---

  at <0x00000> <unknown method>
  at System.Drawing.Graphics.FromHdcInternal (IntPtr hdc) [0x00000] 
  at System.Drawing.Graphics.FromHdcInternal (IntPtr hdc) [0x00000] 
  at System.Windows.Forms.XplatUIX11.SetDisplay (IntPtr display_handle)
[0x00000] 
  at System.Windows.Forms.XplatUIX11..ctor () [0x00000] 
  at System.Windows.Forms.XplatUIX11.GetInstance () [0x00000] 
  at System.Windows.Forms.XplatUI..cctor () [0x00000] --- End of inner
exception stack trace ---

  at <0x00000> <unknown method>
  at System.Windows.Forms.Application.EnableVisualStyles () [0x00000] 
  at System.Windows.Forms.Application.EnableVisualStyles () [0x00000] 
  at Inspector.MainForm.Main (System.String[] args) [0x00000] 

and this even though the lib is in that folder and running a file command on it
it shows that it is universal. 


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.