You are not logged in.
Pages: 1
I am not able to use my touchscreen to scroll. Can anyone tell me how to make it do that?
This issue has been posted in other questions, but none I found resolved the problem.
I am working with a Lenovo x250 and using KDE's Plasma desktop environment.
Based on the output of xinput list and xinput --list-props 9, I tried enabling Evdev Wheel Emulation, but that didn't do the trick.
The laptop also has a touch pad that can be used to scroll when you use two fingers. Using two fingers on the screen just selects text no matter which application I am running.
I consdidered trying Touchegg, but according to:
https://wiki.archlinux.org/index.php/touchscreen: ". . . on the touchscreen, it's generally better for applications to respond to touch in their own unique ways. Some Qt and GTK applications do that, but they will not be able to if you have Touchegg "eating" the touch events. So, Touchegg is useful when you are running mainly legacy applications which do not make their own use of touch events."
I will note that I have only a few months experience with Linux, so please make your suggestions detailed and don't assume I know too much. I've set up a desktop and a laptop and enjoy Arch's "only install what you need" approach, but it can be tricky to configure a few things.
The output of xinput list:
Virtual core pointer id=2 [master pointer (3)]
Virtual core XTEST pointer id=4 [slave pointer (2)]
ELAN Touchscreen id=9 [slave pointer (2)]
SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)]
TPPS/2 IBM TrackPoint id=13 [slave pointer (2)]
Virtual core keyboard id=3 [master keyboard (2)]
Virtual core XTEST keyboard id=5 [slave keyboard (3)]
Power Button id=6 [slave keyboard (3)]
Video Bus id=7 [slave keyboard (3)]
Sleep Button id=8 [slave keyboard (3)]
Integrated Camera id=10 [slave keyboard (3)]
AT Translated Set 2 keyboard id=11 [slave keyboard (3)]
ThinkPad Extra Buttons id=14 [slave keyboard (3)]
$ xinput --list-props 9
Device 'ELAN Touchscreen':
Device Enabled (138): 1
Coordinate Transformation Matrix (140): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (271): 0
Device Accel Constant Deceleration (272): 1.000000
Device Accel Adaptive Deceleration (273): 1.000000
Device Accel Velocity Scaling (274): 10.000000
Device Product ID (258): 1267, 769
Device Node (259): "/dev/input/event1"
Evdev Axis Inversion (275): 0, 0
Evdev Axis Calibration (276): <no items>
Evdev Axes Swap (277): 0
Axis Labels (278): "Abs MT Position X" (267), "Abs MT Position Y" (268), "Abs MT Touch Major" (264), "Abs MT Touch Minor" (265), "Abs MT Orientation" (266), "Abs MT Tool X" (269), "Abs MT Tool Y" (270), "None" (0), "None" (0)
Button Labels (279): "Button Unknown" (261), "Button Unknown" (261), "Button Unknown" (261), "Button Wheel Up" (144), "Button Wheel Down" (145)
Evdev Scrolling Distance (280): 0, 0, 0
Evdev Middle Button Emulation (281): 0
Evdev Middle Button Timeout (282): 50
Evdev Third Button Emulation (283): 0
Evdev Third Button Emulation Timeout (284): 1000
Evdev Third Button Emulation Button (285): 3
Evdev Third Button Emulation Threshold (286): 20
Evdev Wheel Emulation (287): 0
Evdev Wheel Emulation Axes (288): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (289): 10
Evdev Wheel Emulation Timeout (290): 200
Evdev Wheel Emulation Button (291): 4
Evdev Drag Lock Buttons (292): 0
Last edited by luser (2019-04-02 17:46:58)
luser: an epithet applied by Windows users to linux users
Offline
I have also tried editing /usr/share/X11/xorg.conf.d/10-evdev.conf
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Option "VertTwoFingerScroll" "on"
Driver "evdev"
EndSection
but it doesn't help.
And, now I'm using the libinput driver instead of the evdev driver, and making similar edits to 40-libinput.conf doesn't seem to work any better.
I'm really starting to wonder if it's possible. . .
Last edited by luser (2016-12-28 05:57:02)
luser: an epithet applied by Windows users to linux users
Offline
Use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code
Offline
Hello,
I didn't think it would be necessary when pasting text from a configuration file. It's not really code as it would be in a script.
When I tried prepending "LC_ALL=" as indicated in the link you provided, it appears as literal text when previewed, so I'm really not sure what you would like me to do.
luser: an epithet applied by Windows users to linux users
Offline
I've edited one of your posts. Click the edit button for the same post to see how it is done, then you can fix your first post.
Offline
It turns out that each application must support touch gestures. Unfortunately, that information does not seem to be revealed here: https://wiki.archlinux.org/index.php/Touchscreen
Many common linux apps do not respond to touch gestures. For example, Firefox (my preferred browser) is not configured to do so out of the box. Long after my posting about this issue, I realized that Google Chrome was responding to touch input. More recently, I found that Firefox could be configured to work with it.
https://wiki.archlinux.org/index.php/Fi … n_gestures
Make sure dom.w3c_touch_events.enabled is either set to 1 (enabled) or 2 (default, auto-detect).
Add MOZ_USE_XINPUT2 DEFAULT=1 to /etc/security/pam_env.conf and then logout or reboot your system for the changes to take effect.
So, the problem probably never was that the touch hardware wasn't supported. It was the lack of application support that was the problem. I say "probably" because my original post was some time ago, so there might have been other issues. In any case, for anyone who sees this, make sure you have the application configured to use touch, if that's possible.
luser: an epithet applied by Windows users to linux users
Offline
Pages: 1