Page 1 of 1

Touch Foil lost settings after some minutes

Posted: 14 Jan 2019, 11:19
by manuele
Hello,

I have a problem with a touch foil device and Porteus Kiosk. I set via config some touch setting (i.e. touchscreen_calibration="USBest Technology SiS HID Touch Controller" "Evdev Axes Swap" 8 1), when the system start, touch settings is correctly applied but after a while touch device lost settings.

After some troubleshooting I foud that if I run via ssh xinput watch-props "USBest Technology SiS HID Touch Controller" after some minutes an error occurs:

Property 'Device Enabled' changed.
X Error: BadDevice, invalid or unintialized input device
Request Major code 131 (XInputExtension)
Request Minor code 39 ()
Error Serial #81
Current Serial #81

After this error occurs touch continue work with default settings.
We have 2 system running with same hardware and we obtain same error. Tried with old version but nothing change.

Any suggest?

Thanks and sorry for my english... :(

Manuele

Re: Touch Foil lost settings after some minutes

Posted: 14 Jan 2019, 12:53
by fanthom
Hi Manuele,

Please boot latest Ubuntu live on this hardware and check if you get the same issue.
If not then new kiosk release (scheduled for next week) may resolve this problem.

Thanks

Re: Touch Foil lost settings after some minutes

Posted: 14 Jan 2019, 14:37
by manuele
Hi Fanthom,

Thanks for your feedback. I have just tried with Ubuntu live as you suggest and it works.
If I run xinpunt watch-props on Ubuntu I see diffent propreties (all propreties start with libinput instead of evdev). Different driver?

Thanks

Re: Touch Foil lost settings after some minutes

Posted: 14 Jan 2019, 16:07
by fanthom
"If I run xinpunt watch-props on Ubuntu I see diffent propreties (all propreties start with libinput instead of evdev). Different driver? "
Ubuntu uses libinput while we are still on evdev as we should avoid breaking our API ('touchscreen_calibration=' parameter in this case).
As far as i'm concerned the touchscreen calibration applies to evdev driver only (unless i'm mistaken).

Hopefully its about the kernel driver rather than userspace input driver - will find out next week once kiosk 4.8.0 is out.
If your touchscreen really needs libinput then customized build will be required i'm afraid.

Thanks