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.
My system has two monitors, primary to the right, secondary to the left. Running MD in the primary. The debugger inspection windows that come up when hovering during a debug session often appear in the secondary window. I see a number of similar bugs all marked fixed but this is happening to me in a new build:
Installation UUID: feaee481-7c2a-4781-a090-d6228809132d
Mono 2.11.1 ((no/426188e Tue May 15 15:50:21 EDT 2012) (64-bit)
Git revision: dc87d3242eedc2439f023c9e0b8883acfb3d8faa-dirty
Build date: 2012-05-16 14:50:52+0000
Linux pharos 2.6.35-32-generic #67-Ubuntu SMP Mon Mar 5 19:39:49 UTC 2012 x86_64 GNU/Linux
It would help if you could add some debugging to monodevelop/main/src/core/Mono.Texteditor/Mono.TextEditor/Gui/TextEditor.cs in the DoShowTooltip() method.
See if you can figure out where things are going wrong.
It does not happen with sufficient regularity to do that. I would say about 10% of the time the tooltip appears on the other monitor.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.