Package Details: prey-node-client 1.13.8-1

Git Clone URL: https://aur.archlinux.org/prey-node-client.git (read-only, click to copy)
Package Base: prey-node-client
Description: Node.js client for the Prey anti-theft software
Upstream URL: https://github.com/prey/prey-node-client
Licenses: GPL-3.0-or-later
Submitter: lutoma
Maintainer: None
Last Packager: phnx47
Votes: 35
Popularity: 0.000000
First Submitted: 2014-12-02 03:20 (UTC)
Last Updated: 2025-01-16 14:05 (UTC)

Latest Comments

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

nuksan commented on 2016-09-08 23:55 (UTC) (edited on 2016-09-09 00:02 (UTC) by nuksan)

@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 (UTC)

Not working anymore after first reboot :( Anyone has any idea? # prey_project config log returns: error Thu, 28 Jul 2016 07:53:12 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443 error Thu, 28 Jul 2016 07:53:27 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443 error Thu, 28 Jul 2016 07:53:42 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443

OdinEidolon commented on 2016-07-26 09:13 (UTC)

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 (UTC) (edited on 2016-06-24 05:52 (UTC) by noplomplom)

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/flash.py patching file lib/conf/gui/linux/prey-config.py patching file prey.conf.default patching file lib/system/linux/index.js patching file lib/conf/gui/linux/prey-config.py 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). EDIT: 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.

noplomplom commented on 2016-06-24 05:35 (UTC)

Same error remaining in PKGBUILD, line 23: it should be cd "$srcdir/prey-$pkgver" instead of cd "$srcdir/prey-$pkgver.$pkgrel"

disprofarma commented on 2016-06-23 18:47 (UTC)

Hi, license should be GPL3, and not GPLv3. Thanks!"

noplomplom commented on 2016-06-13 17:33 (UTC)

It seems there's an error in the PKGBUILD: line 23 should be cd "$srcdir/prey-$pkgver" without the ".$pkgrel" part

mzecher commented on 2016-05-14 02:15 (UTC)

prey-agent.service is not included, or am I doing something wrong?

JDCNS commented on 2016-03-20 04:49 (UTC)

OK, it's working now.

JDCNS commented on 2016-03-20 02:18 (UTC)

Well, now I get a 404 trying to download it from this, so I cannot test your node.js suggestion.

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