Linux pen tablet driver

Arch Linux User Repository

Search Criteria

Package Details: xp-pen-tablet 1:3.2.0.210824-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/xp-pen-tablet.git (read-only, click to copy)
Package Base:	xp-pen-tablet
Description:	XP-Pen (Official) Linux utility (New UI driver)
Upstream URL:	https://www.xp-pen.com/download/index.html
Licenses:	LGPL3
Conflicts:	xp-pen
Submitter:	Poilrouge
Maintainer:	Poilrouge (rad4day)
Last Packager:	rad4day
Votes:	17
Popularity:	1.39
First Submitted:	2020-06-12 15:35
Last Updated:	2021-08-26 23:08

Dependencies (0)

Required by (0)

Sources (2)

Pinned Comments

stratus_ss commented on 2021-04-05 02:30

I am having the same problems as @linuxmobile. When I launch the GUI after installing from the AUR it says I need to be running as root (but the UI is blank except for the OK and Cancel buttons). I verified that the settings files were in my home directory. I also tried linking the config files from /usr/lib/pentablet/conf

/.local/share/pentablet but the same effect. The GUI is missing any options.

Any pointers as to where to check next? I have XP-PEN STAR G640

EDIT I contacted support and then sent me this: https://www.youtube.com/watch?v=tZmRZr7aH6M

After chown the /usr/lib/pentablet directory and unplugging and replugging the usb cord for the tablet the driver provided here worked as expected

Latest Comments

Poilrouge commented on 2021-09-05 21:24

@generic-muffin32 I don’t think there’s a way to make it run in background at the start. But if you want to not have it launched at the start, you can remove the /etc/xdg/autostart/xppentablet.desktop file.

generic-muffin32 commented on 2021-09-03 04:12

Is there any way to make this run in the background on start? I know that it is supposed to do this by default but since I am on i3wm I have to set what I want running on boot manually. So do you think there are some launch parameters I could use?

Cyprien_bzh commented on 2021-08-30 12:36

Sorry, it have been updated now with no problems. Perhap’s it was not available for few days.

rad4day commented on 2021-08-27 11:05

@Cyprien_bzh can you give more information about that?

The link clicked directly on here is giving a 403 because of the referer but the package is building for me on my PC and my build server using either yay or makepkg directly without a problem.

Cyprien_bzh commented on 2021-08-27 05:55

I can confirm that the link is not valid. I can’t update my package.

ptrLx commented on 2021-08-19 14:00

Hey there. It seems to me that the download link to xp-pen has become unvalid. A newer version (3.2) is available on the website.

Mashiroto commented on 2021-07-14 21:28

its seem to be working correct, i was using another person driver, unable to save xp-pen configuration. now its working. thx alot.

CIAvash commented on 2021-07-13 13:45

@zwastik running /usr/lib/pentablet/pentablet directly seems to kinda work. If it doesn’t, you can just run env QT_QPA_PLATFORM=xcb /usr/lib/pentablet/pentablet.sh .

zwastik commented on 2021-05-01 03:33

Any idea on how to run this natively under wayland? It seems /usr/lib/pentablet/plugins/platforms only has libqxcb.so Does this means only X11 is supported even though qt5-wayland is installed?

linuxmobile commented on 2021-04-25 18:24

curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://download01.xp-pen.com/file/2021/02/XP-PEN_Pentablet_3.0.5.201126-2.x86_64.tar.gz.zip Aborting. error downloading sources: xp-pen-tablet

Copyright © 2004-2021 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

Linux pen tablet driver

DIGImend kernel drivers

This is a collection of graphics tablet drivers for the Linux kernel, produced and maintained by the DIGImend project. We maintain this package to provide newer drivers for older kernel versions which don’t have them, and to allow users to test new drivers before we contribute them to the mainline kernel.

Consider becoming a patron of the project maintainer to help make more tablets work with Linux. You can also support the maintainer on Liberapay, or you can buy him a coffee!

Kernel v3.5 or newer is required.

