Package Details: logkeys-git 1:r74.5c36832-2

Git Clone URL: (read-only)
Package Base: logkeys-git
Description: Simple keylogger supporting also USB keyboards.
Upstream URL:
Keywords: keylogger
Licenses: GPLv3
Conflicts: logkeys
Provides: logkeys
Submitter: SanskritFritz
Maintainer: SanskritFritz
Last Packager: SanskritFritz
Votes: 46
Popularity: 0.000320
First Submitted: 2013-04-10 13:03
Last Updated: 2018-01-15 15:37

Dependencies (1)

Required by (0)

Sources (3)

Pinned Comments

SanskritFritz commented on 2018-03-09 14:08

Flagging a -git package out-of-date is only feasible if the build requirements change. Just rebuild the package otherwise.

Latest Comments

SanskritFritz commented on 2018-03-09 14:08

Flagging a -git package out-of-date is only feasible if the build requirements change. Just rebuild the package otherwise.

SanskritFritz commented on 2018-01-16 08:40

Since upstream introduced releases again, I have reintroduced the stable logkeys package. Happy keylogging!

SanskritFritz commented on 2018-01-14 21:23

@MrHritik, autoconf is part of the base-devel group which should be installed already. "Note: The group base-devel is assumed to be already installed when building with makepkg. Members of this group should not be included in makedepends array."

binTrl commented on 2018-01-14 20:27

autoconf should be added as a dependency.

SanskritFritz commented on 2016-02-23 20:53

Thanks. I will update the package right away. Use gistit next time :)

sanerb commented on 2016-02-23 16:44

looks like they restructured some of the build process. here's a patch.

EDIT: wow. munged to hell. here it is in base64.


SanskritFritz commented on 2016-01-22 20:25

Upstream moved to Github. There are no releases on Github, I'll file a bug report. Please use the logkeys-git package, it is perfectly usable and has the logkeys-stdout patch included.

SanskritFritz commented on 2015-12-14 15:00
This means, you have to rebuild the package.

brad87 commented on 2015-12-14 14:31

Getting this on service start:

Dec 14 09:27:48 gemini logkeys[17926]: /usr/bin/logkeys: Error opening input event device '': No such file or di
Dec 14 09:27:48 gemini systemd[1]: Started Keylogger daemon.
Dec 14 09:27:48 gemini systemd[1]: logkeys.service: Main process exited, code=exited, status=1/FAILURE
Dec 14 09:27:48 gemini systemd[1]: logkeys.service: Control process exited, code=exited status=1
Dec 14 09:27:48 gemini systemd[1]: logkeys.service: Unit entered failed state.
Dec 14 09:27:48 gemini systemd[1]: logkeys.service: Failed with result 'exit-code'.

SanskritFritz commented on 2015-01-05 08:39

Nice catch! Post your findings here later so that everyone can benefit.

TiborB commented on 2015-01-04 23:43

I have got it - I have to define a device:

cat /var/log/Xorg.0.log | grep keyboard | grep event
[ 26.621] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event14)
[ 26.621] (**) AT Translated Set 2 keyboard: always reports core events
[ 26.621] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event14"


But I wonder if the device changes after each boot, I will have to investigate...

TiborB commented on 2015-01-04 23:30

command dumpkeys works - better in Ctrl-Alt-Fn, but works in X as well.

SanskritFritz commented on 2015-01-04 23:19

Try dumping the keys:

TiborB commented on 2015-01-04 23:13

I have there:
LOGKEYS_PARAMS="--no-func-keys --keymap /usr/share/lkmaps/"

Under some circumstances I get following garbage in the log file:

2015-01-04 23:53:21+0100 > <E-110><E-110><E-110><E-110><E-110><E-110><E-110><E-110><E-110> ....and so on....

SanskritFritz commented on 2015-01-04 23:10

Make sure the keyboard definition matches the one you use. Use the /etc/conf.d/logkeysd file with this content (replace the hu to sk or whatever you use):

