Package Details: wootility-appimage 4.6.15-1

Git Clone URL: https://aur.archlinux.org/wootility-appimage.git (read-only, click to copy)
Package Base: wootility-appimage
Description: Utility for configuring Wooting keyboards (binary AppImage version)
Upstream URL: https://wooting.io/wootility
Keywords: configuration keyboards wootility wooting
Licenses: unknown
Conflicts: wootility
Provides: wootility, wootility-lekker
Submitter: Freso
Maintainer: Freso (shaybox, AutoUpdateBot)
Last Packager: AutoUpdateBot
Votes: 7
Popularity: 0.000000
First Submitted: 2018-07-14 18:07 (UTC)
Last Updated: 2024-03-02 07:58 (UTC)

Latest Comments

Pulec commented on 2023-01-20 14:58 (UTC)

I was dumb and didn't check the rules file and I spent some time figuring out why wootility won't detect the keyboard.

Rules expect for the user to be in "input" group, a notice during installation would be great.

This v3 works fine with the first Wooting One, only via USB 2.0 though, on USB 3.0 the utility lags as crazy and can't save settings anyway.

shawly commented on 2022-07-23 19:29 (UTC)

Could you update this to 3.6.16 ?

diff --git a/.SRCINFO b/.SRCINFO
index da7a39b..fa7c961 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,6 +1,6 @@
 pkgbase = wootility-appimage
    pkgdesc = Utility for configuring Wooting keyboards (binary AppImage version)
-   pkgver = 3.6.15
+   pkgver = 3.6.16
    pkgrel = 1
    url = https://wooting.io/wootility
    install = wootility-appimage.install
@@ -10,9 +10,9 @@ pkgbase = wootility-appimage
    depends = fuse2
    provides = wootility
    conflicts = wootility
-   noextract = wootility-3.6.15.AppImage
+   noextract = wootility-3.6.16.AppImage
    options = !strip
-   source = https://s3.eu-west-2.amazonaws.com/wooting-update/wootility-linux-latest/wootility-3.6.15.AppImage
+   source = https://s3.eu-west-2.amazonaws.com/wooting-update/wootility-linux-latest/wootility-3.6.16.AppImage
    source = 70-wooting.rules
    b2sums = a4e3ab61b95141b655cc11280b1b3e74c22fae3c55c448411a5101f273e12b33baeba34e476ecd82c030bb3dda62f29ee6b259071aa22d8d245756766d046ecc
    b2sums = c26f695826bd32456bc5c145b8e4462059b1c0de02b86f1622c848b9aa85bc4294c672be7122d0685fca872a9322c3207df1bb15b2e72781a6425dfca1f02d86
diff --git a/PKGBUILD b/PKGBUILD
index 481c457..d843046 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Frederik “Freso” S. Olesen <archlinux@freso.dk>
 _pkgname=wootility
 pkgname=${_pkgname}-appimage
-pkgver=3.6.15
+pkgver=3.6.16
 pkgrel=1
 pkgdesc='Utility for configuring Wooting keyboards (binary AppImage version)'
 arch=('x86_64')
@@ -17,7 +17,7 @@ install=$pkgname.install
 source=("https://s3.eu-west-2.amazonaws.com/wooting-update/wootility-linux-latest/${_appimage}"
         '70-wooting.rules')
 noextract=("${_appimage}")
-b2sums=('a4e3ab61b95141b655cc11280b1b3e74c22fae3c55c448411a5101f273e12b33baeba34e476ecd82c030bb3dda62f29ee6b259071aa22d8d245756766d046ecc'
+b2sums=('79a32462cb3f375344ace2a4785c950854b8a7dd027d9c1e7c24696135f641d1d88f56ccbc2dfadc53d278e291bf11735d81d860e57b83cb981366d4930bf641'
         'c26f695826bd32456bc5c145b8e4462059b1c0de02b86f1622c848b9aa85bc4294c672be7122d0685fca872a9322c3207df1bb15b2e72781a6425dfca1f02d86')

 prepare() {

deemon commented on 2022-01-25 07:53 (UTC) (edited on 2022-01-25 08:14 (UTC) by deemon)

This appimage stopped working for me with my Wooting One. I mean the appimage works and the app starts, but it does not detect my WootingOne anymore.

shaybox commented on 2021-08-31 22:01 (UTC)

@mixlos that's for Wooting Two Lekker & HE only, Wooting One & Two still use and will forever use the old VID

mixlos commented on 2019-03-10 07:56 (UTC)

Please update 70-wooting.rules It should be ATTRS{idVendor}=="03eb" everywhere.

Freso commented on 2019-03-08 15:01 (UTC)

@N00byKing Huh. AppImages are supposed to be entirely self-contained. What is the output if you run this AppImage without fuse2 installed?

N00byKing commented on 2019-03-05 10:52 (UTC)

Just noticed that wootility depends on fuse2, please add

N00byKing commented on 2018-12-22 16:27 (UTC)

Package is really out-of-date, please update