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

Add tablet definition for Huion Kamvas 13 (GS1331) #535

Merged
merged 1 commit into from
Dec 5, 2022

Conversation

blzq
Copy link

@blzq blzq commented Dec 4, 2022

sysinfo: linuxwacom/wacom-hid-descriptors#247 (comment)

Similar issues to #361 in that the USB identifier is shared with the Huion H950P, so I had to edit that tablet definition locally to not match in order for this one to take priority.

@blzq blzq changed the title Add tablet definition for Huion Kamvas 13 Add tablet definition for Huion Kamvas 13 (GS1331) Dec 4, 2022
@whot whot merged commit 56797c8 into linuxwacom:master Dec 5, 2022
@whot
Copy link
Member

whot commented Dec 5, 2022

merged, thanks!

@theFroh
Copy link

theFroh commented Jan 17, 2023

Chiming in here -- I manually installed this (and removed the H950P file), and it wasn't working. Looking at libinput record it looks like the tablet was identifying itself as "Tablet Monitor Pad" and "Pen", not the names given in this PR's files.

Not too sure if this is something I've done somehow, but in case anyone else with a Kamvas 13 runs into it, I had to take this PR's file and edit the DeviceMatch line to be as follows:

DeviceMatch=usb:256c:006d:Tablet Monitor Pad;usb:256c:006d:Tablet Monitor Pen

With that change I'm able to see the device in GNOME Control Center, though I do get the following output from libwacom-list-local-devices:

# libwacom-list-local-devices
/dev/input/event21 is a tablet but not supported by libwacom
/dev/input/event20 is a tablet but not supported by libwacom
devices:
- name: 'Huion Kamvas 13'
  bus: 'usb'
  vid: '0x256c'
  pid: '0x006d'
  nodes: 
  - /dev/input/event19
- name: 'Huion Kamvas 13'
  bus: 'usb'
  vid: '0x256c'
  pid: '0x006d'
  nodes: 
  - /dev/input/event18

Here's what I see from libinput record for reference there:

/dev/input/event18:	Tablet Monitor Pen
/dev/input/event19:	Tablet Monitor Pad
/dev/input/event20:	Tablet Monitor Stylus
/dev/input/event21:	Tablet Monitor
/dev/input/event22:	Tablet Monitor Keyboard
/dev/input/event23:	Tablet Monitor Consumer Control
/dev/input/event24:	Tablet Monitor System Control

@KatsuroKurosaki
Copy link

Chiming in here -- I manually installed this (and removed the H950P file), and it wasn't working. Looking at libinput record it looks like the tablet was identifying itself as "Tablet Monitor Pad" and "Pen", not the names given in this PR's files.

Not too sure if this is something I've done somehow, but in case anyone else with a Kamvas 13 runs into it, I had to take this PR's file and edit the DeviceMatch line to be as follows:

DeviceMatch=usb:256c:006d:Tablet Monitor Pad;usb:256c:006d:Tablet Monitor Pen

With that change I'm able to see the device in GNOME Control Center, though I do get the following output from libwacom-list-local-devices:

# libwacom-list-local-devices
/dev/input/event21 is a tablet but not supported by libwacom
/dev/input/event20 is a tablet but not supported by libwacom
devices:
- name: 'Huion Kamvas 13'
  bus: 'usb'
  vid: '0x256c'
  pid: '0x006d'
  nodes: 
  - /dev/input/event19
- name: 'Huion Kamvas 13'
  bus: 'usb'
  vid: '0x256c'
  pid: '0x006d'
  nodes: 
  - /dev/input/event18

Here's what I see from libinput record for reference there:

/dev/input/event18:	Tablet Monitor Pen
/dev/input/event19:	Tablet Monitor Pad
/dev/input/event20:	Tablet Monitor Stylus
/dev/input/event21:	Tablet Monitor
/dev/input/event22:	Tablet Monitor Keyboard
/dev/input/event23:	Tablet Monitor Consumer Control
/dev/input/event24:	Tablet Monitor System Control

Hi,
Excuse my ignorance, but could you tell me which file do I have to edit in order for the tablet settings to show up on gnome-control-center? Gnome is updating to v45 on Arch and now, after every login, movement is set to absolute and I have to change it back to the Kamvas 13 screen with the "xinput map-to-output 20 HDMI-A-0" command.
Also "dconf list /org/gnome/desktop/peripherals/tablets/" returns 2 entries, not sure if that's correct, and they are:
056a:033b/
256c:006d/

Thanks!

@blzq
Copy link
Author

blzq commented Oct 15, 2023

The file on Arch Linux is located at /usr/share/libwacom/huion-kamvas-13.tablet, I would recommend just editing the DeviceMatch line to DeviceMatch=usb:256c:006d unless you have another tablet with the same ID connected at the same time.

Not sure if it will solve your particular issue though.

@KatsuroKurosaki
Copy link

Well, it did solve my issue! Thank you very much, kind Internet person <3
Tablet shows up again on gnome-control-center and I can finally map it to the tablet monitor, no more running commands after log in to stop absolute positioning across 3 monitors.
Easy steps

  • Comment out the original line
  • Add yours
  • Reboot
  • Profit!

Here is how it looks like now, the USB ID's are the same:

#DeviceMatch=usb:256c:006d:HUION Huion Tablet_GS1331 Pad;usb:256c:006d:HUION Huion Tablet_GS1331 Pen
DeviceMatch=usb:256c:006d:Tablet Monitor Pad;usb:256c:006d:Tablet Monitor Pen

Also libwacom-list-local-devices command successfully detects the tablet, before editing the file, it returned that nothing was supported yet it still worked the mapped buttons, the pen movement and pressure on krita:

/dev/input/event15 is a tablet but not supported by libwacom
/dev/input/event3 is a tablet but not supported by libwacom
/dev/input/event2 is a tablet but not supported by libwacom
devices:
- name: 'Huion Kamvas 13'
  bus: 'usb'
  vid: '0x256c'
  pid: '0x006d'
  nodes: 
  - /dev/input/event14: 'Tablet Monitor Pad'
- name: 'Huion Kamvas 13'
  bus: 'usb'
  vid: '0x256c'
  pid: '0x006d'
  nodes: 
  - /dev/input/event13: 'Tablet Monitor Pen'

Thanks again!

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

Successfully merging this pull request may close these issues.

4 participants