Bug 1226706 - [GTK3] first tick of mouse scroll wheel does not register in certain circumstances
Summary: [GTK3] first tick of mouse scroll wheel does not register in certain circumst...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-31 20:06 UTC by April
Modified: 2017-10-29 13:37 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 11:58:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 750994 0 None None None Never

Description April 2015-05-31 20:06:08 UTC
Description of problem:
After typing a search term in the location bar and pressing enter, search results come up. If you move your mouse wheel down one tick, you should see that the page does not scroll. From the second tick onward, there is no issue with scrolling.

Version-Release number of selected component (if applicable):
38.0, in Fedora 22 only (not in Fedora 20 or 21)

How reproducible:
100%

Steps to Reproduce:
1.type a search term in the location bar and press enter (doesn't seem to matter which search provider you're using; tested with Yahoo and a customized Google URL)
2.move mouse wheel down one tick

Actual results:
Does not scroll

Expected results:
Should scroll slightly

Additional info:
Happens in other circumstances, too, such as navigating by hyperlinks between pages, but I was able to get the most consistent results following the steps listed above.

Comment 1 David H. Gutteridge 2015-06-01 03:18:15 UTC
Which desktop environment are you using? I'm having this problem with Firefox on Fedora 22, but only in KDE Plasma, not in Gnome. I'm wondering if our issues are related.

Comment 2 April 2015-06-01 11:56:41 UTC
I'm using the Mate Desktop environment.

Comment 3 April 2015-06-08 23:14:50 UTC
Same problem in Xfce and LXDE, too.

Comment 4 Martin Stransky 2015-06-09 06:12:45 UTC
Yes, I can see that too.

Comment 5 Jan Horak 2015-06-10 10:00:10 UTC
I can reproduce that also in Epiphany and i3wm.

Comment 6 Jan Horak 2015-06-11 15:03:03 UTC
It seems to be problem with GdkEventScroll struct. The delta_y is set to 0 while direction is GDK_SCROLL_SMOOTH so Firefox or any other GTK3 app don't know the scroll direction  In the next scroll event delta_y is 1 or -1 (depending on user's movement). 

I'm using mouse without free scrolling, only stepped movement. I'm going to recheck in Gnome.

Comment 7 Kamil Páral 2015-06-16 15:39:38 UTC
I have reported a very similar problem against gtk3 here:
https://bugzilla.gnome.org/show_bug.cgi?id=750994

I believe it could be the same core issue.

Comment 8 Jan Horak 2015-06-22 12:53:24 UTC
Moving to gtk3 as long as it is relevant to all GTK3 apps.

Comment 9 LiuYan 2015-07-22 12:15:30 UTC
I updated to gtk3-3.16.6, and it seems this bug is fixed.

https://admin.fedoraproject.org/updates/gtk3-3.16.6-1.fc22?_csrf_token=7cdb4a62f7dd4ac5b9f005f0c88522e6805d7515

Comment 10 April 2015-07-22 14:49:41 UTC
I no longer experience this issue with gtk3 3.16.5-1 and Firefox 39.0-8

Comment 11 Kamil Páral 2015-07-23 08:14:18 UTC
Please read the upstream report. It was fixed, but the fix will be reverted and the devs currently don't know how to fix it in a different way.

Comment 12 April 2015-08-16 15:28:46 UTC
This bug is back in gtk3 3.16.6-1 :-(

Comment 13 Fedora End Of Life 2016-07-19 14:25:23 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 14 Kamil Páral 2016-07-19 15:13:39 UTC
Still valid in F24.

Comment 15 Fedora End Of Life 2017-07-25 18:56:27 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2017-08-08 11:58:37 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.