On Sun, Jan 02, 2022 at 06:23:22PM +0000, Koka Koko wrote: > Hello, everyone! > I face a problem with an old touchscreen in CF-18 using libinput and lubuntu > 18.04 (Linux 5.4.0-91-generic) > > My 40-libinput.conf has right (as it goes for me) section describing > touchscreens: > > Section "InputClass" > Identifier "libinput touchscreen catchall" > MatchIsTouchscreen "on" > MatchDevicePath "/dev/input/event*" > Driver "libinput" > EndSection > > But Xorg.0.log writes: > > [ 37.305] (II) config/udev: Adding input device LBPS/2 Fujitsu Lifebook > TouchScreen (/dev/input/event6) > [ 37.305] (**) LBPS/2 Fujitsu Lifebook TouchScreen: Applying InputClass > "libinput touchscreen catchall" > [ 37.305] (**) LBPS/2 Fujitsu Lifebook TouchScreen: Applying InputClass > "calibration" > [ 37.306] (II) Using input driver 'libinput' for 'LBPS/2 Fujitsu Lifebook > TouchScreen' > [ 37.306] (**) LBPS/2 Fujitsu Lifebook TouchScreen: always reports core > events > [ 37.306] (**) Option "Device" "/dev/input/event6" > [ 37.306] (**) Option "_source" "server/udev" > [ 37.308] (II) event6 - LBPS/2 Fujitsu Lifebook TouchScreen: is tagged by > udev as: Touchscreen > [ 37.324] (II) event6 - LBPS/2 Fujitsu Lifebook TouchScreen: device is a > touch device > [ 37.324] (II) event6 - LBPS/2 Fujitsu Lifebook TouchScreen: device > removed > [ 37.324] (**) Option "config_info" > "udev:/sys/devices/platform/i8042/serio3/input/input11/event6" > [ 37.324] (II) XINPUT: Adding extended input device "LBPS/2 Fujitsu > Lifebook TouchScreen" (type: TOUCHSCREEN, id 11) > [ 37.324] (**) Option "AccelerationScheme" "none" > [ 37.325] (**) LBPS/2 Fujitsu Lifebook TouchScreen: (accel) selected > scheme none/0 > [ 37.325] (**) LBPS/2 Fujitsu Lifebook TouchScreen: (accel) acceleration > factor: 2.000 > [ 37.325] (**) LBPS/2 Fujitsu Lifebook TouchScreen: (accel) acceleration > threshold: 4 > [ 37.327] (II) event6 - LBPS/2 Fujitsu Lifebook TouchScreen: is tagged by > udev as: Touchscreen > [ 37.327] (II) event6 - LBPS/2 Fujitsu Lifebook TouchScreen: device is a > touch device
Up to here it's about the event device. the device_removed message is a side-effect of how the X server pre-inits and then later (read: immediately) starts them. Nothing to worry about, this output looks coorrect. > [ 37.329] (II) config/udev: Adding input device LBPS/2 Fujitsu Lifebook > TouchScreen (/dev/input/mouse1) > [ 37.329] (**) LBPS/2 Fujitsu Lifebook TouchScreen: Applying InputClass > "calibration" > [ 37.329] (II) No input driver specified, ignoring this device. > [ 37.329] (II) This device may have been added with another device file. > > You know, the last two lines looks very suspecious as well as the line [ > 37.324] which ends up with "device removed". this is for the /dev/input/mouse1 device which shouldn't be added (and hasn't been for the last decade or so). > > At the same time, I see the device in the output of: > > $ libinput list-devices > ------------------------- > Device: LBPS/2 Fujitsu Lifebook TouchScreen > Kernel: /dev/input/event6 > Group: 7 > Seat: seat0, default > Capabilities: touch > Tap-to-click: n/a > Tap-and-drag: n/a > Tap drag lock: n/a > Left-handed: n/a > Nat.scrolling: n/a > Middle emulation: n/a > Calibration: identity matrix > Scroll methods: none > Click methods: none > Disable-w-typing: n/a > Accel profiles: n/a > Rotation: n/a > > and I get a somewhat stream of values by: > > $ cat /dev/event6 > > Moreover, the touchscreen reacts to poking at the screen, but the mouse > pointer moves along X-axes only (but withing the full range of the screen) > somwhere at the bottom of the screen (over the panel line, thus I can see > the icon of the pointer fully) > > 1. Am I right in conclusion that libinput driver does not connect to the > device? But why a mouse pointer moves in this case? > > 2. How can I edit 40-libinput.conf to get libinput driver to operate > properly with LBPS/2 Fujitsu Lifebook TouchScreen? your config is correct. It's probably a bug with the device itself or something inside libinput. File a bug against libinput please with the `sudo libinput record` output attached for a short event sequence. Cheers, Peter
