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.
Steps to reproduce:
1. You'll need the updater to show up when you start MD, so revert to an older version or something
2. Start MD
3. Go to the menu and choose "About MonoDevelop"
4. Note that this will open in front of the updater dialog, but you will not be able to click on the tabs or buttons.
5. Move About dialog out of the way so you can dismiss it
6. About dialog should work now
(Version of MD is 2.8.5)
There seem to be two problems, both likely in GTK:
* other windows can be focused while a modal dialog is active, therefore the main window can be focussed and its about menu command activated.
* and newly created windows can be further forward in the z order than an already open modal window.
We might be able to work around this issue with an event handler on the main window's focus event that woud look for the topmost open modal window and focus it if found.
Probably the same issue, so I'll add it here. If while the "Waiting for debugger" dialog is open sometimes the "Failed to connect" dialog (sorry name is wrong but I dismissed it and of course now can't duplicate) pops up and looks like it has focus, but won't accept click events. You need to close the waiting for debugger dialog first.
*** Bug 2921 has been marked as a duplicate of this bug. ***
I've noticed the same problem in a more annoying way on MacOS X.
1) startup an "old" Xamarin studio...
2) bring up the open-panel before the update-dialog shows
3) ...when the update dialog shows, it can appear behind the open-panel (perhaps because of user-interaction with the open-panel, perhaps not), AND it stops the open-panel from functioning or closing. At this point Xamarin studio appears broken and non-responsive. However, moving the open-panel aside will uncover the install dialog which is blocking the UI.
It would be nice if the update-dialog could either be made non-modal, or be made to always stay on top of other application windows/dialogs.
I am confirming that this issue exists in 4.1.4 (117) exactly as described by David.
*** This bug has been marked as a duplicate of bug 12527 ***