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.
See the attached video. It works fine with kwin and metacity.
Created attachment 1397 [details]
Monodevelop 2.8.2 works fine in the same setup.
As I can see this issue is caused by this commit: https://github.com/mono/monodevelop/commit/a5524bf142e4119cab05e132bf08752dd47e1374
When I compile monodevelop from previos one it works fine.
*** This bug has been marked as a duplicate of bug 2985 ***
Actually, I should probably mark the other as a dup of this...
*** Bug 2985 has been marked as a duplicate of this bug. ***
I'm thinking the bug has to be in the DoShowTooltip() in TextEditor.cs because that's the only one that changes the X location.
The other possibility is that getting the location of the window in the DebugValueWindow code is getting invalid values?
I can't reproduce this with Ubuntu 11.10 in VirtualBox with the default window manager (how do I even make it use Compiz?)
Can someone who can reproduce this bug add some Console.WriteLine()'s to figure out what is breaking?
I've tried everything and I just can't replicate it.
Marek is helping me debug this with some CWL's in his MD.
Gtk seems to be giving us wrong allocation *and* window position values in the OnSizeALlocated() callback.
It is telling us that the tooltip window is already at 0,0 when it is not, so we adjust the position to a location that is not up against the edge of the screen.
Interestingly, Compiz seems to be resizing the tooltip window 5 times ,the third time it just randomly says the window is at 0,0
This seems related (windows always show up at 0,0 no matter what): http://bugs.compiz.org/show_bug.cgi?id=5
This one claims Compiz is broken wrt window position reporting (often claiming position being 0,0 when it's not): http://bugs.compiz.org/show_bug.cgi?id=72
Seems very likely to be related.
*** Bug 3499 has been marked as a duplicate of this bug. ***