Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 18862 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
When XS fails to start, re-scans addins, and tries again, it fails.
ERROR [2014-04-08 11:43:02Z]: Xamarin Studio failed to start. Some of the assemblies required to run Xamarin Studio (for example gtk-sharp)may not be properly installed in the GAC.
System.InvalidOperationException: The main synchronization context has already been set
at MonoDevelop.Core.Runtime.set_MainSynchronizationContext (System.Threading.SynchronizationContext value) [0x00022] in /Users/michael/Mono/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core/Runtime.cs:288
at MonoDevelop.Ide.IdeStartup.Run (MonoDevelop.Ide.MonoDevelopOptions options) [0x001dc] in /Users/michael/Mono/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:130
at MonoDevelop.Ide.IdeStartup.Main (System.String args, MonoDevelop.Ide.Extensions.IdeCustomizer customizer) [0x0008d] in /Users/michael/Mono/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:620
We have tried to check this issue but not sure of the exact steps. Could you please provide us some suggestions/directions so that we can reproduce and check this issue at our end?
This is an internal error that is difficult to reproduce without corrupting the addin database or installing a broken addin.