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 3776 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
Summary says it all. Regardless of the last position MonoDevelop was closed in, it always starts maximized on the secondary monitor.
I've searched around, and I found this guy who has the same problem from two years ago:
The problem doesn't seem to have changed since then. I imagine all that's needed is a simple check to ensure the window spawns on the primary monitor. It's very annoying to open it and have to drag it to the primary monitor each time, but it's not critical.
OS: Windows 7 x64
This is a GTK issue, unrelated to MonoDevelop.