Download appropriate files for one of the releases from the releases page. The «Download ZIP» link on the right of the GitHub page leads to the source of the current development version, use it only if you know what you’re doing.

Installing Debian package

If you’re using Debian or a derived distro, such as Ubuntu, and are installing a release, please use the .deb package. If you’re not using a Debian-based distro, or the .deb package didn’t work, you can install the driver using DKMS, or manually, as described below.

Installing from source

Source is either an unpacked release tarball (.tar.gz file), an unpacked source code archive downloaded from GitHub (.zip file), or source code checked out from Git.

Before installing from source in any way, make sure you have the headers for your kernel installed (on Debian-based systems):

or (on Fedora-based systems):

If you get «Error: Unable to find a match» from the above command, make sure your kernel is up-to-date, and if not, update it and try again.

Installing from source with DKMS

DKMS (Dynamic Kernel Module Support) is a system for installing out-of-tree Linux kernel modules, such as DIGImend kernel drivers. It helps make sure the modules are built with correct kernel headers and are properly installed, and also automatically reinstalls the modules when the kernel is updated.

Installing with DKMS is the recommended way of installing development versions of DIGImend kernel drivers.

To install with DKMS, make sure you have the dkms package installed (on Debian-based distros):

or (on Fedora-based distros):

After that, run the following command from the source directory to install:

Watch for any errors in the output, and if the drivers installed successfully, they will be automatically rebuilt and reinstalled each time the kernel is updated.

Installing from source manually

To install from source manually, first build the drivers. Run the following command in the source directory:

Then, to install the drivers, run this command in the same directory:

Note that if you built and installed the drivers this way, you will need to run make clean in the source directory, and then redo the above, after each kernel upgrade.

SSL errors during installation

On Ubuntu, and possibly other distros, the driver installation process attempts to cryptographically sign the modules being installed. Most of the users don’t have the system configured to support this, so during the installation they get error messages similar to these:

The above basically means that the system tried to sign the module, but couldn’t find the key to sign with. This does not interfere with module installation and operation and can safely be ignored. That is, unless you set up module signature verification, but then you would recognize the problem, and would be able to fix it.

After installing the drivers, make sure the previous versions of the drivers were unloaded. To do that, simply reboot the machine. Alternatively, execute the following command:

and reconnect the tablet.

If your tablet is supported, its pen will work after this, and applications will be able to recognize the pressure after appropriate configuration. Refer to the application documentation for instructions on how to do that, but in most cases it is enough to simply enable the tablet in the application.

By default, your tablet will be handled by the libinput X.org driver ( xserver-xorg-input-libinput package in Debian, Ubuntu, and derived distros, xorg-x11-drv-libinput in Fedora and derived distros). This driver will support reporting pen coordinates and pressure, and some frame controls.

Some tablets, however, can work with the Wacom driver, which has support for configuring pressure curves, keyboard shortcuts for buttons on the tablet frame, and other advanced features. This driver package includes configuration enabling Wacom driver for tablets that are known to work with it.

For those tablets, all you need to do is make sure the Wacom driver is installed, which is done automatically when installing the driver from the .deb package. In other cases, you can install the driver package ( xserver-xorg-input-wacom or xorg-x11-drv-wacom ) yourself. To verify that your tablet is handled by the Wacom driver, see if its devices appear in the output of xsetwacom list .

Enabling Wacom X.org driver

If this driver package hasn’t configured your tablet to work with the Wacom driver, but you know it works, or would like to try to make it work, you can write the following to /etc/X11/xorg.conf.d/50-tablet.conf file:

would be the tablet’s USB vendor and product IDs respectively, as seen in lsusb output. E.g. if your tablet’s line in lsusb output looks like this:

then your /etc/X11/xorg.conf.d/50-tablet.conf should look like this:

You will need to log out of your X.org session and login again, or simply restart your machine for these changes to take effect. If your configuration worked, please open an issue, or contribute code directly, to have configuration for your tablet included into this driver package.

Configuring Wacom X.org driver

