libwacom VS libcurl

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.

Then, in another terminal window, we use curl to hit the endpoint:

Made a PR to curl in line with the above: https://github.com/curl/curl/pull/13338

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

From the GitHub Issue itself, the maintainer did end up creating a PR to fix a related issue: https://github.com/curl/curl/issues/12983

Also, the bot filed another issue despite the complaints.

This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.