You are not logged in.

#1 2025-02-25 20:37:28

asafgre
Member
Registered: 2024-10-07
Posts: 4

Touchscreen stopped responding, twice. Might relate to keyd

actually, it is UNRESOLVED,

yesterday I disabled "keyd" (and restarted!), touchscreen resumed operation.
Today "keyd" is still disabled, but the touchscreen is again stopped working.


System:
Dynabook (ex-toshiba) portege x30L
EndeavorOS
KDE + WayLand

Touchscreen isn't working now, but it had been working already within the current setup, during first 8 months since purchase.
Then it stopped working, then worked again after a system update for few days, then stopped.

(only the touch functionality has stopped. The screen itself is working).
In the past 2 months it didn't work at all.

I suspect it has something to do with "keyd", a daemon that controls the keyboard in certain ways.
(github: raiya/keyd)

The hardware seems fine:

cat /proc/bus/input/devices:

Siliconworks SiW HID Touch Controller

xinput

xwayland-touch:10    
           id=10   slave  pointer  (2)

sudo libinput debug-events
keyboard, touchpad, track-point:  they all generate events.
touchscreen? nothing.


sudo libinput list-devices

Device:           Siliconworks SiW HID Touch Controller
Kernel:           /dev/input/event7
Group:            5
Seat:             seat0, default
Capabilities:     touch
Calibration:      identity matrix
(etc...)

I disabled keyd service, but touch is still unresponsive.
I don't know what to check next.
Any ideas?

Last edited by asafgre (2025-03-02 21:16:35)

Offline

#2 2025-02-25 23:49:33

eriefisher
Member
Registered: 2025-02-01
Posts: 24

Re: Touchscreen stopped responding, twice. Might relate to keyd

This may be of some help:

https://wiki.archlinux.org/title/Touchscreen

Also, I though these touch screens also used the wacom driver? Don't know.


I Am Canadian!

Offline

Board footer

Powered by FluxBB