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.
Standard MonoDevelop install on Ubuntu 12.04. Created an empty Gtk# 2.0 solution, ran it just to make sure that compilation was working and so on, the pressed F1 to see if MonoDoc had installed OK. It was there, but when I closed the window I got the error message, "MonoDoc exited with a exit code = 134". (This also triggered Ubuntu's irritating error-reporting system dialog, but never mind that since it never works anyway.)
There's the cosmetic problem (in English, it should be "an exit code" rather than "a exit code") and the irritating but presumably harmless matter of the error code.
Expected behaviour: MonoDoc window should close without complaint.
Actual behaviour: foolish error message.
Pull request to fix exit issue already applied: https://github.com/mono/mono-tools/commit/8f8dbe245b3fb7f69b95234c6098739c4cec7000
Pull request to fix error message pending: https://github.com/mono/monodevelop/pull/213
Pull request to fix error message applied:
Thanks, the patches have been applied now.