Search Criteria
Package Details: g13-git v1.0.4.r0.g0a8d6e8-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/g13.git (read-only, click to copy) |
---|---|
Package Base: | g13 |
Description: | Userspace driver for the Logitech G13 Keyboard |
Upstream URL: | https://github.com/khampf/g13 |
Licenses: | unknown |
Submitter: | prg |
Maintainer: | khampf |
Last Packager: | khampf |
Votes: | 6 |
Popularity: | 0.000000 |
First Submitted: | 2015-09-04 03:37 (UTC) |
Last Updated: | 2020-05-22 21:20 (UTC) |
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »
Nihilman commented on 2020-05-15 18:11 (UTC) (edited on 2020-05-15 20:47 (UTC) by Nihilman)
Hello, having some issue under manjaro. I'm not an expert but I found that the PKGBUILD point into the develop branch instead of the master branch and the G13.cpp is missing in the develop branch(this is the issue). I have modified line 27: "git checkout develop" by "git checkout master" and it compile for me. I've modified the syntax of 2 others lines too : 51 : " install -m 755 pbm2lpbm "${pkgdir}/usr/bin"" by 51 : " install -m 755 pbm2lpbm "${pkgdir}"/usr/bin"
54 : "install -dm 755 "{pkgdir}"/etc/g13" by 54 : "install -dm 755 "${pkgdir}"/etc/g13" (syntax did not seems to be good for me ?????) After that building the pkg by my own with makepkg and it did it! thank you for your time.
khampf commented on 2020-05-07 00:55 (UTC)
I fixed the loop on LIBUSB_ERROR_NO_DEVICE, merged some work on mousebutton support and worked a little on cleaning up the codebase. Completely untested so I will run the changes in my upstream github develop-branch and test a couple of days before I push the new version (v1.0.2).
khampf commented on 2020-05-06 13:57 (UTC)
This packaged version is the one I edited so it might no longer be in sync with original upstream but I feel this might be an easy fix as it should just retry a couple of times and eventually exit on LIBUSB_ERROR_NO_DEVICE. I'll try to fire up my dev environment and see how dusty it is...
I would first check original upstream for possible fixes, then fix it myself if no such exists and of course I will also suggest those fixes upwards.
achilleas commented on 2020-05-06 13:20 (UTC) (edited on 2020-05-06 13:20 (UTC) by achilleas)
I've seen the same behaviour. Pegs a single core to 100%. I made a habit of stopping the service manually when I disconnect, but I didn't know if it's an issue to be reported here or upstream.
laoshanlong commented on 2020-05-06 13:14 (UTC) (edited on 2020-05-06 13:15 (UTC) by laoshanlong)
Disconnecting the device before stopping the service seems to cause systemd-journald high cpu usage. Upon inspection, the journal is littered with millions of these such messages:
May 06 06:06:41 patches g13d[499549]: 1588770401 ERROR : Error while reading keys: -4 (LIBUSB_ERROR_NO_DEVICE No such device (it may have been disconnected))
achilleas commented on 2020-01-11 20:59 (UTC) (edited on 2020-01-11 21:00 (UTC) by achilleas)
log4cpp is as runtime dependency, not just a build/make dep. It should be in the "depends" array.
domoaligato commented on 2020-01-07 04:50 (UTC)
thanks. it installs now.
khampf commented on 2020-01-07 01:06 (UTC)
I forgot to include log4cpp as a dependency. Fixed in release 2
domoaligato commented on 2020-01-02 19:45 (UTC)
==> Sources are ready. :: Building g13-git package(s)... ==> Making package: g13 v1.0.1.r0.ge6ad66c-1 (Thu 02 Jan 2020 11:45:00 AM PST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting pkgver()... ==> Starting build()... GIT_VERSION = 1.0.1-dirty
define GIT_VERSION "1.0.1-dirty"
g++ -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -std=c++17 -c g13_main.cpp In file included from g13_main.cpp:1: g13.hpp:13:10: fatal error: log4cpp/Category.hh: No such file or directory 13 | #include <log4cpp/Category.hh> | ^~~~~~~~~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:13: g13_main.o] Error 1 ==> ERROR: A failure occurred in build(). Aborting... :: failed to build g13-git package(s)
purpuru commented on 2019-12-30 15:40 (UTC)
Worked perfectly for me!
Thx
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »