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: 3
Popularity: 0.281524
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-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

khampf commented on 2016-02-27 13:40

For me default.bind is always loading (first line makes the display go red). But I think I found out what is going on. Everything else seems to be working except that g13d is unable to write to /dev/uinput. Changing the udev rule for it to make it owned by group wheel works for me, I'll repackage and then you have to upgradre and re-edit /usr/lib/udev/rules.d/91-g13.rules and key input should work again.

khampf commented on 2016-02-27 12:59

From what I can see the differences are that your g13d daemon runs as root making g13-0 and g-13-0_out fifos also owned by root. What happens if you And that I've also added myself to the g13 group. I will uninstall, user and group and all dirs and reinstall and see if I get something out of it.

If g13d is running as user g13 and your user is in the g13 group you should be able to throw bitmaps and configs at the fifo, what happens if you for example do:
cat /usr/share/doc/g13-git/examples/starcraft.lpbm > /run/g13d/g13-0

All comments