Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Touch Screen Input not working #306

Closed
Torsten85 opened this issue Jan 19, 2024 · 13 comments
Closed

Touch Screen Input not working #306

Torsten85 opened this issue Jan 19, 2024 · 13 comments

Comments

@Torsten85
Copy link

Hello,
I've no experience with cage nor with wayland, so I'm sorry if I'm missing something obvious.

I've a mouse and a touch screen connected to my raspberry pi, but only the mouse is recognized. The default raspberry desktop recognizes both devices.

Thanks in advance

@Torsten85 Torsten85 changed the title Touch Input not working Touch Screen Input not working Jan 19, 2024
@joggee-fr
Copy link
Collaborator

Hi @Torsten85,
Do you know which version of Cage you are running? Do you have any (debug) logs available?
Can you observe the input devices returned by the kernel e.g. using libinput list-devices command?

@Torsten85
Copy link
Author

Torsten85 commented Jan 19, 2024

@joggee-fr Thanks for your quick response!

I'm running Cage version 0.1.4.
Running libinput debug-events I see all the touch events, so this is working.

This is the output from libinput list-devices:

Click me
Device:           WaveShare WaveShare
Kernel:           /dev/input/event3
Group:            1
Seat:             seat0, default
Size:             512x293mm
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
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           Logitech K400 Plus
Kernel:           /dev/input/event4
Group:            2
Seat:             seat0, default
Capabilities:     keyboard pointer
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   button
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           pwr_button
Kernel:           /dev/input/event0
Group:            3
Seat:             seat0, default
Capabilities:     keyboard
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:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         n/a

Device:           vc4-hdmi-0
Kernel:           /dev/input/event1
Group:            4
Seat:             seat0, default
Capabilities:     keyboard pointer
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *button
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           vc4-hdmi-1
Kernel:           /dev/input/event2
Group:            5
Seat:             seat0, default
Capabilities:     keyboard pointer
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *button
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

@joggee-fr
Copy link
Collaborator

Version 0.1.4 is a bit old now. Last release is 0.1.5 and I remember a fix for touch events has been pushed even after this version. I don't know if it could fix your issue but it could be a good start if you can compile and test the very last commit (or at least 7ec7e3df2bfc2069219285ccca676327480fa471).

@Torsten85
Copy link
Author

Thanks @joggee-fr , that did the trick!

Now I have to figure out how to rotate the screen (the -r options seems to be missing in the newer version)... and maybe rotate the touch input... and also hide the cursor 😉

But those tasks might be independend issues if I cannot figure it out.

@joggee-fr
Copy link
Collaborator

Take a look at wlr-randr or kanshi for the screen rotation.
Hiding cursor is also discussed in open issued #299.

@Torsten85
Copy link
Author

@joggee-fr thanks for pointing me in the right direction.

One unrelated question: Is there a discord channel or something like that where I can ask for some guide, best practices? Using github issues feels kinda wrong and I've still a lot to learn.

@joggee-fr
Copy link
Collaborator

@Torsten85, I am not aware of any Discord or IRC channel for Cage.
wlroots has a dedicated IRC channel, see README (but I have never used it yet).
Is this issue to be closed now?

@Torsten85
Copy link
Author

yes thank you

@OctopusET
Copy link
Contributor

@joggee-fr what about making new channel #cage at the liberachat?

@joggee-fr
Copy link
Collaborator

@OctopusET, I am not a Libera chat user so I can't say.

@denysvitali
Copy link

Can confirm: touch input is not working on Cage 0.1.5: I had to compile Cage from main to make it work.

Can you please create a release 0.1.6 so that others will have the fix too? Thanks!

@mpfaff
Copy link

mpfaff commented May 5, 2024

Can confirm: touch input is not working on Cage 0.1.5: I had to compile Cage from main to make it work.

Can you please create a release 0.1.6 so that others will have the fix too? Thanks!

Also not working for me on 0.1.5. On every touch event this error is printed:

[ERROR] [types/seat/wlr_seat_touch.c:191] could not create touch point

@denysvitali, can you confirm that is the same error you saw and that it is fixed on main?

@denysvitali
Copy link

Sorry. I can't confirm (I don't remember the exact error message) and I'll not be able to check for at least 2 weeks :S

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants