Bug 687 - Fon't not showing in GUI with MonoDevelop
Summary: Fon't not showing in GUI with MonoDevelop
Status: RESOLVED DUPLICATE of bug 637
Alias: None
Product: Runtime
Classification: Mono
Component: packaging ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- critical
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-09-09 14:40 UTC by Colin Faulkingham
Modified: 2011-12-09 11:58 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Colin Faulkingham 2011-09-09 14:40:19 UTC
See this example screenshot http://www.twitpic.com/6ie4k4

I installed MonoDevelop 2.6

I also installed the MonoFramework 2.10.5 (SDK)

OSX 10.6.8
Comment 1 Colin Faulkingham 2011-09-09 15:07:04 UTC
I tried to install the MonoFramework 2.10.3 (SDK) and it did the same thing. 

I thought I saw somewhere that X11 might need to be installed so I installed it. Now when I try to launch MonoDevelop 2.6 I get the following error.

9/9/11 2:00:20 PM com.apple.launchd.peruser.501[218]	([0x0-0x25025].com.ximian.monodevelop[570]) Exited with exit code: 255
Comment 2 Colin Faulkingham 2011-09-09 16:40:34 UTC
I was able to fix my problem by fully uninstalling the MonoFramework 2.10.5 and 2.10.3 and installing 2.10.4
Comment 3 Jeffrey Stedfast 2011-12-09 11:58:46 UTC

*** This bug has been marked as a duplicate of bug 637 ***