Package Base Details: g13

Git Clone URL: https://aur.archlinux.org/g13.git (read-only, click to copy)
Submitter: prg
Maintainer: khampf
Last Packager: khampf
Votes: 7
Popularity: 0.000000
First Submitted: 2015-09-04 03:37 (UTC)
Last Updated: 2020-05-22 21:20 (UTC)

Packages (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

khampf commented on 2019-12-29 05:31 (UTC)

Ok, here we go then. This repo is now based on my fork and my fixes. And after having trouble with boost libraries I just reworked all parts relying on boost to modern C++. Current status is "works for me" but it might work for you too

khampf commented on 2019-12-21 20:55 (UTC)

As I really am short on time I quickly retagged the develop branch to v1.0.1 (I have introduced versioning) and made a PKGBUILD for testing it installed from a package. PKGBUILD here: https://pastebin.com/YPbFwm0M If this packaged version works for me (tm) over a couple of days I will switch repo source in this AUR package and update in AUR

(I can not publish it right off without having tested it packaged first, but I also wanted all interested people to be able to test it right away)

purpuru commented on 2019-12-19 06:31 (UTC) (edited on 2019-12-19 06:35 (UTC) by purpuru)

@mangaman For the version you have compiled from git have you checked the arch wiki? The syntax is all there, you can either cat text files or pipe individual commands.

https://wiki.archlinux.org/index.php/Logitech_G13#Configuring

mangaman commented on 2019-12-18 06:26 (UTC) (edited on 2019-12-18 06:29 (UTC) by mangaman)

I have been really excited to try and get this working. I have a G13 and it is very hard to try playing games without it anymore. I just switched to Linux as my gaming platform. I have used Linux a little in the past, but not as a daily driver.

Anyways, back to the subject. I wanted to show my interest in this project and ask for some help. I have tried to install this package using pamac-manager and pacman on Manjaro and I get the same error. The error is :

==> Starting prepare()... ==> Modifying udev 91-g13.rules ... ==> Starting pkgver()... fatal: No names found, cannot describe anything. ==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace. ==> ERROR: pkgver() generated an invalid version: ==> Trying to read git version ... ==> Git version failed, using date of last commit ... 20160120

I have the full output at https://forum.manjaro.org/t/logitech-g13-keyboard-help/115313 . I did try building it from source and got it to display the "Linux Inside" stuff but it still doesn't seem to work.

Thanks for the help in advance.

khampf commented on 2019-12-14 16:33 (UTC)

@purpuru I have been using my rewritten version for a while, thought it best to try it for a while before going further after a the rather big changes I did. I will take another look at it soon now that I know someone else but me is using it :)

purpuru commented on 2019-12-13 21:20 (UTC)

Any chance of updating this? I built it from source (from your repo) and it works fine but it would be nice to have it through pacaur.

khampf commented on 2019-03-26 19:58 (UTC)

I actually refactored the source and replaced everything depending on boost in the upstream source. I got it working without boost but after more refactoring I have a linking problem that I will fix when I get a little more time (hopefully in a couple of weeks). If someone wants to play around and test my last should-be-stable it is at https://github.com/khampf/g13

deprecated13 commented on 2019-03-26 17:52 (UTC)

Adding CXXFLAGS=-ggdb before the make call in PKGBUILD also worked for me to stop the segfault.

Ei_Diablo commented on 2018-12-23 03:17 (UTC)

Edit PKGBUILD to use https://github.com/dhardy/g13. Worked 100% for me

titibandit commented on 2018-11-03 02:19 (UTC)

The package is also segfaulting for me, but as krafgor said, if you use the --log_level switch with those values: "warning", ""fatal" and "error", the executable doesn't segfault anymore. It somehow seems to be link with the output that the program produces depending on that log_level switch. I'm not sure how I could debug this further