Package Details: g13-git 20160120-5

Git Clone URL: https://aur.archlinux.org/g13.git (read-only)
Package Base: g13
Description: Userspace driver for the Logitech G13 Keyboard
Upstream URL: https://github.com/ecraven/g13
Licenses: unknown
Submitter: punkrockguy318
Maintainer: khampf
Last Packager: khampf
Votes: 5
Popularity: 0.011924
First Submitted: 2015-09-04 03:37
Last Updated: 2016-04-03 17:18

Dependencies (3)

Required by (0)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

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:
https://github.com/zekesonxx/g13-profiles/blob/master/default.bind

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

brittyazel commented on 2016-02-26 21:17

# grep g13 /etc/passwd /etc/group <(ps axu)
/etc/passwd:g13:x:613:613:Logitech G13 daemon:/run/g13d:/usr/bin/nologin
/etc/group:wheel:x:10:root,britt,g13
/etc/group:g13:x:613:britt
/dev/fd/63:root 492 0.1 0.0 91612 7344 ? Ssl 13:12 0:00 /usr/bin/g13d --config /etc/g13/default.bind --pipe_in /run/g13d/g13-0 --pipe_out /run/g13d/g13-0_out &
/dev/fd/63:britt 1845 0.0 0.0 10756 2180 pts/0 S+ 13:14 0:00 grep g13 /etc/passwd /etc/group /dev/fd/63


# ls -lah /dev/uinput /run/g13d
crw-rw----+ 1 root root 10, 223 Feb 26 13:12 /dev/uinput

/run/g13d:
total 0
drwxr-xr-x 2 g13 g13 80 Feb 26 13:12 .
drwxr-xr-x 25 root root 580 Feb 26 13:12 ..
prwxrwxrwx 1 root g13 0 Feb 26 13:12 g13-0
prwxrwxrwx 1 root g13 0 Feb 26 13:12 g13-0_out

khampf commented on 2016-02-26 15:53

Thanks for trying out the package brittyazel! I will look over the wiki as soon as I am a little more confident in the user/group problem. I usually test if the g13d service gets loaded as expected using "ps axu | grep g13" but I have another service riding on top of the normal daemon (a clock written i C instead of scripts, I will release it under GPL and package it later).

Let's compare some output (I might have missed something in the install file)
# grep g13 /etc/passwd /etc/group <(ps axu)
/etc/passwd:g13:x:613:613:Logitech G13 daemon:/run/g13d:/usr/bin/nologin
/etc/group:wheel:x:10:root,core,g13
/etc/group:g13:x:613:
/proc/self/fd/13:g13 814 0.0 0.0 157172 1300 ? Ssl feb25 0:39 /usr/bin/g13d --config /etc/g13/default.bind --pipe_in /run/g13d/g13-0 --pipe_out /run/g13d/g13-0_out &

# ls -lah /dev/uinput /run/g13d
crw-rw----+ 1 root root 10, 223 25 feb 12.32 /dev/uinput

/run/g13d:
total 0
drwxr-xr-x 2 g13 g13 80 25 feb 12.32 .
drwxr-xr-x 29 root root 920 25 feb 19.03 ..
prwxrwxrwx 1 g13 g13 0 26 feb 17.53 g13-0
prwxrwxrwx 1 g13 g13 0 25 feb 12.32 g13-0_out

brittyazel commented on 2016-02-26 06:45

Ok I was able to get it to work by taking out the "User=g13" line from the .service file, and by adding my personal user to the g13 group. Something is up with the g13 user and/or the something is up with trying to run the command as that user

brittyazel commented on 2016-02-26 06:19

if I evoke the command:
"/usr/bin/g13d --config /etc/g13/default.bind --pipe_in /run/g13d/g13-0 --pipe_out /run/g13d/g13-0_out"

manually, everything works fine. However when I comment out the last two lines in rules.d and plug it in, the screen changes to the logo but no keypresses work. I think something may be up with the .service file

brittyazel commented on 2016-02-26 05:32

@Khampf thank you for the work you have done. Do you think you could update the wiki though with better instructions? The ones that are there now don't really apply anymore