Bug 99664

Summary: Device 'DIALOGUE INC PenMount USB' does not meet tablet criteria. Ignoring this device
Product: Wayland Reporter: crankshaft <forms>
Component: libinputAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: normal    
Priority: medium CC: flussence+bz.fdo, peter.hutterer
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: attachment-21236-0.html
evemu-record /dev/input/by-id/usb-WALTOP_International_Corp._Slim_Tablet-event-mouse evemu.log

Description crankshaft 2017-02-03 12:09:05 UTC
Arch Linux 4.4.46-1-lts
X.Org X Server 1.19.1

I have been using the same installation / touch screen for several years, it all worked fine until today !
I decided to do a fresh install and now X11 refuses to use the touch screen:

(EE) libinput bug: Device 'DIALOGUE INC PenMount USB' does not meet tablet criteria. Ignoring this device.

I have googled this and found several reports on other O/S but no real answers.
Comment 1 Anthony Parsons 2017-02-04 03:33:36 UTC
I'm getting the same with a different tablet, after upgrading from libinput 1.5.3 to 1.6.0:

~ # libinput-debug-events
libinput error: libinput bug: Device 'WALTOP International Corp. Slim Tablet' does not meet tablet criteria. Ignoring this device.
-event1   DEVICE_ADDED     Power Button                      seat0 default group1  cap:k
-event0   DEVICE_ADDED     Power Button                      seat0 default group2  cap:k
-event2   DEVICE_ADDED     Microsoft NaturalĀ® Ergonomic Keyboard 4000 seat0 default group3  cap:k
-event3   DEVICE_ADDED     Microsoft NaturalĀ® Ergonomic Keyboard 4000 seat0 default group3  cap:kp scroll-nat
-event4   DEVICE_ADDED     Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) seat0 default group4  cap:p left scroll-nat scroll-button
(moving pen around here)
-event2   KEYBOARD_KEY     +24.79s      KEY_LEFTCTRL (29) pressed
 event2   KEYBOARD_KEY     +24.93s      KEY_C (46) pressed
^C

After downgrading to libinput 1.5.4 and replugging the tablet, it fills the screen with axis/pressure events again as expected.

USB ID is 172f:0031, kernel driver is hid_waltop.
Comment 2 Peter Hutterer 2017-02-07 00:34:26 UTC
I need an evemu-record output from the device please, thanks.
Comment 3 Peter Hutterer 2017-02-13 23:29:58 UTC
ping?
Comment 4 crankshaft 2017-02-15 03:46:55 UTC
Created attachment 129618 [details]
attachment-21236-0.html

Hi;

Sorry, but this test environment is no longer available.

I needed to do a fresh install of ARCH LINUX on a industrial Touch Panel 
that we have deployed across several countries for the last 7 years, but 
not having touch capability on the fresh install was a show-stopper.

I waited for a few days, but your response came a little too late, as 
this is a live production device that is used in an industrial 
environment, and I could not wait any longer.

But the previous versions of the driver has worked flawlessly for over 7 
years and survived numerous updates usually every 3 months, it's only 
the latest that seems to have killed it for me.

Sorry  & Thanks


On 14/2/17 7:29 am, bugzilla-daemon@freedesktop.org wrote:
>
> *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=99664#c3> 
> on bug 99664 <https://bugs.freedesktop.org/show_bug.cgi?id=99664> from 
> Peter Hutterer <mailto:peter.hutterer@who-t.net> *
> ping?
> ------------------------------------------------------------------------
> You are receiving this mail because:
>
>   * You reported the bug.
>
Comment 5 Peter Hutterer 2017-02-15 04:02:08 UTC
ok, closing the bug, there's no way I can debug this based on the information you've given me.

Arch recently switched to the xorg-x11-drv-libinput driver as default X driver and that driver has more stringent requirements on tablets. I recommend uninstalling that one, that will return you to the previous evdev driver and things should work as before.
Comment 6 Anthony Parsons 2017-03-24 02:22:43 UTC
Created attachment 130409 [details]
evemu-record /dev/input/by-id/usb-WALTOP_International_Corp._Slim_Tablet-event-mouse evemu.log

