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 362 [details]
Image for Exception
Steps to Reproduce:
1.Go to Start>>MonoDevelop.
2.Click MonoDevelop window.
3.Open .cs file.
4.Press ctrl+M+P keys from the keyboard.
Actual Result:Exception occurred when user press Ctrl+M+P keys.
Refer to the attached screenshot.
Expected Result:Exception should not be occurred.
Windows 7 (32 bit)
Created attachment 363 [details]
possibly a win32 gtk bug (cannot reproduce under MacOS by using keybindings for Print)
Is this simply a printing bug in Gtk on windows? Does invoking 'Print' from the monodevelop menu using the mouse have the same problem?
The print menu item had been disabled on Windows because it requires COM STA (there is another bug tracking non-working printing), however the command had not been disabled properly - it could still be activated from the keyboard shortcut. I fixed this soon after 2.8.4.
Actually, I think the fix made it into 2.8.4.
It is still occurring for MonoDevelop 188.8.131.52.
It is still occurring for MonoDevelop 184.108.40.206
Now the shortcut command for print (ctrl+M+P)option is not working.
Please suggest if we can close this issue.
As per comment, printing has been disabled on windows. This is expected behaviour.
As per the above comments, closing this issue.