Package Details: prey-node-client 1.9.1-1

Git Clone URL: (read-only, click to copy)
Package Base: prey-node-client
Description: Remote tracking and monitoring application for laptops, smartphones, and other electronic devices
Upstream URL:
Licenses: GPL3
Replaces: prey-tracker
Submitter: lutoma
Maintainer: xpt
Last Packager: xpt
Votes: 30
Popularity: 0.026551
First Submitted: 2014-12-02 03:20
Last Updated: 2020-01-03 03:24

Latest Comments

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

jhartz commented on 2016-12-15 01:59

After upgrading nodejs to 7.0, I had to change /opt/prey-node-client/bin/prey so that it explicitly uses /opt/prey-node-client/bin/node (the version of node that ships with prey) instead of the system nodejs. (It was already doing this when run from /opt/prey-node-client/bin/prey directly, but not when using the /usr/bin/prey_project symlink.)

Angel_Caido commented on 2016-11-08 04:16

FYI: The package nodejs reached version 7.0. After I upgraded it, prey-node-client started crashing on my system. I downgraded to version 6.9 and prey is spreading its wings again. Be careful when updating/upgrading.

xpt commented on 2016-10-26 17:38

Hi everyone!

So, I edited PKGBUILD;

1. I commented the line "rm bin/node"
2. Added npm as dependency

cjmzy commented on 2016-10-24 13:28

Thank you, Angel, that worked well!

Angel_Caido commented on 2016-10-23 16:20

First of all, Good job in building this PKGBUILD and thank you for sharing it. I just have a few observations after installing it and doing some testing on my system:
1. I edited the PKGBUILD following yut23's observation. I commented the "rm bin/node" from the PKGBUILD.
2. You may want to consider adding 'npm' as an obligatory dependency. The Account Setup process will not run properly without this package installed.
3. I had to create the file '/usr/local/bin/python' and give it executable permissions using 'chmod +x /usr/local/bin/python'.
4. The setup process that worked for me included [using the terminal and after installing 'npm']:
a) cd /opt/prey-node-client/bin/
b) sudo ./prey config account setup

After that the setup process went as normal, asking if I had an account and [if so] the username and password for such account. Process ended up properly and added my device to my Prey-project account.

I hope this helps somebody else.

yut23 commented on 2016-09-11 18:30

I just noticed that Prey was crashing with "Error: Cannot find module '/opt/prey-node-client/node_modules/sqlite3/lib/binding/node-v48-linux-x64/node_sqlite3.node'". It looks like the client ships with the sqlite3 bindings for node.js ABI v46, while community/nodejs installs the latest version (currently v6.5.0, ABI v48).

I was able to get the client working by using the bundled node.js (I removed "rm bin/node" from the PKGBUILD).

nuksan commented on 2016-09-08 23:55

@OdinEidolon I'm having the same problem with the "re-evaluating native module sources is not supported..." message, and for me it appears with every command I try to run. I can't even run "prey_project config log".

@ThecaTTony Does networkmanager really need to be a dependency? Automatically connecting to WiFi happens on my system with netctl, and the ArchWiki lists other daemons users could use as well.

OdinEidolon commented on 2016-07-28 07:54

Not working anymore after first reboot :(

Anyone has any idea?
# prey_project config log

error Thu, 28 Jul 2016 07:53:12 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND
error Thu, 28 Jul 2016 07:53:27 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND
error Thu, 28 Jul 2016 07:53:42 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND

OdinEidolon commented on 2016-07-26 09:13

Is the GUI working for anyone?
I get:
sudo -u prey prey_project config gui
(node:27806) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Valid existing keys found. Proceeding anyway.
Firing up config GUI!

But nothing happens.

noplomplom commented on 2016-06-24 05:41

When checking installation (1.6.1), get the error "Unable to verify keys:" and no key following. I'm sure the config is alright, it was working well with 1.5.1.

Here's the package build output:

patching file bin/prey
patching file lib/agent/actions/alert/linux/
patching file lib/conf/gui/linux/
patching file prey.conf.default
patching file lib/system/linux/index.js
patching file lib/conf/gui/linux/
patching file lib/conf/shared/messages.js
patching file lib/conf/shared/keys.js
patching file lib/agent/plugins/console/index.js
patching file package.json
Hunk #1 succeeded at 83 (offset 2 lines).
patch unexpectedly ends in middle of line
Hunk #2 succeeded at 92 with fuzz 1 (offset 2 lines).

I'm still getting the same error message when checking config after a reboot, but my computer appears correctly in the web app. However, it cannot be located.