LOGKEYS_PARAMS="--no-func-keys --keymap /usr/share/lkmaps/"

TiborB commented on 2015-01-04 22:56

Hi, it does not work. Process is active (via systemctl), log file created but nothing is added in it... only "Logging started ..." and a time

SanskritFritz commented on 2014-10-21 11:54

patch is part of the base-devel group, see here:

smirky commented on 2014-10-21 10:22

Please add 'patch' as a dependency, since it needs it.

SanskritFritz commented on 2014-03-31 20:05

roentgen, you're right, I'll put it back.

roentgen commented on 2014-03-31 19:53

Why did you remove

rm -rf "${pkgdir}/usr/etc/"

in the PKGBUILD.

Please see my comment bellow.

paraxor commented on 2014-01-23 22:19

procps-ng should be in depends.

SanskritFritz commented on 2013-11-14 21:12

@intelfx: No, sorry. Last commit date is much more informative than commit count, for me at least.

intelfx commented on 2013-11-14 16:32

Sorry for broken link (I had a major issue with my server).
Could you re-iterate please? Link is the same.

intelfx commented on 2013-10-21 14:35

Could you please update pkgver to use commit count instead of last commit date? It's less clutter and also per guidelines...

In case, the updated package is here:

arokux commented on 2013-09-27 20:19

Alright, I appologize.

SanskritFritz commented on 2013-09-27 20:01

arokux commented on 2013-09-27 19:53

There are some build dependencies: binutils, patch and gcc.

sakalisc commented on 2013-09-10 14:36

Hey, now that you have removed the old rc files, may I suggest removing the logkeysd.conf file as well? Since there are usually distro specific there are preferably avoided when using systemd.

So instead of having a logkeysd.conf file, you add any command line options you want in the systemd file. In the package usually you add the minimal required and then the users can override the systemd service file (which is located in /usr/lib/systemd/) with their own (which should be located in /etc/systemd).

SanskritFritz commented on 2013-08-26 19:22

roentgen thanks for your observations, will fix these problems soon.

roentgen commented on 2013-08-26 18:39

File (usr/etc/) exists in a non-standard directory (those scripts are useless anyway).

/etc/conf.d/logkeysd has execute permissions.

sysfu commented on 2013-07-13 07:00

Build is failing with the message below. I can email or pastebin a copy of the config.log if needed.

checking whether we are cross compiling... configure: error: in `/tmp/packerbuild-1001/logkeys/logkeys/src/logkeys-0.1.1a':
configure: error: cannot run C++ compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
==> ERROR: A failure occurred in build().
The build failed.

SanskritFritz commented on 2013-05-28 14:38

Removed rc.d script as per

SanskritFritz commented on 2013-05-28 14:34

Removed rc.d script as per

SanskritFritz commented on 2013-04-15 09:23

Upstream has switched to git, please use this logkeys-git package from now on.

SanskritFritz commented on 2013-04-10 13:04

Upstream switched to git, please use the logkeys-git package from now on. This package will be deleted soon.

SanskritFritz commented on 2013-04-08 20:27

I'm renaming logkeys-keymap-svn to logkeys-keymaps-svn.

SanskritFritz commented on 2013-04-08 20:26

I'm renaming logkeys-keymap to logkeys-keymaps.

sakalisc commented on 2012-09-05 20:17

Thanks and no problem. I am monitoring the comments, so if there are any problems with the unit file, I will look into it.

SanskritFritz commented on 2012-09-05 20:05

SakalisC thanks for your kind help. I added the service file you sent.
1. I like the names that way, after all logkeys *is* launched as a daemon.
2. Agree and fixed.
3. Agreed. This way it is more KISS.
4. True and fixed.

sakalisc commented on 2012-09-04 15:34

Good job. Here is a unit file for systemd:
Just add it as /usr/lib/systemd/system/logkeys.service

If you don't mind, I have a couple of suggestions.
1. I think the /etc/rc.d and /etc/rc.conf files should be "logkeys" and not
"logkeysd". Usually, only daemons with "daemon" in their name use the "d" in the
2. The default parameters in the configuration file will not work if the user
does not have the extra keymaps and just wants to use the default one.
3. Alongside the one above, do not ask the user for a keymap. They can configure
it later if they want.
4. I think that the convention is to use all caps variables in the /etc/rc.conf

Number #2 and #3 are the most important, because it breaks the unit and
service files on some users. The other two are mostly for keeping up with the
current conventions.

Also, on a side note, I do not use the --no-func-keys option, but I can easily
change that on my own. I am not sure if the users prefer it though.

SanskritFritz commented on 2012-09-04 14:51

I'd be grateful if someone came up with a systemd unit file. I don't use systemd yet.

SanskritFritz commented on 2012-09-04 14:50

conf.d/logkeysd implemented.

SanskritFritz commented on 2012-09-04 14:50

I'd be grateful if someone came up with a systemd unit file. I don't use systemd yet.

SanskritFritz commented on 2012-09-04 14:50

conf.d/logkeysd implemented.

SanskritFritz commented on 2012-08-21 13:12

SakalisC brilliant idea, thanks, I'll look into this. Expect a new version soon.

sakalisc commented on 2012-08-15 11:31

Hello. May I suggest that instead of modifying the rc script, add the
commandline options in a variable in a file in /etc/conf.d/ and the source it in
the rc script? This is the way most packages work and it's easier to modify the
commandline arguments after the installation. Also this way you won't have to
ask the user for what arguments should be passed during post-install.

Take a look at existing deamons in your system (their rc scripts in /etc/rc.d/
and their conf files in /etc/conf.d) if you are not sure how exactly this is
supposed to work.

SanskritFritz commented on 2012-04-05 18:48

@eduardosm: post your /etc/rc.d/logkeys to some pastebin. I suspect you messed up something at install. It is interactive, you have to enter the command executed by the script.

SanskritFritz commented on 2012-04-05 18:46

@eduardosm: I use this very daemon script every day automatically at startup. Never had any problem with it. I just tested it now with
rc.d stop logkeys
rc.d start logkeys
There could be something wrong on your system, check some logs.

eduardosm commented on 2012-04-05 17:21

The daemon script does not work.
Whether it is running or not it always fails to start and always says has success to stop.

SanskritFritz commented on 2012-03-25 07:28

Done, thank you for the warning.

Seninha commented on 2012-03-25 01:08

please, remove de "dependencies" line from the PKGBUILD

Seninha commented on 2012-03-25 01:08

please, remove de "dependencies" line from the PKGBUILD
an empty "dependencies" area makes an error in pacman 4

Seninha commented on 2012-03-25 01:07

please, remove de "dependences" line from the PKGBUILD
an empty "dependences" area makes an error in pacman 4

SanskritFritz commented on 2012-01-06 14:11

Updated, now it finally works in archlinux.

SanskritFritz commented on 2012-01-04 22:56


SanskritFritz commented on 2011-11-01 07:11

eworm, that's because it only checks out trunk, and that is at r77. I'll change the package soon (just adopted it) so that it will include the keymaps as well.

eworm commented on 2011-10-27 09:23

This only gets revision 77 while the repo already has revision 88. Any ideas what goes wrong?

domanov commented on 2011-01-19 19:01

I will orphan the package, anyone wants to step up? no big activity upstream, it seems.

Anonymous comment on 2010-12-06 21:07

I am a robot. This is not an official message. You have accidentally tarred up some dotfiles. Examples:
Suggestion: use "makepkg --source". Feel free to disregard this as you would any other comment. This robot will not post here again.

domanov commented on 2010-06-07 15:32

As suggested by wido, no keymap is provided with this package; logkeys-keymap given as as optdepends.

widowild commented on 2010-06-06 14:47

delete and use a package logkeys-keymap for keymap