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.
Create an application that fires off some stuff into "Application Output." I used an app that throws an exception and doesn't catch it.
Make the MonoDevelop window fairly narrow, so that when the exception fires and its details are dumped into the "Application Output" pad, you'll need to scroll to see the whole width.
Run the application.
You'll get the MonoDevelop debugger window up, with "Application Output" flashing in the status bar at the bottom.
Click on the flashing "Application Output. You should get the pad, crawling up from the bottom of the window, with colored scroll indicators at bottom and right.
Move the mouse down to the bottom scroll indicator. A scroll bar thumb will appear below the pad.
Move the mouse onto the scroll bar thumb.
Your mouse cursor is now down in the status bar area, so MonoDevelop re-hides the Application Output pad! If you click fast, you can scroll the pad left/right for a couple of tenths of a second while it fades out of existence.
I suspect that the bug is in Gtk-- the thumbs should NOT be letting their mouse messages get to whatever's underneath them-- but it's showing up here.
What distro and GTK+ version?
This sounds to me like a bug in Ubuntu's "overlay scrollbar". The MD autohidden pads hide when they get a "mouse leave" event, indicating that the mouse has gone outside the pad.
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.