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.
Version 2.8.5 of MonoDevelop for Mac
OSX Lion System Version: Mac OS X 10.7.2 (11C74) Kernel Version: Darwin 11.2.0
When the Properties Pad displays, the properties appear for a split second and then disappear.
Steps to reproduce:
1. From the Solution Pad right click any item and select Properties.
2. Property Pad displays, shows the properties for a split second and then the properties disappear.
The Properties Pad remains open and there is no crash or anything. Just an empty property pad.
3 months later and still marked as "New". Guess the use of the Property pad isn't important.
Sorry, but I couldn't reproduce the problem. Also, the core property pad features for the solution pad are accessible from the context menu, so the only thing bitten badly by this would be the GTK# designer.
What layout of pads do you have - position, autohide status, etc? Can you try with Mono 2.10.9 from the beta channel? It has a new version of the GTK+ UI toolkit that may fix issues like this.
I've only hit this in the Gtk# designer, and it seems to only happen to me when I try to pin the Properties Pad.
I typically get an NRE exception dialog and then the properties pad fails to display.
*** This bug has been marked as a duplicate of bug 25991 ***