Bug 408029 - Scrolling in evince when window does not have focus does not work (Xinput2-related)
Summary: Scrolling in evince when window does not have focus does not work (Xinput2-re...
Status: RESOLVED DUPLICATE of bug 394772
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.14.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-28 12:27 UTC by Ralf Jung
Modified: 2020-04-02 14:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Jung 2019-05-28 12:27:47 UTC
SUMMARY
When scrolling in an evince window that does not have focus, nothing happens.

STEPS TO REPRODUCE
1. Open evince, make it cover half the screen.
2. Put some other window on the other half and give it focus.
3. Hover the mouse over the evince window without clicking, and turn the scroll wheel.

OBSERVED RESULT
Nothing happens.


EXPECTED RESULT
It should scroll.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-5-amd64
OS Type: 64-bit

ADDITIONAL INFORMATION
First reported against evince/GTK at https://gitlab.gnome.org/GNOME/gtk/issues/949. However, after discovering that setting GDK_CORE_DEVICE_EVENTS=1 in the environment works around the issue, they concluded that this has something to do with KWin not supporting Xinput2 (?).

Curiously, when I use two-finger scrolling on my touchpad to scroll, evince *does* scroll properly. It's only mouse wheel scrolling that gets "lost", and only when the evince window does not have focus.
Comment 1 Nate Graham 2019-05-28 15:05:49 UTC
Are you using Libinput as your input driver?
Comment 2 Ralf Jung 2019-05-28 15:19:06 UTC
How do I figure that out?  I think I left most everything at the default value.
Comment 3 Nate Graham 2019-05-28 15:23:48 UTC
just search for whether or not Libinput is installed. That should be enough.

apt search libinput | grep -i installed
Comment 4 Ralf Jung 2019-05-28 15:31:22 UTC
Looks like it is:

libinput-bin/testing,unstable,now 1.12.6-2 amd64 [installed,automatic]
libinput10/testing,unstable,now 1.12.6-2 amd64 [installed,automatic]
xserver-xorg-input-libinput/testing,unstable,now 0.28.2-2 amd64 [installed,automatic]
Comment 5 Nate Graham 2019-05-28 15:48:12 UTC
Thanks for the info.
Comment 6 Vlad Zahorodnii 2019-06-07 10:58:59 UTC
Perhaps the libinput driver has nothing to do with this.

For some reason, GTK clients do not like replayed events.
Comment 7 Andreas Sturmlechner 2020-04-02 12:21:45 UTC
This is likely a duplicate of bug 394772.
Comment 8 Nate Graham 2020-04-02 14:47:02 UTC
Yep.

*** This bug has been marked as a duplicate of bug 394772 ***