Fedora Account System
Red Hat Associate
Red Hat Customer
I have a new laptop and horizontal scrolling doesn’t work on the edge. Here is the configuration: Section "InputClass" Identifier "system-touchpad" Driver "libinput" MatchIsTouchpad "on" Option "Tapping" "on" Option "ScrollMethod" "edge" Option "HorizontalScrolling" "on" EndSection And libinput-list-devices reports: Device: SynPS/2 Synaptics TouchPad Kernel: /dev/input/event4 Group: 7 Seat: seat0, default Size: 112x45mm Capabilities: pointer gesture Tap-to-click: disabled Tap-and-drag: enabled Tap drag lock: disabled Left-handed: disabled Nat.scrolling: disabled Middle emulation: n/a Calibration: n/a Scroll methods: *two-finger edge Click methods: none Disable-w-typing: enabled Accel profiles: none Rotation: n/a The touchpad is actually 115x50mm. touchpad-edge-detector reports: touchpad-edge-detector 115x50 /dev/input/event4 Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event4 Move one finger around the touchpad to detect the actual edges Kernel says: x [1292..5648], y [1026..4826] Touchpad sends: x [1332..5689], y [1043..4916] /^C Touchpad size as listed by the kernel: 111x45mm User-specified touchpad size: 115x50mm Calculated ranges: 4357/3873 Suggested udev rule: # <Laptop model description goes here> evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnInsyde:bvrF.31:bd11/01/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.45:cvnHP:ct10:cvrChassisVersion:* EVDEV_ABS_00=1332:5689:38 EVDEV_ABS_01=1043:4916:77 EVDEV_ABS_35=1332:5689:38 EVDEV_ABS_36=1043:4916:77 I hope it helps, Pablo
please drop this into /etc/udev/hwdb.d/99-touchpad.hwdb: evdev:name:SynPS/2 Synaptics TouchPad:dmi:*svnHP:pnHPLaptop15-bs0xx:* EVDEV_ABS_00=1332:5689:38 EVDEV_ABS_01=1043:4916:77 EVDEV_ABS_35=1332:5689:38 EVDEV_ABS_36=1043:4916:77 run sudo udevadm hwdb --update, restart and try again. more info: https://wayland.freedesktop.org/libinput/doc/latest/udev_config.html#hwdb
With these data, libinput reports a size of 111x45 mm. With these (newer) ones, I get a 112x45 mm: EVDEV_ABS_00=1282:5689:38 EVDEV_ABS_01=1120:4916:76 EVDEV_ABS_35=1282:5689:38 EVDEV_ABS_36=1120:4916:76 In fact, the touchpad size is 115x50 mm. Horizontal scrolling doesn’t work when too near to the edge. Anyway, which would be the component to report that hotkeys for screen brightness aren’t working for this laptop? (I wonder whether it is libinput.) Many thanks for your help again.
If you get different min/max ranges, then you're not running the touchpad-edge-detector long enough. The numbers are supposed to capture the min/max for each axis, if they differ between runs, you're not getting into the edges far enough. e.g. the x axis has a mm difference here for the minimum and so does the y axis. The resolution is calculated based on those min/max ranges and the size you supply on the commandline. While it's impossible to get there 100% (integer rounding errors), we should still be within a mm or so. Please re-run, trying to really get into the edges of the touchpad. screen brightness: mutter. check with sudo libinput debug-events that you see the key event there first though, if you don't, it's a kernel issue.
Many thanks for your reply, Peter. I have seen the key events with libinput debug-events. I use LXDE, is mutter also the component? I tried for some minutes with touchpad-edge-detector and I went so close to the edges as it is human possible. I have the impression the edge very near the buttons may be not be part of the touchpad. But I will rerun the touchpad-edge-detector tomorrow again. BTW, just in case it were relevant, with the following configuration: evdev:name:SynPS/2 Synaptics TouchPad:dmi:*svnHP:pnHPLaptop15-bs0xx:* EVDEV_ABS_00=1282:5689:38 EVDEV_ABS_01=1120:4916:76 EVDEV_ABS_35=1282:5689:38 EVDEV_ABS_36=1120:4916:76 I get the following message: touchpad-edge-detector 115x50 /dev/input/event4 Error: this device does not have abs axes I wonder whether this might be relevant to the issue with the touchpad measures.
If you use lxde, the component is... lxde? I honestly don't know, whatever handles the touchpad settings there :) That hwdb entry only updates the axes, but your device node is not constant. makes sure that event4 is still the touchpad device, the enumeration order may have changed. IOW, the hwdb entry cannot be the cause for this.
Peter, many thanks for your reply. Just after searching for mutter, I realized that my question about LXDE and mutter was stupid. I got a new configuration, which gives a 116x50mm touchpad: evdev:name:SynPS/2 Synaptics TouchPad:dmi:*svnHP:pnHPLaptop15-bs0xx:* EVDEV_ABS_00=1272:5689:38 EVDEV_ABS_01=1029:4916:78 EVDEV_ABS_35=1272:5689:38 EVDEV_ABS_36=1029:4916:78 I hope it is fine now.
PR sent to https://github.com/systemd/systemd/pull/8404
Merged upstream. I'll reassign to systemd so it'll get closed when systemd is released.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.