Search Criteria
Package Details: g910-gkeys-git 0.3.0.r19.g4b1f05e-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/g910-gkeys-git.git (read-only, click to copy) |
---|---|
Package Base: | g910-gkeys-git |
Description: | GKey support for Logitech G910 Keyboard on GNU/Linux |
Upstream URL: | https://github.com/JSubelj/g910-gkey-macro-support |
Keywords: | daemon g910 gkey-support gkeys hotkeys logitech macros |
Licenses: | GPL3 |
Submitter: | cleptes |
Maintainer: | jlaunay |
Last Packager: | jlaunay |
Votes: | 2 |
Popularity: | 0.001231 |
First Submitted: | 2019-02-26 16:58 (UTC) |
Last Updated: | 2023-10-07 12:08 (UTC) |
Dependencies (7)
- python-pyusb (python-pyusb-gitAUR)
- python-uinputAUR
- git (git-gitAUR, git-glAUR) (make)
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-wheel (make)
- systemd (systemd-chromiumosAUR, systemd-gitAUR, systemd-fmlAUR, systemd-selinuxAUR, sysupdated-systemd-gitAUR) (make)
Latest Comments
profiluefter commented on 2023-10-07 12:23 (UTC)
Thank you, it works without issues now!
jlaunay commented on 2023-10-07 12:10 (UTC)
@Profiluefter I took time to check and pushed an update. It should be ok now.
profiluefter commented on 2023-10-06 14:07 (UTC)
@jlaunay I completely uninstalled the package and rebuilt it from the AUR and get the exact same output as you show in your code snippet. However, it shows that the conf file still gets installed into
/etc/modules-load.d/uinput-g910-gkeys.conf/uinput-g910-gkeys.conf
.If I reboot while the file is in that subdirectory I get an error message during the boot process for some systemd service. If I manually move that file outside the directory and rename it so that is has the same name again (after deleting the directory) it works again. Does it work for you in the subdirectory configuration?
jlaunay commented on 2023-10-03 12:09 (UTC)
Hi, I don't think so. Maybe you should first uninstall to delete the
uinput-g910-gkeys.conf
folder.profiluefter commented on 2023-10-03 11:39 (UTC)
Hi, I think there's still the issue that the kernel module gets installed into
/etc/modules-load.d/uinput-g910-gkeys.conf/uinput-g910-gkeys.conf
ararhoo commented on 2023-09-13 16:51 (UTC) (edited on 2023-09-13 16:51 (UTC) by ararhoo)
@jlaunay, the fool has only to blame themselves.
Just as I wanted to amend my recent posting, I saw that you have already replied. Whoops. Now it's too late. Thank you for your fast reply! :-)
The media keys are working again. Yay!
So, yes, somethings else needed to have been the issue, even though I did reboot yesterday, before writing my post.. hmmn.
Sorry to have accused anybody related to this package of anything, I was clearly in the wrong.
Also, what I can report is that
lsmod | grep uinput
does not return anything, it's missing from the listing.There is some pending issue here, yes, looks like it, but it's only a me-problem. I think, it can be summmerized that as the module is not loaded, surely nothing can be found. Thus, the error.
So all is well and solved.
Thank you very much for pitching in, cheers to you!
jlaunay commented on 2023-09-13 09:19 (UTC)
@ararhoo no problem here, Is the
uinput
driver module loaded?I think g910-gkeys doesn't control multimedia keys but only GKey
ararhoo commented on 2023-09-12 19:31 (UTC)
Hey there, sadly I have to tell you that it seems like this is not working as expected anymore.
I cannot use the media keys anymore, which is quite sad. G1-G5 are still working as expected, though. Weird.
It changed around the recent update of the package to v0.3.0.
I get an error for the service now:
Hopefully this log gives you already a hint to what is happening here.
If there is anything else I could do to provide helpful feedback in fixing the issue, please let me know.
Python 3.11.5-2 is installed and the listed dependencies are up to date.
The log file (
/var/log/g910-gkeys.log
) also doesn't say anything useful (to me at least):Thank you very much in advance :)
ISSOtm commented on 2022-06-15 21:22 (UTC)
The source must be changed from
git://
togit+https://
, as the clone otherwise fails. (I think GitHub removed support for that protocol.)