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

test issue #612

Closed
whot opened this issue Dec 4, 2023 · 2 comments
Closed

test issue #612

whot opened this issue Dec 4, 2023 · 2 comments
Labels
not libwacom Used to label a bug in the rest of the stack

Comments

@whot
Copy link
Member

whot commented Dec 4, 2023

blah

@whot whot added the not libwacom Used to label a bug in the rest of the stack label Dec 4, 2023
Copy link

github-actions bot commented Dec 4, 2023

Hi, there. I'm a bot and have been asked to have a look at this.

libwacom is a bunch of text files with a C API, and the information in those text files
is static fixed information that we cannot get from the device (e.g. the model name or which
button will produce which event code). It does not affect functionality directly, if the
tablet does not work this is either an issue with the kernel drivers, xf86-input-wacom
(if using X) or libinput/the desktop environment (if using Wayland). Please file the
issue with the component that most likely applies.

See also https://github.com/linuxwacom/libwacom/wiki/Troubleshooting
See also https://github.com/linuxwacom/libwacom/wiki/Adding-a-new-device


This is an automated comment created by a bot. Responding to the bot or mentioning it won't have any effect.

@github-actions github-actions bot closed this as completed Dec 4, 2023
@whot
Copy link
Member Author

whot commented Dec 4, 2023

🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not libwacom Used to label a bug in the rest of the stack
Projects
None yet
Development

No branches or pull requests

1 participant