Package Details: g13-git 20160120-5

Git Clone URL: (read-only)
Package Base: g13
Description: Userspace driver for the Logitech G13 Keyboard
Upstream URL:
Licenses: unknown
Submitter: punkrockguy318
Maintainer: khampf
Last Packager: khampf
Votes: 4
Popularity: 0.101961
First Submitted: 2015-09-04 03:37
Last Updated: 2016-04-03 17:18

Dependencies (3)

Required by (0)

Sources (3)

Latest Comments

khampf commented on 2016-06-07 20:29

osvein: I have given it thought but not done anything about it, has to do with original PKGBUILD submitted before I maintained it. I will take a closer look soon

osvein commented on 2016-06-03 16:42

You probably don't want pkgbase to be something else than pkgname, unless it's a split package, which it currently isn't. If you just want a variable in the PKGBUILD which does not include the -git suffix, a better approach is to create a seperate variable, eg. _pkgname.

What you probably do want, however, is to declare the package a provider of g13.

khampf commented on 2016-04-03 16:23

jukebone: You're right, we should be using -r. I just set it up that way when testing initially and the number 613 reminds me of g13

jukebone commented on 2016-04-03 07:10

Why do you create the group and user with the fixed GID/UID of 613? This might clash with existing accounts, which it did for me. Maybe you should try -r for groupadd and useradd instead of hardcoding the IDs.

brittyazel commented on 2016-02-29 21:58

Awesome thanks. I'm just excited to finally have my g13 working in a way that is practical, and I'm just trying to do my part to help out. Let me know if you need me to test any changes.

khampf commented on 2016-02-29 19:21

I also got the "remove primary group of user" error but have sinced changed the order in which group and user g13 are deleted. The service should of course be stopped first, I will add that to the uninstall part next time around.

Why I left those parts commented out is due to the possibility of errors in the udev-rules, they are not well tested yet. They might be considered a bit more safe now but I think other packages might have problems with /dev/uinput too and this way of fixing it might clash with others. And it's a hack at best, using "uaccess" by itself should work but it does not.

Your wiki edits were fine so I let them be, uinput is mentioned a lot now but I will edit the wiki again when I'm certain uinput permissions are working.

brittyazel commented on 2016-02-27 18:48

I made some minor wiki changes for clarifications sake, please edit them as you see fit

brittyazel commented on 2016-02-27 18:18

When removing I get this:
"Removing user and group ...
groupdel: cannot remove the primary group of user 'g13'
userdel: user g13 is currently used by process 431
error: command failed to execute correctly"

You should probably add a line to kill the service before removing these users or groups, and you need to probably delete the user before group for order of events to be happy

brittyazel commented on 2016-02-27 18:16

Ok uncommenting all three lines in the .rules is working! I get keypresses!

Quick note, on the wiki you said that default.bind was located in /etc/g13d, it actually should be in /etc/g13 per your .service file. I went ahead and corrected it in the wiki.

Second, on package install we don't create the directory /etc/g13, as it is crucial to loading default.bind perhaps it would be worth our while to, as well as potentially drop in this example file to help people along and give them some feedback as to if it even works at all:

Third, why not uncomment all three lines in the .rules file for the user? Why the manual intervention? I'm afraid that a user who just want's his g13 to work, is not going to understand the importance of editing the .rules file (nor manually creating the /etc/g13 dir and making a default.bind file for that matter). They may just write this package off as bugged and move on. Is there a solid situation where setting the uinput group to wheel and the hotplugging is undesirablable?

khampf commented on 2016-02-27 14:57

Now I have had a go at editing the wiki as well

All comments