Description of problem: Plasma 5.3 Kf 5.10: I noticed that many times if you try to use mouse-scroll-wheel on GTK applications, the scrolling will not work until you click on the application or you manually use the scrollbar. One example? Firefox
I can reproduce this with Firefox, which is Gtk3 (in F22), but it works fine with Gimp (Gtk2), so it might be some sort of Gtk3 issue.
Update: with Firefox the scrolling sometimes does not work even when the window has focus. Might be related, might be some Firefox-specific glitch.
*** Bug 1226761 has been marked as a duplicate of this bug. ***
Notified upstream developers too.
Firefox is not really GTK+, it's XUL, GTK+ 3 is only used for rendering.
Some additional info: When wheel in firefox stops working for me, scrolling still works with pushed middle button.
Ok, now it just reverted to original behaviour - resizing. So not 100% deterministic.
(In reply to Kevin Kofler from comment #5) > Firefox is not really GTK+, it's XUL, GTK+ 3 is only used for rendering. No, it's Gtk3 application and process scroll events from Gtk event loop.
related to https://bugzilla.redhat.com/show_bug.cgi?id=983834 ?
Notified upstreem but they think it is Fedora specific. https://bugs.kde.org/show_bug.cgi?id=348270
Fedora specific or not, it's not a KDE bug really. We (KDE) can't just selectively block inputs to GTK only apps (well technically I guess we could but I'm certain that kwin does not). It looks more like broken event processing in GTK and with that there's no reason why that should be a KDE report; especially given that the comments in bug 983834 (from comment #9) suggests it's actually a Gnome issue.
Triaging to gtk3 (as suggested)
Please test other Gtk3 apps (evince, gedit, epiphany). It may also be a bug in Firefox.
Quoting Dan Vratil from the KDE report: "This does not affect only FireFox, I can reproduce with GEdit too [...] it's not triggered only by notifications stealing focus from the window, I can reproduce even when I move the focus manually to another window".
*** Bug 1230942 has been marked as a duplicate of this bug. ***
dvratil tested with openbox, and problem is not present there, so now we suspect kwin, reassigning.
More upstream references, this time gtk3: https://bugzilla.gnome.org/show_bug.cgi?id=737726 https://bugzilla.gnome.org/show_bug.cgi?id=750870
Suggestion from Carlos for diagnosis: please test if this problem disappears with GDK_CORE_DEVICE_EVENTS=1 in the environment
I have tested firefox with GDK_CORE_DEVICE_EVENTS=1 and the problem disappears
From, https://bugs.kde.org/show_bug.cgi?id=348270#c26 , we can certainly implement this workaround in plasma/kwin: kwrite ~/.config/plasma-workspace/env/gtk3-scrolling.sh ----------------- snip -------------- GDK_CORE_DEVICE_EVENTS=1 export GDK_CORE_DEVICE_EVENTS ----------------- /snip --------------
I downloaded Firefox from mozilla.org (i.e. it should be a GTK 2 application) and the issue is the same.
kde-settings-22-11.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/kde-settings-22-11.fc22
Since applying the update referenced in comment 22 this morning, I haven't encountered any problems during regular use of GTK3 applications, so it seems to work around the issue.
(In reply to Fedora Update System from comment #22) > kde-settings-22-11.fc22 has been submitted as an update for Fedora 22. > https://admin.fedoraproject.org/updates/kde-settings-22-11.fc22 I have just given a -1 karma point because I am still experiencing the problem: in Firefox, even if the window is active, sometimes I can manage to scroll the page only after clicking once on the webpage
(In reply to Germano Massullo from comment #24) > (In reply to Fedora Update System from comment #22) > > kde-settings-22-11.fc22 has been submitted as an update for Fedora 22. > > https://admin.fedoraproject.org/updates/kde-settings-22-11.fc22 > I have just given a -1 karma point because I am still experiencing the > problem: in Firefox, even if the window is active, sometimes I can manage to > scroll the page only after clicking once on the webpage My mistake, please ignore comment #24. Yesterday I was updating the package to the testing version but repositories had troubles so the update has not been completed. Today I have forgotten that (so I did the test on the old bugged version)
Package kde-settings-22-11.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kde-settings-22-11.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-10192/kde-settings-22-11.fc22 then log in and leave karma (feedback).
kde-settings-22-11.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
fixed in gtk3 (3.16.5-1.fc22) the workaround referenced in comment 20 are not required yet
kde-settings-22-12.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-f3467dc630
With kde-settings-22-12.fc22, the problem has returned, so the removal of the workaround seems premature, unless there's some other dependency that's supposed to be pulled in that hasn't been in my case.
David, what version of gtk3 are you testing with? (it's supposed to be fixed) rpm -q gtk3
I have gtk3-3.16.7-1.fc22.x86_64 installed. If this is related to the upstream bug I'll link below, the change in question was reverted by Gnome. https://bugzilla.gnome.org/show_bug.cgi?id=750994
Hmm, the Gnome bug referenced in comment 32 may pertain more to bug 1226706, I'm not sure.
kde-settings-22-12.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update kde-settings' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-f3467dc630
kde-settings-22-12.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Good day. After this update I had a problem with the mouse wheel. example in firefox 41.0.1. Temporary downgrade to 22-7
@Race : Same for me ; with all updates applied today and a reboot mouse scrolling is problematic in firefox (and for that matter it seems to cause focus issues with the keyboard as well).
Confirmed the workaround does still seem to be needed, will put it back asap
kde-settings-22-14.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update kde-settings' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-a02471b8c6
kde-settings-23-6.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update kde-settings' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-1528230139
I tested kde-settings-22-14.fc22 and it didn't resolve the problem for me. Steps to reproduce the issue in Firefox are very simple for me: (1) Open Firefox and do something in it. Observe the scroll wheel works. (2) Click on the time in the Plasma panel to bring up the calendar, then minimize it by clicking on the time again. (It's important that you click on the time to minimize, rather than elsewhere on the screen, or this is less reproducible for some reason.) (3) Go back to Firefox and note the scroll wheel no longer works. (4) Go into another application and use the scroll wheel in it. Observe it works fine. (5) Go back to Firefox and note the scroll wheel works again.
It works for me. did you restart your session after updating kde-settings? Though, if you installed plasma-5.4.2 from -testing, you'll have to also get plasma-workspace-5.4.2-4 (or newer) to fix a regression in startkde not importing environment variables properly, https://bodhi.fedoraproject.org/updates/FEDORA-2015-6b26456127 To rule all that out, you can re-test by running firefox as: GDK_CORE_DEVICE_EVENTS=1 firefox
I'd installed all the plasma-5.4.2 packages in testing as of a few days ago. It's news to me I needed to update to plasma-workspace-5.4.2-4 in relation to this issue, I had 5.4.2-1 installed. With 5.4.2-4 installed, I can't replicate the issue using the existing test cases I'd noted, so it indeed appears fixed. I will test further and advise if I find an issue (but I can't imagine how I could), and will revise karma in Bodhi otherwise.
Confirming the updated package works for me, my Bodhi input has been amended accordingly.
kde-settings-22-14.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
kde-settings-23-6.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
With a current GTK3 as of 2018/07, this fix breaks GTK's xinput2 pathway, hence nukes all gestures and touch control for GTK3 applications on plasma, including firefox. I'd suggest to unset GDK_CORE_DEVICE_EVENTS as this workaround isn't used anymore on any other DE/WM, and bars GTK applications to access xinput2. Relevant thread: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/thread/OIYKLSEWALYOBUB6KSDWRIFMOFXSSGCU/
If we do that, the original bug reported here will resurface. So I guess we have to make a choice which is worse.
The original workaround is to cover for a GTK3 bug, but their devs chose to live with it instead of fixing it proper. And not to enforce GDK_CORE_DEVICE_EVENTS to keep xinput2 features. https://bugzilla.gnome.org/show_bug.cgi?id=750994#c8 This fix breaks (gtk3-)touch functionality on equipped devices, and I had a hard time to track this to here. I feel that it should be opt-in, not default.
Ah, found it! > hence nukes all gestures and touch control for GTK3 applications on plasma, including firefox. Yes, this breaks touch support in GTK apps. For anyone with a touchscreen device using Firefox/GTK on Plasma, this is much a bigger problem than mouse wheel events / touchpad scrolling not scrolling the region directly under the cursor (which in any case seems to be broken in GNOME itself). Short version: please un-break Firefox on Plasma.
This workaround breaks xournalpp. I took me a fair amount of time to identify the problem, see https://github.com/xournalpp/xournalpp/issues/2273 After desactivating this ``fix'', my xournalpp works perfectly, and I discovered that firefox was in fact able to react in a meaningful way to my touchscreen: I can zoom and scroll from my fingers. This is exciting time, maybe I'll discover that many more of the programs I use can in fact interpret touch events!
I am no longer experiencing this problem by a long time. Feel free to close the bugreport. Thank you plasma-desktop-5.23.3-1.fc35.x86_64
`unset GDK_CORE_DEVICE_EVENTS` seems still to be needed on Fedora 35 for eg Xournalpp and Firefox in order to make tablet input recognized as a stylus and not a mouse. C.f. * https://bugzilla.mozilla.org/show_bug.cgi?id=1606832 * https://github.com/xournalpp/xournalpp/issues/2273
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.