SUMMARY While scrolling up/down, I get that pressing the CTRL key will zoom the konsole window, however, this should only happen while actively using the mouse/touchpad. When using a touchpad to 'flick' up the window, if you press CTRL after the flick, the text is zoomed. This is very frustrating. STEPS TO REPRODUCE 1. Open console and type dmesg to get the kernel output 2. Scroll to the top of the output by flicking the touchpad 3. Press CTRL-SHIFT-F with the intention of starting a find command OBSERVED RESULT Text is zoomed EXPECTED RESULT Find command is launched / text is not zoomed SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: 18.12.0 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Not 100% sure, but this is unfixable* (at Konsole level) - the kinetic scrolling (flick) is implemented in input driver/lib - it just sends additional scroll events as if real scrolling was happening; they are indistinguishable from normal scrolling in a Qt app. * - in legit way. Some hacks like ignoring ctrl-does-zoom X ms after scroll event handled as scrolling might work for some cases.
It is actually fixable in Konsole. Here's how Kate fixed it: https://cgit.kde.org/ktexteditor.git/commit/?id=f51befdc80b1a8dfd65b800b3b10dba97d10a2cb
Can confirm that this occurs on Konsole. This also currently occurs on Firefox, Dolphin, WPSOffice and SoftmakerOffice, just some examples I tested. An easy way to reproduce this on Dolphin is navigating to /etc with maximum zoom and testing with scrolling downwards. Nate also once mentioned that this occurs due to an X11 synaptics driver issue here on this Okular bug report: https://bugs.kde.org/show_bug.cgi?id=353330#c1 Should I submit a bug report for Dolphin as well? To me it seems a bit redundant having the same bug report across several KDE applications (Okular, Kate, Konsole, Dolphin) that is seemingly caused by an upstream issue, but this would need at least a temporary fix on KDE applications until libinput is fully implemented, I think.
Confirmed by a second user and suggestion for fix provided by Nate via Kate, unfortunately the cgit server no longer exists and the commit id doesn't match any in Gitlab so some digging will need to be done.
https://commits.kde.org/ktexteditor/f51befdc80b1a8dfd65b800b3b10dba97d10a2cb See https://community.kde.org/Infrastructure/GitLab#Generating_.22eternal.22_URLs_to_commits_or_objects_in_a_repository
A possibly relevant merge request was started @ https://invent.kde.org/utilities/konsole/-/merge_requests/268
Git commit 1af0a1d53399a4a0b3ccdd043cc9a7db30e659e0 by Tomaz Canabrava, on behalf of Carlos Alves. Committed on 14/11/2020 at 14:08. Pushed by tcanabrava into branch 'master'. Fix scrolling with ctrl+mouse wheel Based on commit f51befdc from kde/ktexteditor by René J.V. Bertin FIXED-IN: 20.12 M +11 -1 src/terminalDisplay/TerminalDisplay.cpp https://invent.kde.org/utilities/konsole/commit/1af0a1d53399a4a0b3ccdd043cc9a7db30e659e0
*** Bug 432002 has been marked as a duplicate of this bug. ***
With Konsole 20.12.3 and a touchpad, the issue persists. Cannot reproduce with Kate, so seems to be a Konsole bug.
And you are using the Synaptics driver with inertia turned on, right?
Right, but it's not a problem for other apps.
...Because other apps implement special code to reject auto-generated scroll events following the release of the ctrl key. :) This is exactly why the Libinput maintainer decided not to include the feature and instead delegate inertial scrolling to toolkits. IMO the real bug is that Qt scrollviews don't support it out of the box the way GTK ones do. Synaptics' inertia feature is just working around that bug, and it requires apps to work around the bugs created by doing this.
how do you even have inertia scrolling on linux/kde plasma?! i've been trying for weeks to get it working to no avail, i'm on fedora 37 kde plasma 5.27 wayland, did you manually configure inertia scrolling or it just is by default when you install linux? if manually how did you do it?
The old unmaintained Synaptics touchpad drivers expose a driver-level scroll inertia feature that's the cause of this issue.