Bug 11346 - Monodevelop startup problem
Summary: Monodevelop startup problem
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-03-22 06:05 UTC by silverblade1234
Modified: 2014-12-13 12:25 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 Developer Community or GitHub 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 silverblade1234 2013-03-22 06:05:57 UTC
I deleted some cs code files but the tabs in the source editor was still opened. 
The next time I started the monodevelop an exception occured and monodevelop crashed.
When I closed all the tabs it worked fine (Monodevelop 3.05 Windows XP).
Comment 1 Mikayla Hutchinson [MSFT] 2013-03-23 01:41:29 UTC
Do you get this with 4.0.x (Xamarin Studio)?

MonoDevelop 3.x is no longer supported.
Comment 2 Marius Ungureanu 2013-11-24 13:03:14 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days.
Can we put this back into the NEW or CONFIRMED state, or are we still awaiting

If there is no change in the status of this bug over the next two weeks, this
bug will be marked as NORESPONSE.
Comment 3 David 2013-11-27 12:47:29 UTC
Was able to resolve this one on my own - on my end, was related to an improper installation of Gtk causing there to be two different Gtk paths in my %PATH% variable - specifically one to my C:\Program Files... (my %PROGRAMFILES%) and one to my D:\Program Files... (where I told Gtk to install)

After uninstalling Gtk, manually removing the Gtk Paths from the %PATH% variable via the registry, and then reinstalling Gtk, the problem was resolved.
Comment 4 Marius Ungureanu 2014-12-13 12:25:31 UTC
Closing as NORESPONSE.