xf86-input-wacom VS libwacom

I tried the QT_XCB_TABLET_LEGACY_COORDINATES=1 fix on https://github.com/linuxwacom/xf86-input-wacom/wiki/Known-Issues#android-misdetect

What if you switch to x11 when using the tablet and log into wayland when you're done? Probably not ideal and you'll lose the touchpad gestures. their wiki has more info but might not be what you're looking for https://github.com/linuxwacom/xf86-input-wacom/wiki/Wayland

May be worth to take a look at https://github.com/linuxwacom/xf86-input-wacom/wiki/Known-Issues and in general the page. There seems to be quite a bit you can configure and calibrate by hand.

On most distros it should just work. However, there are a few hiccups in some distros / tablets. See this link: https://github.com/linuxwacom/xf86-input-wacom/wiki/Known-Issues

It doesn't look like a bug report was ever filed by the other reporter. Would you mind creating a bug report at https://github.com/linuxwacom/xf86-input-wacom/issues/ for us on the linuxwacom team to track? You should include the following information in your report:

Major issues ------------ Breeze Light color scheme not initially applied correctly - https://bugzilla.redhat.com/show_bug.cgi?id=1963709 xorg-x11-drv-wacom breaks touchscreen touch events for Qt apps - Upstream issue: https://github.com/linuxwacom/xf86-input-wacom/issues/178 - Maybe work around it in Fedora? https://pagure.io/fedora-kde/SIG/issue/77 - Workaround: run xsetwacom set `xsetwacom --list devices | grep TOUCH | cut -d " " -f 8` gesture off GTK apps produce horrible jarring beeps when run on KDE Plasma - Upstream issue: https://phabricator.kde.org/T14523 - Maybe work around it in Fedora? https://pagure.io/fedora-kde/SIG/issue/83 Installing KDE Connect should automatically create a relevant firewall allow-list for it - https://bugzilla.redhat.com/show_bug.cgi?id=1968002 Minor issues ------------ DNF packageKit plugin does not support DependsOn operation, so Discover can't show app dependencies - https://bugzilla.redhat.com/show_bug.cgi?id=1983315 org.freedesktop.accounts.change-own-user-data unnecessarily prompts for admin password, so various System Settings Users KCM operations are annoying for admins and unusable for regular users - https://bugzilla.redhat.com/show_bug.cgi?id=1988509 Feature requests/nice-to-haves ------------------------------ In Fedora, plasma-discover-flatpak-backend should add flathub repo during installation - https://bugzilla.redhat.com/show_bug.cgi?id=1524756 Package CryFS so that plasma-vaults can use it as a backend - https://bugzilla.redhat.com/show_bug.cgi?id=1963740 Install plasma-firewall by default - https://pagure.io/fedora-kde/SIG/issue/34

xorg-x11-drv-wacom breaks touchscreen touch events for Qt apps - Upstream issue: https://github.com/linuxwacom/xf86-input-wacom/issues/178 - Maybe work around it in Fedora? https://pagure.io/fedora-kde/SIG/issue/77 - Workaround: run xsetwacom set xsetwacom --list devices | grep TOUCH | cut -d " " -f 8 gesture off

The 13ALC6 has tilt, so it's very likely the 13ALC7 does, too. But, like you said, that's not direct information. Check your digitizer on Device Manager > Human Interface Devices > HID Touchscreen or HID Pen. If the hardware ID is 52xx (for example 52a2) it's probably AES 2.0.

You can check Device Manager and see if the four-character Hardware ID of your HID Pen or HID Touchscreen devices (under Human Interface Devices) match any of the hardware IDs on the list at libwacom, or you could borrow an AES-2.0-only pen and see if it works.

Good question! Technically yes, you can compare the "HID Touchscreen" or "HID Pen" Device ID in Device Manager to the list on libwacom which is an open-source project that helpfully lists lots of digitizers. If it says "Sensor Type: AES", "Features: Touch (Integrated), Tilt", it's AES 2.0 (because 1.0 doesn't have tilt).

The same ID 256c:006d as yours -> https://github.com/linuxwacom/libwacom/issues/469

The name is wacom because wacom was the originator, but I think that it will work with other manufacturers if it is listed inlibwacom.

Technically you can look at the 4-hex-digit hardware ID of the pen digitizer in Device Manager and then look it up in libwacom, but obviously that's not how it's supposed to be. Wacom (and Microsoft) doesn't publish the version of their digitizers anywhere so it's always a game of test-which-pens-work-on-it.

So, for instance, I should be able to see the stylus in the Wacom section in the Settings but don't because I assume it's yet to have been added to the libwacom database. At least that's what I understand based on what I've read so far on it. My next step is to see if I can get it to work based on this.

This issue and its workaround is described at https://github.com/linuxwacom/libwacom/issues/281. Briefly, you'll need to edit the libwacom tablet definition for your tablet, adding 0xffffe to the end one of the lines. After saving the changes you should be able to open the Graphics Tablet settings without it crashing.

Check this. If it's listed here and entered about a year ago or more, then it's pretty much guaranteed to work out of the box and be configurable in the GNOME settings.