(In reply to Peter Hutterer from comment #2)
> I need an evemu-record output from the device please, thanks.

Sorry for not replying, hadn't added myself to CC. Here's one for my tablet.
Comment 7 Peter Hutterer 2017-03-24 04:18:10 UTC
this tablet needs a hwdb override, it doesn't provide resolution so libinput rejects it. locate 60-evdev.hwdb on your machine and read the instructions at the top, you need to set the resolution for axes 0 and 1 (ABS_X and ABS_Y) so that the axis range reflects the physical size of the touchpad. A match key in the evdev:input:b0003... form should work, just replace vendor and product with the waltop's. Please try fixing this yourself, let me know if you get stuck though.
Comment 8 Anthony Parsons 2017-03-24 19:50:51 UTC
(In reply to Peter Hutterer from comment #7)

I'm not having much success despite following those instructions to the letter. Here's the contents of my /etc/udev/hwdb.d/61-evdev-local.hwdb:

evdev:input:b0003v172fp0031*
 EVDEV_ABS_00=::400
 EVDEV_ABS_01=::400
## Also tried these, didn't work:
#evdev:name:WALTOP International Corp. Slim Tablet
#evdev:input:*v172fp0031*
# EVDEV_ABS_00=0:10000:400
# EVDEV_ABS_01=0:6250:400

I've done udevadm hwdb --update/udevadm trigger, and I've restarted udevd and replugged the tablet a few times to make sure. I've verified udev does read that file, since it complains if I deliberately put syntax errors in and I can see hwdb.bin's timestamp updating. But it doesn't seem to be sticking at all, evemu-record still shows the resolution values set to 0 and libinput still refuses to believe it's a tablet.


I don't know if I'm making a glaringly obvious mistake somewhere, but just in case here's the udevadm info output too:

P: /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/0003:172F:0031.000F/input/input17/event5
N: input/event5
S: input/by-id/usb-WALTOP_International_Corp._Slim_Tablet-event-mouse
S: input/by-path/pci-0000:00:13.0-usb-0:1:1.0-event-mouse
E: DEVLINKS=/dev/input/by-id/usb-WALTOP_International_Corp._Slim_Tablet-event-mouse /dev/input/by-path/pci-0000:00:13.0-usb-0:1:1.0-event-mouse
E: DEVNAME=/dev/input/event5
E: DEVPATH=/devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/0003:172F:0031.000F/input/input17/event5
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_INPUT_TABLET=1
E: ID_MODEL=Slim_Tablet
E: ID_MODEL_ENC=Slim\x20Tablet
E: ID_MODEL_ID=0031
E: ID_PATH=pci-0000:00:13.0-usb-0:1:1.0
E: ID_PATH_TAG=pci-0000_00_13_0-usb-0_1_1_0
E: ID_REVISION=0102
E: ID_SERIAL=WALTOP_International_Corp._Slim_Tablet
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=WALTOP_International_Corp.
E: ID_VENDOR_ENC=WALTOP\x20International\x20Corp.
E: ID_VENDOR_ID=172f
E: LIBINPUT_DEVICE_GROUP=3/172f/31/110:usb-0000:00:13.0-1
E: MAJOR=13
E: MINOR=69
E: SUBSYSTEM=input
E: USEC_INITIALIZED=58642072685
Comment 9 Peter Hutterer 2017-03-24 21:01:25 UTC
> I'm not having much success despite following those instructions to the letter.
> Here's the contents of my /etc/udev/hwdb.d/61-evdev-local.hwdb:
> 
> evdev:input:b0003v172fp0031*

immediate issue I see here: the hex codes must be uppercase, so 
 evdev:input:b0003v172Fp0031*
Comment 10 Anthony Parsons 2017-03-24 21:05:23 UTC
(In reply to Peter Hutterer from comment #9)
> > I'm not having much success despite following those instructions to the letter.
> > Here's the contents of my /etc/udev/hwdb.d/61-evdev-local.hwdb:
> > 
> > evdev:input:b0003v172fp0031*
> 
> immediate issue I see here: the hex codes must be uppercase, so 
>  evdev:input:b0003v172Fp0031*

That was it! Flipped one bit, kicked udev again and everything suddenly works. Thanks a lot!
Comment 11 Peter Hutterer 2017-03-24 21:13:48 UTC
> That was it! Flipped one bit, kicked udev again and everything suddenly works.
> Thanks a lot!

great! please open a systemd PR for this patch so we can ship it by
default.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.