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.
Created attachment 700 [details]
Screenshot of the bug.
See attached screeshot
chris says that this has happened when only 1 product is being updated, for example when it was just the mono framework itself.
I can repro this issue, fixing it now.
This has already been fixed and will be part of the next release. Thanks!
This bug hasn't been fixed completely. It just appeared when I tried installing updates from m4a, MD 220.127.116.11 and MT.
*** Bug 2682 has been marked as a duplicate of this bug. ***
I think this only happens when the updater restarts MD.
Not sure if this has anything to do with it, but it might be because I usually opt out of M4A updates.
*** Bug 2539 has been marked as a duplicate of this bug. ***
Fixed. This happened because the updater attempted to terminate MonoDevelop and apps from within the MD app bundle, but did not exclude itself.