If your tablet is handled by the Wacom driver, you should be able to use the xsetwacom tool to configure the advanced features.

For example, if xsetwacom list produces this output:

you can assign Ctrl-Z («Undo») key combination to the fifth button on the tablet frame this way:

Note that buttons are numbered 1, 2, 3, 8, 9, 10, and so on, i.e. buttons 4, 5, 6, and 7 are not used. They’re reserved for vertical and horizontal scrolling events by the X server.

Another example: if xrandr output has this line:

you can restrict the tablet input to that display like this:

See the xsetwacom man page for more parameters and details.

Wacom GUI configuration tools

Note that so far, in most cases, graphical Wacom tablet configuration tools won’t work with non-Wacom tablets, and you will need to use the xsetwacom tool, even if the Wacom X.org driver supports them.

To uninstall a Debian package simply use your favorite package-management tools.

To uninstall a DKMS-installed package execute make dkms_uninstall as root in the package source directory.

To uninstall a manually-installed package execute make uninstall as root in the package source directory.

If you’ve manually installed a version of this package before, please uninstall it before installing another one, using the sources you used for installation.

Building Debian package

If you’re a developer, or simply want to install a development version of the drivers as a Debian package, make sure you have dpkg-dev , debhelper , and dkms packages installed, and run the following command in the source directory:

The resulting package files will be written to the parent directory.

DKMS issues preventing correct installation

If you’re installing Debian packages, or installing from source with DKMS, you might hit one of DKMS bugs which prevent some of the driver modules from installing.

They make DKMS produce messages like this:

while trying to install the drivers.

Fixes for these were accepted upstream (first fix and second fix) and should eventually appear in distributions. Meanwhile, to fix the issues, you can apply these yourself, or execute the following command:

Be aware that the operation of the above command is inexact, and might not work, or might break DKMS. You’ve been warned. In any case, simply reinstall DKMS to restore it.

Systems with Secure Boot enabled

If your system has Secure Boot enabled, then the installed driver modules won’t be permitted to load. You will see messages like «Required key not available». To make them work, you will need to sign them, or disable Secure Boot entirely. See documentation for your Linux distribution on how to sign kernel modules, or documentation for your computer’s UEFI firmware on how to disable Secure Boot.

Touch ring/strip scrolling doesn’t work in Gnome

Scrolling with a touch ring or a touch strip doesn’t work in Gnome version 3.24 and later. At the moment there doesn’t seem to be a workaround beside not using Gnome.

If you have any problems with the drivers, look through HOWTOs on the project website, and search for solutions and report new issues at the issues page on GitHub.

If you find somebody has already reported your issue and it’s not resolved yet, leave a thumbs-up 👍 reaction on the first post in the issue. This will let developers identify popular issues and pick them first for solving!

Join the #DIGImend channel on irc.libera.chat to discuss the drivers, tablets, development, to ask for help, and to help others!

About

DIGImend graphics tablet drivers for the Linux kernel

Источник

Linux pen tablet driver

OpenTabletDriver is an open source, cross platform, user mode tablet driver. The goal of OpenTabletDriver is to be cross platform as possible with the highest compatibility in an easily configurable graphical user interface.

All statuses of tablets that are supported, untested, and planned to be supported can be found here. Common issue workarounds can be found in the wiki for your platform.

Running OpenTabletDriver binaries

OpenTabletDriver functions as two separate processes that interact with each other seamlessly. The active program that does all of the tablet data handling is OpenTabletDriver.Daemon , while the GUI frontend is OpenTabletDriver.UX.* , where * depends on your platform 1 . The daemon must be started in order for anything to work, however the GUI is unnecessary. If you have existing settings, they should apply when the daemon starts.

1 Windows uses Wpf , Linux uses Gtk , and MacOS uses MacOS respectively. This for the most part can be ignored if you don’t build it from source as only the correct version will be provided.

Building OpenTabletDriver from source

The requirements to build OpenTabletDriver are consistent across all platforms. Running OpenTabletDriver on each platform requires different dependencies.

Источник