Arch Linux User Repository

Doesn't save the config anymore. Not since the last or 2nd last update. Even if I export the config then import it it's back to default shortcuts

Edit: Never mind, this is an issue on Windows as well... Unbelivable

The sha512sums is incorrect and needs to be updated, and the version too. The current deb file is named XPPenLinux-3.3.9.230222-1.x86_64.deb

Why does this use the deb file instead of the tar.gz?

@alexandria The driver is available on the English website and comes in 3 formats: rpm, deb, tar.gz - all are binary, no sources. The tarball has the LGPL license file inside but it's likely only referring to the bundled Qt5. The 'pentablet' binary in particular seems to be proprietary, but there is no clear information anywhere, there is only copyright notice in the app itself.

This is very sus. This package claims a LGPL license, but the source website (https://www.xp-pen.ru/) does not offer a source tarball for download, nor list to a version tracking repo or external resource where I might find it on the website. The closest thing to source code they offer is a Windows-only SDK.

Furthermore, the Linux version isn't even available on the English website (https://xp-pen.com).

Which makes me suspect that they are using LGPL-licensed components for the Linux driver, but didn't want to actually release their source code, and so only released the driver for Windows and Mac on the non-Russian version. I hope I'm wrong here. Please let me know if anyone knows where to find the source code for this driver.

UPDATE: I emailed them, and their staff flatly ignored the issue at hand.

Date: 2023-02-12 13:15:37
To:  service@xp-pen.com
Subject: Source code>To whom it may concern,
>
>The official Linux version of your driver, as pulled from:
>https://download01.xp-pen.com/file/2022/08/XPPen-pentablet-3.2.3.220323-1.x86_64.deb
>
>This file (and the adjacent binary tarball) both claim a LGPLv3
>license, which is classified as a weak copyleft license, implying that
>source code is available -- but I could not find any source code
>tarballs available for download. Can you please provide me the source
>code tarball, or a source repo link so that I can build the software
>from source and modify its functionality for my use case?
>
>Thanks!
>
>-Alexandria

And their response:

Hello,

We only have SDK for our tablets. Please check on this link: Developer Center | XPPen (xp-pen.com)

Thank you,
Tina

Given this new information, I would like to request that the license on this package be changed from LGPL to unknown, as people will mistake it for FOSS otherwise.

here is more sane version of the pkgbuild without that install file

pkgname=xp-pen-tablet
pkgver=3.2.3.220323
pkgrel=10
pkgdesc="XP-Pen official driver with GUI configuration tool"
arch=('x86_64')
url='https://www.xp-pen.com'
license=('LGPL3')
depends=('libxinerama' 'libxrandr' 'libxtst')
source=("XPPen-pentablet-${pkgver}-1.${arch}.tar.gz::${url}/download/file/id/1936/pid/525/ext/gz.html")
md5sums=('aa9581d987f954c9d69288d5a7b06aa5')

package() {
       cp -r $srcdir/xp-pen-pentablet-$pkgver-1.$arch/App/* $pkgdir

       #don't create /lib
       install -Dm644 $pkgdir/lib/udev/rules.d/10-xp-pen.rules $pkgdir/usr/lib/udev/rules.d/10-xp-pen.rules
       rm -rf $pkgdir/lib

       #make those executable
       chmod 755 $pkgdir/usr/lib/pentablet/pentablet.sh
       chmod 755 $pkgdir/usr/lib/pentablet/pentablet

       #fix license permissions
       chmod 644 $pkgdir/usr/lib/pentablet/LGPL

       #config is global so everyone needs write access
       chmod 666 $pkgdir/usr/lib/pentablet/conf/xppen/config.xml

       #minimize GUI on autostart
       sed -re 's/(^Exec=\/.+)/\1 \/mini/gi' -i ${pkgdir}/etc/xdg/autostart/xppentablet.desktop
}

Hi, is there a way to disable autostart? I deleted "/etc/xdg/autostart/xppentablet.desktop" but it still starts automatically. I also checked "~/.config/autostart" , nothing is there.

Edit: It was solved the next day somehow by itself.

I think it is bad that xppen unpacked its files with user permissions. Despite possible problems with updates, this is not the way to do it.

@effeffe Sorry! It was my mistake. Checksum is fixed.

Hello! The current pkgbuild reports a different sha256sum for the install.sh.patch than the one present on the repository. Can a maintainer/collaborator investigate if this is just a simple repackaging mistake, or something else is going on?

Thank you