Bug 387182 - Scrolling bug with KDE/QT apps, but not with GTK
Summary: Scrolling bug with KDE/QT apps, but not with GTK
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-21 13:30 UTC by Jacob Emery
Modified: 2017-12-11 13:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jacob Emery 2017-11-21 13:30:29 UTC
I have a laptop that I sometimes connect to an external monitor. I had frequent crashed with the external monitor until I changed from OpenGL 2.0 to OpenGL 3.1 in the display settings. Although this is not the reason I am filling this bug report, maybe it could be advised to people that report problems with external displays.
That solved almost all problems, but there is only one left now. It is weird because it happens only on the laptop and only with KDE applications (maybe QT in general), but not with GTK applications. The problem happens with both OpenGL 2.0 and OpenGL 3.1. I didn't test it on wayland. I don't have a complete scaled display, but my fonts DPI is set to 120. I'm using KDE neon 5.11.3.
The problem is: if I scroll with the touchpad or with a mouse on Firefox, it scrolls normally. But if I change application, let's say I click on Okular and I want to scroll, as soon as I start scrolling it goes one page back (so it doesn't start scrolling from where it should be supposed to start), and this is becoming very annoying. If I go back to Firefox again, it will work all right, and if I go back to another KDE app it will start scrolling in a weird way.
Comment 1 Jacob Emery 2017-12-01 09:41:21 UTC
I solved it by installing the latest libinput for KDE neon, so by running:
sudo apt install xserver-xorg-input-libinput-hwe-16.04
Although the default synaptics driver for the touchpad will be loaded like before, now I don't experience the bug any more.