libinput issueshttps://gitlab.freedesktop.org/libinput/libinput/-/issues2018-06-20T23:22:13Zhttps://gitlab.freedesktop.org/libinput/libinput/-/issues/53"libinput record" aborts after selecting the event number2018-06-20T23:22:13ZSergiusz M"libinput record" aborts after selecting the event numberIn relation to #46 I have discovered a bug in `libinput-util.h`.
In the commit 793c8d51e871252e03fd6aac79d1bf6fd4f717d3 function `zalloc(size_t size)` was restricted to not allow to allocate more than 1MB of memory.
```
/* We never ne...In relation to #46 I have discovered a bug in `libinput-util.h`.
In the commit 793c8d51e871252e03fd6aac79d1bf6fd4f717d3 function `zalloc(size_t size)` was restricted to not allow to allocate more than 1MB of memory.
```
/* We never need to alloc anything even near one MB so we can assume
* if we ever get above that something's going wrong */
if (size > 1024 * 1024)
abort();
```
However, libinput-record.c tries to allocate 136000 bytes which exceeds the new limit thus aborting the execution of libinput record.
A fix for that would be either to increase that limit to 1.5 MB or to decrease `d->events_sz = 5000;` in function `init_device(struct record_context *ctx, char *path)` from libinput-record.c.
I will make a merge request with the fix but I am not sure which of the proposed solutions is better.https://gitlab.freedesktop.org/libinput/libinput/-/issues/50libinput list-devices core dumps since libinput 1.11.12018-07-03T04:12:11ZMark Blakeneylibinput list-devices core dumps since libinput 1.11.1libinput updated from 1.11.0-1 -> 1.11.1-1 on Arch Linux today and since then running `libinput list-devices` core dumps as follows:
```
$ libinput list-devices
Segmentation fault (core dumped)
$ coredumpctl dump
PID: 4177 (...libinput updated from 1.11.0-1 -> 1.11.1-1 on Arch Linux today and since then running `libinput list-devices` core dumps as follows:
```
$ libinput list-devices
Segmentation fault (core dumped)
$ coredumpctl dump
PID: 4177 (libinput-list-d)
UID: 1000 (mark)
GID: 1000 (mark)
Signal: 11 (SEGV)
Timestamp: Tue 2018-06-19 22:49:51 AEST (9s ago)
Command Line: libinput-list-devices
Executable: /usr/lib/libinput/libinput-list-devices
Control Group: /user.slice/user-1000.slice/session-c1.scope
Unit: session-c1.scope
Slice: user-1000.slice
Session: c1
Owner UID: 1000 (mark)
Boot ID: xx
Machine ID: xx
Hostname: pc
Storage: /var/lib/systemd/coredump/core.libinput-list-d.1000.xx.lz4
Message: Process 4177 (libinput-list-d) of user 1000 dumped core.
Stack trace of thread 4177:
#0 0x000055d50c5029a4 n/a (libinput-list-devices)
#1 0x00007fb66202f82b n/a (libinput.so.10)
#2 0x00007fb6620445d6 n/a (libinput.so.10)
#3 0x00007fb6620449ad n/a (libinput.so.10)
#4 0x00007fb662044b54 libinput_udev_assign_seat (libinput.so.10)
#5 0x000055d50c501df0 n/a (libinput-list-devices)
#6 0x00007fb66227c06b __libc_start_main (libc.so.6)
#7 0x000055d50c5028ba n/a (libinput-list-devices)
```
This is problematic for many people who run [libinput-gestures](https://github.com/bulletmark/libinput-gestures) because it uses this command to find the touchpad device.
Note that other commands such as `libinput debug-events` still work fine.https://gitlab.freedesktop.org/libinput/libinput/-/issues/421gestures stopped working with 1.15.12020-02-05T21:21:45ZNonegestures stopped working with 1.15.1## Summary
Updated to libinput version 1.15.1 on Thinkpad X1 Carbon Gen 7 + Void Linux + i3wm, and gestures stopped working entirely (had been working fine for months). The behavior of the touchpad changed too. The mouse pointer could n...## Summary
Updated to libinput version 1.15.1 on Thinkpad X1 Carbon Gen 7 + Void Linux + i3wm, and gestures stopped working entirely (had been working fine for months). The behavior of the touchpad changed too. The mouse pointer could no longer be moved with more than one finger touching the touchpad e.g. when trying to drag something (I believe it was trying to scroll instead).
Reverting to libinput version 1.15.0 resolved the issue and gestures are working again.
Apologies for not being able to capture logs before reverting. Thanks in advance!
## Steps to reproduce
Install libinput 1.15.1
## libinput version you encountered the bug on
1.15.1
## Hardware information:
Lenovo Thinkpad X1 Carbon Gen 7
Package reference: https://github.com/void-linux/void-packages/tree/master/srcpkgs/libinput
https://gitlab.freedesktop.org/libinput/libinput/-/issues/427Regression: libinput-debug-events dumped core in 1.15.12020-02-18T08:04:41ZChris BillingtonRegression: libinput-debug-events dumped core in 1.15.1I'm on Arch Linux, and updated to libinput 1.15.1 today. Previously it was 1.15.0.
I'm getting a core dump from libinput-debug-events on system startup. Here is what GDB thinks about the coredump after rebuilding the libinput package wi...I'm on Arch Linux, and updated to libinput 1.15.1 today. Previously it was 1.15.0.
I'm getting a core dump from libinput-debug-events on system startup. Here is what GDB thinks about the coredump after rebuilding the libinput package with debug symbols :
```gdb
$ coredumpctl gdb 1220
PID: 1220 (libinput-debug-)
UID: 1000 (bilbo)
GID: 1000 (bilbo)
Signal: 6 (ABRT)
Timestamp: Wed 2020-02-12 13:27:34 EST (6min ago)
Command Line: libinput-debug-events --device /dev/input/by-path/pci-0000:00:15.1-platform-i2c_designware.1-event-mouse
Executable: /usr/lib/libinput/libinput-debug-events
Control Group: /user.slice/user-1000.slice/user@1000.service/gnome\x2dsession\x2dmanager.slice/gnome-session-manager@gnome.service
Unit: user@1000.service
User Unit: gnome-session-manager@gnome.service
Slice: user-1000.slice
Owner UID: 1000 (bilbo)
Boot ID: b02600f82a894ba0a395c917eb53d9b1
Machine ID: 6b9f268dc08d4655a8a0b6f6342aa98a
Hostname: bilbo-arch
Storage: /var/lib/systemd/coredump/core.libinput-debug-.1000.b02600f82a894ba0a395c917eb53d9b1.1220.1581532054000000000000.lz4
Message: Process 1220 (libinput-debug-) of user 1000 dumped core.
Stack trace of thread 1220:
#0 0x00007fa740fddce5 raise (libc.so.6 + 0x3bce5)
#1 0x00007fa740fc7857 abort (libc.so.6 + 0x25857)
#2 0x00007fa740fc7727 __assert_fail_base.cold (libc.so.6 + 0x25727)
#3 0x00007fa740fd6426 __assert_fail (libc.so.6 + 0x34426)
#4 0x00007fa740f7a7b9 tp_process_absolute (libinput.so.10 + 0x217b9)
#5 0x00007fa740f821eb evdev_process_event (libinput.so.10 + 0x291eb)
#6 0x00007fa740f81b4f libinput_dispatch (libinput.so.10 + 0x28b4f)
#7 0x000055c436126c72 handle_and_print_events (libinput-debug-events + 0x6c72)
#8 0x000055c4361257a4 mainloop (libinput-debug-events + 0x57a4)
#9 0x00007fa740fc9023 __libc_start_main (libc.so.6 + 0x27023)
#10 0x000055c436125aae _start (libinput-debug-events + 0x5aae)
GNU gdb (GDB) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/libinput/libinput-debug-events...
[New LWP 1220]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `libinput-debug-events --device /dev/input/by-path/pci-0000:00:15.1-platform-i2c'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007fa740fddce5 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007fa740fddce5 in raise () at /usr/lib/libc.so.6
#1 0x00007fa740fc7857 in abort () at /usr/lib/libc.so.6
#2 0x00007fa740fc7727 in _nl_load_domain.cold () at /usr/lib/libc.so.6
#3 0x00007fa740fd6426 in () at /usr/lib/libc.so.6
#4 0x00007fa740f7a7b9 in tp_process_absolute (e=<optimized out>, e=<optimized out>, time=14527759, tp=0x55c43767c970) at ../libinput-1.15.1/src/evdev-mt-touchpad.c:532
#5 tp_interface_process (device=<optimized out>, time=14527759, e=0x7fff74e2c710, dispatch=0x55c43767c970) at ../libinput-1.15.1/src/evdev-mt-touchpad.c:1898
#6 tp_interface_process (dispatch=0x55c43767c970, device=<optimized out>, e=0x7fff74e2c710, time=14527759) at ../libinput-1.15.1/src/evdev-mt-touchpad.c:1888
#7 0x00007fa740f821eb in evdev_process_event (e=0x7fff74e2c710, device=0x55c4376764c0) at ../libinput-1.15.1/src/evdev.c:983
#8 evdev_device_dispatch_one (ev=0x7fff74e2c710, device=0x55c4376764c0) at ../libinput-1.15.1/src/evdev.c:991
#9 evdev_device_dispatch (data=0x55c4376764c0) at ../libinput-1.15.1/src/evdev.c:1050
#10 0x00007fa740f81b4f in libinput_dispatch (libinput=0x55c43765f360) at ../libinput-1.15.1/src/libinput.c:2116
#11 0x000055c436126c72 in handle_and_print_events (li=0x55c43765f360) at ../libinput-1.15.1/tools/libinput-debug-events.c:827
#12 0x000055c4361257a4 in mainloop (li=0x55c43765f360) at ../libinput-1.15.1/tools/libinput-debug-events.c:953
#13 main (argc=<optimized out>, argv=<optimized out>) at ../libinput-1.15.1/tools/libinput-debug-events.c:1095
```https://gitlab.freedesktop.org/libinput/libinput/-/issues/422touchpad stops responding to touch after mempressure/swap event2020-02-23T23:13:44ZAdric Blaketouchpad stops responding to touch after mempressure/swap event## Summary
<!--
Summarize the bug encountered concisely. See
https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html for
detailed instructions to report bugs
-->
I recently started using libinput 1.15.1 from updating my...## Summary
<!--
Summarize the bug encountered concisely. See
https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html for
detailed instructions to report bugs
-->
I recently started using libinput 1.15.1 from updating my system. I was trying to scroll a page in Firefox when scrolling suddenly stopped working, and I found that I could no longer move my cursor with the touchpad. Left, middle and right clicks still worked when I physically clicked down. I enabled my mouse and found that the cursor could still move using it.
I posted this issue here because I examined Xorg.0.log and found the following:
```
[154472.727] (EE) client bug: timer event10 gestures: scheduled expiry is in the past (-73ms), your system is too slow
[154474.762] (II) event10 - DELL0810:00 044E:120A Touchpad: SYN_DROPPED event - some input events have been lost.
[154474.762] (EE) event10 - DELL0810:00 044E:120A Touchpad: kernel bug: Wrong slot count (5), reducing to 0
[154474.762] (EE) event10 - DELL0810:00 044E:120A Touchpad: kernel bug: touch 0 ended and began in in same frame.
[154474.762] (EE) event10 - DELL0810:00 044E:120A Touchpad: libinput bug: Unable to find topmost touch
[154474.762] (EE) event10 - DELL0810:00 044E:120A Touchpad: libinput bug: Unable to find topmost touch
```
I concluded that since the message was from a recent commit (eb6ef9fe), there is a chance system slowness (or something else) could have triggered a case that has been overlooked.
## Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
I haven't yet reproduced it, however I believe this to be caused by system slowness from swap usage. My kernel is linux-lts 5.4.18-1. To reproduce the slowness, you could try enabling a large amount of swap on an HDD and performing lots of file IO at ~85% memory usage/with Firefox running. I do not have a capture.
## libinput version you encountered the bug on
<!-- Note: if your libinput version is older than the current stable version,
please reproduce with a current version instead -->
libinput 1.15.1-1 (Arch Linux)
## Hardware information:
<!-- Model name/number and general hardware information if applicable -->
Device: DELL0810:00 044E:120A Touchpad
Laptop is a Dell Inspiron 15 5770.
## Other log output:
[dmi_id_modalias.txt](/uploads/51dd58c3629003637d67d813510da648/dmi_id_modalias.txt)
[udevadm_info_event10.txt](/uploads/7e42161b053c24f3e3ec3806f57824fd/udevadm_info_event10.txt)
[xinput-list-props.txt](/uploads/525b29be37d879415d75763388a03d10/xinput-list-props.txt)
[Xorg.0.log.txt](/uploads/c39b685418694c242c03ed7951d76d0d/Xorg.0.log.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.) -->https://gitlab.freedesktop.org/libinput/libinput/-/issues/434Regression in 1.15.1: Three/four finger gestures not working any more2021-03-11T06:24:34ZRobert MaderRegression in 1.15.1: Three/four finger gestures not working any more## Summary
Since the 1.15.1 upgrade in Fedora 31 testing, three/four finger gestures like swipes do not work any more.
Only the very first e.g. three finger swipe in a session succeeds, every one after that just creates the following o...## Summary
Since the 1.15.1 upgrade in Fedora 31 testing, three/four finger gestures like swipes do not work any more.
Only the very first e.g. three finger swipe in a session succeeds, every one after that just creates the following output in the journal:
```
libinput error: event4 - SynPS/2 Synaptics TouchPad: kernel bug: touch 1 ended and began in in same frame.
```
Downgrading to 1.15.0 reliable makes it work again.
Unfortunately I was to late to add bad karma to the update on bodhi, so this no goes to stable :(
## Hardware information:
Thinkpad T460p
```
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse0 event4
B: PROP=5
B: EV=b
B: KEY=e520 10000 0 0 0 0
B: ABS=660800011000003
```https://gitlab.freedesktop.org/libinput/libinput/-/issues/515Backlight Keys stopped working 1.15.6 ->1.16.0 (Sony Vaio, 2011)2021-11-16T19:30:15ZJohn RodriguezBacklight Keys stopped working 1.15.6 ->1.16.0 (Sony Vaio, 2011)## Summary
With libinput 1.15.6 pressing the backlight or screen brightness buttons worked. On my laptop that is Fn-F5 and Fn-F6. With 1.16.0, these keys no longer work.
## Steps to reproduce
I have attached two .yml files, one ...## Summary
With libinput 1.15.6 pressing the backlight or screen brightness buttons worked. On my laptop that is Fn-F5 and Fn-F6. With 1.16.0, these keys no longer work.
## Steps to reproduce
I have attached two .yml files, one for event0 (AT Translated Set 2 keyboard) and one for event7 (Sony Vaio Keys). Each file was created with this sequence: volume down, volume up, brightness down, brightness up. The volume works and can be seen in the event0 file. event0 does not show the brightness up or down keypresses. Repeating the test but looking at event7, only the brightness up or down keypresses are seen. Looking at debug_events.txt, I noticed that event7 is being ignored:
```
event7 - Sony Vaio Keys: is tagged by udev as: Keyboard Joystick
event7 - Sony Vaio Keys: device is a joystick, ignoring
event7 - not using input device '/dev/input/event7'
```
event7 has the event codes:
```
# Event code 224 (KEY_BRIGHTNESSDOWN)
# Event code 225 (KEY_BRIGHTNESSUP)
```
## Required information
- libinput version: 1.16.0 not working, 1.15.6 working
- hardware information: Sony Vaio VPCEG, 2011 model year.
- libinput record - 2 files attached
- libinput debug-events --verbose` 1 file attached
[debug_events.txt](/uploads/aab342bbabc2b51338bede981ac90868/debug_events.txt)
[event7_SonyVaioKeys.yml](/uploads/51435d229a290be29b23d06cccef28ae/event7_SonyVaioKeys.yml)
[event0_AT_Translated.yml](/uploads/957ec215d98f52b0432ada833a26568a/event0_AT_Translated.yml)https://gitlab.freedesktop.org/libinput/libinput/-/issues/708Gestures no longer work with thumb holding down button on clickpad2021-12-14T06:10:17ZMatt MayfieldGestures no longer work with thumb holding down button on clickpad## Summary
Somewhere in the last year or two, libinput lost the ability to hold down a clickpad button with the thumb and still use two-finger scrolling or swipes.
## Steps to reproduce
### Scrolling use case
Attempt to select a large...## Summary
Somewhere in the last year or two, libinput lost the ability to hold down a clickpad button with the thumb and still use two-finger scrolling or swipes.
## Steps to reproduce
### Scrolling use case
Attempt to select a large amount of text using a two-finger scroll.
1. In an text editor application, open a file large enough to vertically scroll.
2. Mouse over some text, and hold down the clickpad with a thumb.
3. Attempt to scroll downward with two fingers.
**Expected behavior**: window scrolls. **Actual behavior**: mouse pointer moves, about twice as fast as normal.
### Virtual desktop / workspace use case
Attempt to drag an item from an application on one virtual desktop / workspace / activity to an application on a different one. (File manager to terminal, in this example)
1. Set up a desktop environment to move between workspaces / virtual desktops with 3-finger swipe.
2. Open a file manager window on one workspace, and a terminal in another. Type `cd ` (with trailing space) in the terminal, without pressing Enter.
3. Swipe with 3 fingers to go back to the file manager.
4. Hold down the touchpad button in the file manager window in preparation to drag a folder icon.
5. With the thumb holding down the clickpad, attempt to swipe to the terminal workspace (to drop the folder into the terminal).
**Expected behavior**: 3-finger swipe moves us to the terminal workspace, enabling us to drop the icon on it and insert the folder's path. **Actual behavior**: mouse pointer moves, about three times as fast as normal.
I'll assign this to myself and look into it.Matt MayfieldMatt Mayfield