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.
While editing C#, sometime after start up, the editor scroll stops responding to the track pad.
Is this track pad only? I can scroll for hours with a mouse.
Yes, scrolling with a mouse works, but two fingers trackpad scrolling is not working for me on a Macbook with the latest refresh.
Thanks for the info!
I can scroll with the standalone trackpad as well as the Macbook track pad on a late 2010 macbook.
Which exact macbook are you experiencing this with?
Upping the priority/severity in case this is wide-spread.
My track pads work as well btw.
This is a MacBook 13-inch Late 2007 (Intel) running Mac OS X Lion 10.7.5 (11G63)
Now check this out. After installing Mono 2.10.10 scrolling with the track pad also breaks on the regular MonoDevelop release (3.0.6). Reinstalling Mono 2.10.9 fixes the issue in MonoDevelop.
Mitch, any idea?
I am not sure which exact build of 2.10.10 you have been using. Based on comment 5 perhaps I could have you try a new Mono 2.10.11 build?
Unfortunately, I haven't been able to reproduce the scroll issue here on any scroll/trackpad.
Hope we can track it down (no pun intended)!
No, it does not work with build 2.10.11. This build also breaks the functionality in the regular MonoDevelop install.
I want to clarify this affects all of monodevelop not only the code editor.
We still can't reproduce this. Are you using a custom driver? We're going to have to slate this for a later release if we can track it down.
We have someone in the private beta forum reporting this with a mouse:
"Apple USB Mouse (Model A 1152) iMac 21.5 OS/X 10.8.2
Scrolling works with Safari, Xcode, etc. Was working with MonoDevelop but does not since loading the beta.
To my knowledge I am not running any custom utilities or drivers."
We have been able to reproduce this with the A1152 Mighty Mouse. Mitch/Kris, is there any additional info we can provide to help debug it?
*** Bug 9187 has been marked as a duplicate of this bug. ***
Does that mouse show the same problem in e.g. gtk-demo? All my scrolling
devices scroll just fine, I have no idea how to reproduce this :(
Yes, gtk-demo has the same issue.
From the reports it seems like this is only reproducible on older hardware. A 2007 MacBook Pro model is mentioned and the mighty mouse is from around 2007 as well.
I can try the latest GTK+ on my 2006 MacBook or else see if I can borrow a mighty mouse from somebody for testing.
I'm trying to get my hands on a mighty mouse here too, but my resources
of mac-owning friends are rather limited.
My bug was marked as duplicate and added this this one.
I'm having the issue on a late 2011 MacBook Pro with a Logitech Performance MX.
I wrote lots of details about in on the other bug notes: https://bugzilla.xamarin.com/show_bug.cgi?id=9187
Since I have one of these devices here, you're welcome to send me test code or walk me through debugging it on IRC :)
I did some printf debugging and it appears that this mouse emits precise scrolling events but with no phase.
This is confirmed by the apple docs: "Legacy scroll wheel events (say from a Mighty Mouse) and momentum scroll wheel events have a phase of NSEventPhaseNone."
I have emulated a Mighty Mouse by changing the event translation code to always return a NONE phase on scroll events. The following two patches were necessary to get things to work in that case.
Michael: Could you check for me with a Mighty mouse whether this makes things work properly?
Created attachment 3392 [details]
[PATCH 1/2] Never intervene in the event stream if a gesture was never observed
Created attachment 3393 [details]
[PATCH 2/2] Do not start overshooting without observing a gesture
It mostly works, so I landed it.
The one problem is if I use the trackpad to scroll, then the scrollwheel on the mouse stops working. I can think of cases where this might happen, for example someone use using MD on a laptop then gets to their desk and plugs in a mouse & keyboard.
Ah. I did test with the trackpad and a "normal" mouse and that worked. Will also test with a trackpad and an emulated mighty mouse. I think the events get stuck at the same place, since in patch 1 code was added to check whether a start phase has been observed for a trackpad (and thus uses this state too when you start using the mouse which never emitted a state phase). I think we might need to have this flag for every separate device.
*** Bug 10487 has been marked as a duplicate of this bug. ***
I have a similar issue since Xamarin Studio (MD4) on Mac:
When the scrollbar is at top or bottom, mouse wheel doesn't do anything, but Trackpad works.
When the scrollbar is anywhere else other than top or bottom, mouse wheel works (until I reach the top or bottom, of course, after that, I have to use the trackpad again...)
This is happening everywhere in the application
Very VERY annoying...
Forgot to mention: My mouse is a Logitech Performance MX, Logitech Control Center installed
*** Bug 10579 has been marked as a duplicate of this bug. ***
Created attachment 3461 [details]
[PATCH 1/3] Add momentum_phase to GdkEventScroll
Created attachment 3462 [details]
[PATCH 2/3] Never intervene in the event stream for legacy mice
Created attachment 3463 [details]
[PATCH 3/3] Do not start overshooting for legacy mouse scroll events
From the documentation I figured a different way to detect legacy mice. This feels more robust and also simplifies the patches. See the three new attachments.
Michael: could you re-test whether this fixes the issues? The new patches should fix the problem where the scroll wheel becomes stuck after overshooting.
The one issue I see here is that after overshooting I need a few mouse scroll events before the widget actually starts scrolling. I do not know whether this is really a problem or whether this is caused by the way I emulate a "mighty mouse".
Seems to work well. Landed it, now we just need a release :)
*** Bug 10741 has been marked as a duplicate of this bug. ***
Not to split hairs, but I don't know that this resolved my particular issue. For my situation, what seems to work is Thomas' comment (#27 above) where you must click somewhere in between the top and bottom of the text editor.
However, even doing that does not immediately give control back to the mousewheel. It is still unresponsive unless I first scroll down a tad using the Trackpad. In other words, I have to give it a tiny "push" using scroll on the Trackpad. It's quite annoying, and hardly a solution when I didn't have to do this until today. Prior to today, I could use the scrollwheel all the time.
Marlon, we haven't released the fix yet. There'll be a new Mono build (Mono 2.10.12?) at some point with this fix, but unfortunately it's still going through release/QA.
From your description, it really does sound like the same bug - it's known to happen when using Logitech Control Center. Being able to scroll with the mouse after a "push" with the trackpad matches this problem exactly, because it's caused by "legacy" (Apple's word) mice that emit new-style "smooth" scroll events without the same "begin" event that we expect from more modern devices.
I have the same problem. My scroll wheel does not work at all :(
Thank you for the fix. I hope you'll release it soon.
ok, the mouse wheel worked ok for me all the time. Now, after upgrading to latest MonoDevelop (and MacOS) , the mouse wheel stopped working, I cant scroll the code editor, nor any other windows inside MonoDevelop. I am using a standard Apple mouse. As this is really annoying, is there a scheduled day for releasing a patch for this?
I had to plug another mouse for scrolling to work. My logitech mouse doesn't work but my MS arc mouse works fine. Now I have to switch mice when working with MonoDevelop. :(
Scrolling with the trackpad on my mbp works fine.
Are you using the latest MonoDevelop version? For me the problem disappeared after upgrading (MacOS, Apple mouse).
The new MonoDevelop version (4.0.3) doesn't have the scroll problem anymore with my mouse. Except that now it doesn't synch with my Unity projects as well as 4.0. Sometimes is looses the link to the project if the project is updated externally.
As per comment 42, comment 43 and comment 44 this issue does not exist any more.
Hence closing this issue. Marking it as verified.