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 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.
I installed XS 4.0.13 with GTk 2.12.22 and .NET 4.0 3-4times and restarted my pc in between, because XS just didnt start up after installing. At random at the like 5th installation it worked but I could not update anything related to GTK.
After debugging some stuff this error occured (see attachement, sorry its in german! i hope the error code helps for the translation or the understanding). Colleagues suggested reinstallation of XS and GTK and .NET. What I did. But now it is the same issue as before.
After Installing XS and double clicking the .exe my mouse cursor shows that something is loading and after like 1second it just stops and nothing happens.
Created attachment 5289 [details]
the error code i got. sry its in german
What version of Windows? Can you attach the log file from AppData\Local\XamarinStudio-4.0\Logs?
sadly I can not. I completely wiped my pc to create enough space to install Visual Studio. I am sorry but I really needed a plug and play working solution. If you really want the logs I think I can reproduce the problem.
oh and btw this was my forums post. http://forums.xamarin.com/discussion/9604/problems-starting-xamarin-studio-4-0-13#latest
If you have space to install XS that would be great, though I'd guess that if you formatted your PC then the cause of the error may be gone. I'll leave the bug open but NEEDINFO for now, so if you or someone else encounters the issue again we can investigate.
Been over a year here, closing the bug.