libinput issueshttps://gitlab.freedesktop.org/libinput/libinput/-/issues2021-05-31T16:26:40Zhttps://gitlab.freedesktop.org/libinput/libinput/-/issues/615Disable while typing does not work on Asus ROG Zephyrus G15 20212021-05-31T16:26:40ZNeev ParikhDisable while typing does not work on Asus ROG Zephyrus G15 2021## Summary
When using the touchpad on the Asus Rog Zephyrus G15 2021, it is nearly unusable when disabled while typing (DWT) is on. With it off, it is easier to type. However these issues are only seen when using libinput on X11, and on...## Summary
When using the touchpad on the Asus Rog Zephyrus G15 2021, it is nearly unusable when disabled while typing (DWT) is on. With it off, it is easier to type. However these issues are only seen when using libinput on X11, and on Wayland it disappears (only appearing occasionally and not being nearly as bad). I was trying to debug touch size or touch pressure but this trackpad does not report either, so I was not able to address the problem that way. Any tips on what to do, if I can write a quirks file to address this? It uses a Microsoft precision driver on windows.
<!--
Summarize the bug encountered concisely. See
https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html for
detailed instructions to report bugs
-->
## Steps to reproduce
Use the specified hardware with libinput on X11 (I use Arch with gnome and i3).
<!-- How to reproduce the issue on a developer machine - this is very important -->
## Required information
<!-- Note: if your libinput version is older than the current stable version,
please reproduce with a current version instead -->
- libinput version: 1.17.2
- hardware information:
- ASUS Rog G15 2021
- ASUE1209:00 04F3:319F Touchpad
- `measure touchpad-size` output:
```
~ » sudo libinput measure touchpad-size 128x83 /dev/input/event8
Kernel specified touchpad size: 128.7x83.2mm
User specified touchpad size: 128.0x83.0mm
Kernel axis range: x [ 0..3990], y [ 0..2578]
^C
Detected axis range: x [ 15..3990], y [ 76..2575]
Resolutions calculated based on user-specified size: x 31, y 30 units/mm
Suggested hwdb entry:
Note: the dmi modalias match is a guess based on your machine's modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA503QR.404:bd02/08/2021:br5.19:efr3.5:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA503QR_GA503QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA503QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
Please verify that this is the most sensible match and adjust if necessary.
-8<--------------------------
# Laptop model description (e.g. Lenovo X1 Carbon 5th)
evdev:name:ASUE1209:00 04F3:319F Touchpad:dmi:*svnASUSTeKCOMPUTERINC.:*pnROGZephyrusG15GA503QR_GA503QR**
EVDEV_ABS_00=15:3990:31
EVDEV_ABS_01=76:2575:30
EVDEV_ABS_35=15:3990:31
EVDEV_ABS_36=76:2575:30
-8<--------------------------
Instructions on what to do with this snippet are in /usr/lib/udev/hwdb.d/60-evdev.hwdb
```
- `libinput record` output: do not paste, **attach** the file
- `libinput debug-events --verbose` output: do not paste, **attach the file**
<!--
Paste any other relevant logs - please use code blocks (```) to format
console output, logs, and code as it's very hard to read otherwise.)
Do not paste logs longer than 10 lines, **attach** those instead.
If your libinput record is longer than 5-10s, we will not be able to process
it.
-->[record.txt](/uploads/2e272f3b6bdaf3724889a851becea6d9/record.txt)[debug.txt](/uploads/760dac6a44c0382102ab8f5739bd438a/debug.txt)https://gitlab.freedesktop.org/libinput/libinput/-/issues/579Mouse acceleration works at 150dpi, but doesn't seem to work at 550dpi+2021-03-15T23:53:42ZTrickMeMouse acceleration works at 150dpi, but doesn't seem to work at 550dpi+Linux Mint 20.1 Cinnamon, Kernel 5.8, X.Org 1.20.9, Xserver-xorg-input-libinput 0.29.0
Mouse acceleration works at 150dpi, but doesn't seem to work at 550dpi+.
Changing mouse sensitivity doesn't work, but it might just be a Cinnamon-s...Linux Mint 20.1 Cinnamon, Kernel 5.8, X.Org 1.20.9, Xserver-xorg-input-libinput 0.29.0
Mouse acceleration works at 150dpi, but doesn't seem to work at 550dpi+.
Changing mouse sensitivity doesn't work, but it might just be a Cinnamon-specific issue.https://gitlab.freedesktop.org/libinput/libinput/-/issues/551Thinkpad E14 Gen2: Cursor jumps2021-01-05T13:56:16ZShaleen jainThinkpad E14 Gen2: Cursor jumps## Summary
While using the touchpad on the Thinkpad E14 Gen 2 with the AMD CPU, frequently there are sporadic cursor jumps of over more than 1 cm in gap.
Checking the journalctl these jumps are not detected by libinput and are not igno...## Summary
While using the touchpad on the Thinkpad E14 Gen 2 with the AMD CPU, frequently there are sporadic cursor jumps of over more than 1 cm in gap.
Checking the journalctl these jumps are not detected by libinput and are not ignored.
## Steps to reproduce
Casually use the touchpad on an Thinkpad E14 gen2
## Required information
<!-- Note: if your libinput version is older than the current stable version,
please reproduce with a current version instead -->
- libinput version: 1.16.4-1
- hardware information: Lenovo Thinkpad E14 Gen 2 AMD
- `libinput record` output: [touchpad-main.yaml](/uploads/27c4c9c392f51c86a1c038ff05636a9c/touchpad-main.yaml)
- `libinput debug-events --verbose` output: [debug_events.txt](/uploads/32b5a3bd038499df4b0046a1cf5b0d97/debug_events.txt)
<!--
Paste any other relevant logs - please use code blocks (```) to format
console output, logs, and code as it's very hard to read otherwise.)
Do not paste logs longer than 10 lines, **attach** those instead.
If your libinput record is longer than 5-10s, we will not be able to process
it.
-->https://gitlab.freedesktop.org/libinput/libinput/-/issues/525Genius G-Pen 560 pen tablet fails to detect pen up randomly2020-10-02T05:54:08ZConstantin MikhaylenkoGenius G-Pen 560 pen tablet fails to detect pen up randomlyNote: the device wasn't detected at all at first, I had to add the following to hwdb:
```
# G-Pen 560
evdev:input:b0003v0458p5003*
EVDEV_ABS_00=::75
EVDEV_ABS_01=::75
```
(Will submit it upstream later)
## Summary
Sometimes when li...Note: the device wasn't detected at all at first, I had to add the following to hwdb:
```
# G-Pen 560
evdev:input:b0003v0458p5003*
EVDEV_ABS_00=::75
EVDEV_ABS_01=::75
```
(Will submit it upstream later)
## Summary
Sometimes when lifting the pen, it's still treated as pressed and will draw unwanted
lines when just moving the pen above the tablet.
From libinput debug-events it seems that when it happens, there's no tool tip up
event, and instead it happens before the next down event.
## How to reproduce
Try drawing lines consecutively in a `|||||||` formation. Sometimes the line will continue after
lifting the pen and the lines will be connected like `|||N||||N|||`
See the screen recording:
![Запись_экрана_от_12.09.2020_20_22_19](/uploads/a24a186942e9830c2035cdfeb3c26231/Запись_экрана_от_12.09.2020_20_22_19.webm)
All lines here were drawn the same way, lifting the pen after each one. This is same recording as the attached debug-events output.
## Required information
- libinput version: 1.16.1
- hardware information: Genius G-Pen 560 pen tablet
- `libinput record` output: [recording.yml](/uploads/3a462f558d870354d5d100b34c107cc5/recording.yml)
- `libinput debug-events --verbose` output: [debug-events4](/uploads/7f0f1b5cd88c3a7e2174e2e0eb900d3d/debug-events4)
[udevadm-info](/uploads/ca7907c4dce277673195ecca53e349a2/udevadm-info)
I also noticed that if you don't press the pen too hard, it generates non-zero
pressure events before `BTN_TOUCH` is pressed, this might be related.https://gitlab.freedesktop.org/libinput/libinput/-/issues/466libinput 1.14.1 double palm detection is flapping on HP Pavilion 15 Skylake b...2020-09-27T18:41:59ZRyan C. Underwoodlibinput 1.14.1 double palm detection is flapping on HP Pavilion 15 Skylake bc010nr```$ sudo libinput measure touchpad-pressure
[sudo] password for nemesis:
Using Synaptics TM3114-001: /dev/input/event12
Ready for recording data.
Pressure range used: 30:25
Palm pressure range used: 130
Thumb pressure range used: 255...```$ sudo libinput measure touchpad-pressure
[sudo] password for nemesis:
Using Synaptics TM3114-001: /dev/input/event12
Ready for recording data.
Pressure range used: 30:25
Palm pressure range used: 130
Thumb pressure range used: 255
Place a single finger on the touchpad to measure pressure values.
Ctrl+C to exit
```
Using this touchpad and this version, individual palms are correctly labeled, but when both palms are present, the "palm" flag is flickering and the pressure is flapping between a three digit and a two digit number. Removing either palm causes convergence to a detected palm for the remaining hand. Since palm detection is not working correctly for two palms, it causes problems in applications.
I will attempt to work around this by increasing the exclusion zones but it would be ideal if the firmware labeling worked correctly in this case.https://gitlab.freedesktop.org/libinput/libinput/-/issues/417Memory leak caused by libinput_udev_assign_seat2021-06-10T00:41:40ZSimon KrogmannMemory leak caused by libinput_udev_assign_seat## Summary
When using `libinput_udev_assign_seat` I get the following memory leak:
```
=================================================================
==125549==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 56 byte(s) in...## Summary
When using `libinput_udev_assign_seat` I get the following memory leak:
```
=================================================================
==125549==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 56 byte(s) in 1 object(s) allocated from:
#0 0x7f0fd5d06cd8 in __interceptor_calloc /build/gcc/src/gcc/libsanitizer/asan/asan_malloc_linux.cc:153
#1 0x7f0fd5bcdc33 (/usr/lib/libinput.so.10+0x20c33)
SUMMARY: AddressSanitizer: 56 byte(s) leaked in 1 allocation(s).
```
Might be related to #270
## Steps to reproduce
Compiling and running the following code with `-fsanitize=address` in g++ 9.2 consistently gives me the error message above.
```
#include <fcntl.h>
#include <libinput.h>
#include <unistd.h>
int open_restricted(const char *path, int flags, void *)
{
return open(path, flags);
}
void close_restricted(int fd, void *)
{
close(fd);
}
const struct libinput_interface interface = {open_restricted, close_restricted};
int main(void)
{
auto udev = udev_new();
auto li = libinput_udev_create_context(&interface, nullptr, udev);
libinput_udev_assign_seat(li, "seat0");
libinput_unref(li);
udev_unref(udev);
}
```
## libinput version you encountered the bug on
1.15.0
## Hardware information:
XPS 13 7390 2-in-1 Notebook
## Other log output:
Nonehttps://gitlab.freedesktop.org/libinput/libinput/-/issues/405ThinkPad E585 choppy and not smooth at all2020-03-21T10:32:31ZTorunaiThinkPad E585 choppy and not smooth at all## Summary
<!--
Summarize the bug encountered concisely. See
https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html for
detailed instructions to report bugs
-->
After installing an additional 8GB of RAM and a spare SSD ...## Summary
<!--
Summarize the bug encountered concisely. See
https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html for
detailed instructions to report bugs
-->
After installing an additional 8GB of RAM and a spare SSD to my ThinkPad E585, I decided to finally install a Linux distribution and use it as my daily driver from now on. Though I was surprised to see that the touchpad didn't work as intended. It feels unnatural and looks as if it skips frames as it moves. I wouldn't use the word "jumpy" as the behavior is what I believe is called "choppy". The trackpoint also shows the same behaviour on Linux, while they both work smoothly and show no signs of skipping or choppiness under Windows 10.
## Steps to reproduce
Does not need any additional steps as the touchpad does not work as intended. Tap was also enabled by default.
## libinput version you encountered the bug on
1.14.1 as reported by the following command:
`libinput --version`
Came installed with Pop!_OS 19.10
Edit: Also tested on 1.14.901.
## Hardware information:
ThinkPad E585 (20KV000ATX)
## Other log output:
- `libinput record` output: <!-- attach file here -->[touchpad.yaml](/uploads/ff63fe9e655db233b1ef0217d254f075/touchpad.yaml) [trackpoint.yaml](/uploads/64165e2254473f4e8fa0aaa5a418ecec/trackpoint.yaml)
- `libinput debug-events --verbose` output: [debug-events.log](/uploads/1fdd63e1723dd1a199f9e0bf0d4af474/debug-events.log)
- `touchpad-edge-detector 98x65 /dev/input/event6` output: [touchpad-edge-detector.txt](/uploads/6e9202f19ff4f5ecc403cca8e088f787/touchpad-edge-detector.txt)
- `udevadm info` output: [udevadminfo-trackpad.txt](/uploads/1fe1918bee9e895608a7f884cab352a7/udevadminfo-trackpad.txt) [udevadminfo-trackpoint.txt](/uploads/dbb20119e1110e431b53e207f27128b0/udevadminfo-trackpoint.txt)
- `libinput quirks list /dev/input/event6` output:
```
ModelSynapticsSerialTouchpad=1
AttrThumbPressureThreshold=100
```
- `libinput measure fuzz` output:
```
Using SynPS/2 Synaptics TouchPad: /dev/input/event6
Checking udev property... not set
Checking axes... not set
```
- `cat /sys/class/dmi/id/modalias` output: [modalias.txt](/uploads/51722e02a1a14c3caa668f9be47a26f1/modalias.txt)