Open icaroerasmo opened 1 year ago
What version are you using? Please try with one of the more recent releases or even git master.
Otherwise, amend your service file with flags logkeys -d event15
through event17
, if one of those works.
I have installed it through aurman in arch linux and I could verify it's the most recent version: 0.2.0. When you say I should amend, you mean I have to put those flags in my logkeys.conf?
I have tried all of those and this is the message I receive:
jan 01 00:56:23 Ryzen systemd[1]: Starting Keylogger daemon...
jan 01 00:56:23 Ryzen logkeys[709]: /usr/bin/logkeys: Error opening input event device '/dev/input/event17': No such file or directory
jan 01 00:56:23 Ryzen systemd[1]: logkeys.service: Control process exited, code=exited, status=1/FAILURE
jan 01 00:56:23 Ryzen systemd[1]: logkeys.service: Failed with result 'exit-code'.
jan 01 00:56:23 Ryzen systemd[1]: Failed to start Keylogger daemon.
when I run ls -la /dev/input/event15
; ls -la /dev/input/event16
or ls -la /dev/input/event17
all of these are created.
I think that the service is being run before it should. Maybe before all of these devices are created.
Setting type as "idle" made logkeys work as it delays its execution until the last service starts, but it finished right after startup. Do you have any guess on what service should logkeys wait to execute?
EDIT: Remember that logkeys works perfectly if I run it after startup through "llk"
Do you have any guess on what service should logkeys wait to execute?
Just a guess, since most of /dev is handled by udev, maybe systemd-udevd.service?
I was able to make it run as a daemon following this guide: https://www.vivaolinux.com.br/dica/rclocal-no-Arch-Linux
It's in portuguese. Try to translate it using google or something else. In summary what it does is activate local.rc script and you can put logkeys startup comand there.
When my PC boots there's a message saying that logkeys failed running. Looking to syslog I see these messages:
Here is /proc/bus/input/devices content: