Package Details: selfspy-git 1:0.1.4.r202.ga98a9c0-2

Git Clone URL: https://aur.archlinux.org/selfspy-git.git (read-only)
Package Base: selfspy-git
Description: X11 personal keylogger daemon with statistical analysis.
Upstream URL: https://github.com/gurgeh/selfspy
Keywords: keylogger keylogging productivity quantified-self
Licenses: GPL
Conflicts: selfspy
Provides: selfspy=0.1.4.r202.ga98a9c0
Submitter: fackamato
Maintainer: grandchild
Last Packager: grandchild
Votes: 10
Popularity: 0.101764
First Submitted: 2012-04-15 18:22
Last Updated: 2018-11-11 21:44

Pinned Comments

grandchild commented on 2018-11-11 21:48

I patched this to use pycryptodome explicitly. Thanks @deraffe, for the report and patch draft.

I did have to patch API calls to pycryptodome in selfspy, which only serves as a reminder that this code is unmaintained, and the package may stop working again soon.

I will continue to patch things up for now, but ultimately things will have to happen upstream.

Latest Comments

1 2 Next › Last »

amazingrise commented on 2019-05-28 03:00

This package is not available currently, due to the removal of python2-keyring. python2-keyring was removed from both Arch repository and AUR. But we can still install this through several tricks:

  1. First, please use a AUR tool which supports editing pkgbuild file, for example the deprecated yaourt. When installing, please select "edit pkgbuild", then remove the "python2-keyring" dependency. Save & Exit. (Note: you may also doing this by running "makepkg" manually, for avoiding the usage of the deprecated "yaourt".)
  2. After the modification, the package can be installed. But we still need to install a python2-keyring package. So do "sudo pacman -S python2-pip" to install the pip for python2.
  3. With pip2 installed, we can install the package through PyPi. Use "sudo pip2 install keyring", and wait patiently.
  4. Finally, you can see the selfspy running normally. Cheers!

As you can see, this is not a "elegant" way to make it work.(for nowadays yaourt and python2 are neither recommended by archlinux community now.) So if you have other ways to achieve this, plz share it here! :)

sender commented on 2019-05-27 08:55

Since python2-keyring is not available anymore in the AUR, any suggesions on how to get this installed the right way?

grandchild commented on 2018-11-11 21:48

I patched this to use pycryptodome explicitly. Thanks @deraffe, for the report and patch draft.

I did have to patch API calls to pycryptodome in selfspy, which only serves as a reminder that this code is unmaintained, and the package may stop working again soon.

I will continue to patch things up for now, but ultimately things will have to happen upstream.

mocambo commented on 2018-11-02 17:45

Can confirm, problem with python2-crypto is still there.

nov 02 19:39:23 Twin selfspy[9056]: working_set = WorkingSet._build_master()

nov 02 19:39:23 Twin selfspy[9056]: File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 578, in _build_master

nov 02 19:39:23 Twin selfspy[9056]: ws.require(requires)

nov 02 19:39:23 Twin selfspy[9056]: File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 895, in require

nov 02 19:39:23 Twin selfspy[9056]: needed = self.resolve(parse_requirements(requirements))

nov 02 19:39:23 Twin selfspy[9056]: File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 781, in resolve

nov 02 19:39:23 Twin selfspy[9056]: raise DistributionNotFound(req, requirers)

nov 02 19:39:23 Twin selfspy[9056]: pkg_resources.DistributionNotFound: The 'pycrypto>=2.5' distribution was not found and is required by selfspy

nov 02 19:39:23 Twin systemd[1]: selfspy@gnome.service: Main process exited, code=exited, status=1/FAILURE

nov 02 19:39:23 Twin systemd[1]: selfspy@gnome.service: Failed with result 'exit-code'.

grandchild commented on 2018-10-05 12:13

@deraffe, sorry for the late reply, and thanks for the patch! But I cannot really verify your issue. python2-cryptodome does indeed provide python2-crypto and the package builds for me. Are you having build issues? What do you mean by "pkg_resources mechanism"?

deraffe commented on 2018-09-04 14:07

The dependency python2-crypto is gone, and although python2-pycryptodome provides it, the pkg_resources mechanism complains, because it can't find the pycrypto package.

I solved this using this patch[1], which just renames the dependency in requirements.txt to pycryptodome.

  1. https://pwnage.pw/?5e1da5e92808ff51#VnPFlnjXhem48cHIvElLtP+H+L/k7PeR1RX4RxaGgaI=

maxik commented on 2018-06-07 08:56

The dependency 'python2-keyring' is gone. There is only a 'python-keyring' which is Python 3 and does not work with the package (internal python dependency not found). Any chance of getting it working again?

The source repository seems idle though.

divansantana commented on 2016-12-13 09:00

Sorted I had to modify DISPLAY var in the service file.

divansantana commented on 2016-12-13 08:57

Anyone else getting this?

selfspy Xlib.error.DisplayConnectionError: Can't connect to display ":0"

grandchild commented on 2016-07-23 21:58

Sorry that it's taken me so long to get to this!

@jamesan: Thank you very much, I've just forwarded to your commits -- perfect! :)

@Pastafarianist: I can confirm that something goes awry on Manjaro (or is it KDE's fault?) -- I'm investigating...