Description of problem: When replying to mail, the scroll wheel on the mouse doesn't work. Scrolling received mail with the scroll wheel works. Scrolling with the keyboard in compose works. When replying to a message, and quoting that message the scroll wheel does work. When replying with a blank quote, or deleting the entire quote, the scroll wheel does not work. Composing a new blank message does allow scrolling. Version-Release number of selected component (if applicable): Evolution 3.8.1 evolution-3.8.1-1.fc19.x86_64 How reproducible: Reply to a message. Delete the quote (if present.) Type some text, enough to get a scroll bar. Scroll with a scroll wheel. Steps to Reproduce: 1. Receive a mail. 2. Reply to said mail. 3. Delete the entire quote. 4. Type some text (more than the window size) 5. Scroll wheel. Actual results: 6. Message does not scroll. Expected results: 6. Message scrolls. Additional info:
Thanks for a bug report. I can reproduce this with gtk3-3.8.1-1.fc19, when I get to a state when the mouse wheel doesn't work, then the only way is to use the wheel when mouse pointer hovers above the scrollbar. It seems to me like a regression in gtk3, because the same steps work fine with gtk3-3.6.4-1.fc18, with basically the same gtkhtml3 package (4.6.4-1 in Fedora 19 for me). I'm moving this bug to gtk3, at least to get some explanation what change in there could cause this regression. Note there will be an update for Fedora 19 with 3.8.2 release with this week (most likely), which also includes gtkhtml3-4.6.5. It doesn't include any particular fix for this, but it also doesn't contain any change which would cause this, except of gtk3 version change.
It is indeed still happening. evolution-3.8.2-1.fc19.x86_64 gtk3-3.8.2-1.fc19.x86_64 gtkhtml3-4.6.5-1.fc19.x86_64
this was a bug in libXi that is fixed in current updates
Still a problem with libXi-1.7.1-4.20130524git661c45ca1.fc19 updated today.
Also still a problem with libXi-1.7.2-1.fc19.x86_64. Please reopen this bug report.
This [1] is a corresponding upstream bug report. Probably an interesting comment there is [2]. That said, it's not only about libXi, or at least not directly, from my point of view. [1] https://bugzilla.gnome.org/show_bug.cgi?id=699574 [2] https://bugzilla.gnome.org/show_bug.cgi?id=699574#c16