Hold on! problem in Ubuntu

[sergiobenrocha2]

Hello,

I'm trying to register my machine using Ubuntu 14.04 64 bits (it is already registered in the Windows 8 side, it's dual boot), package deb 1.2.4, and i'm getting this problem when I enter with my account and password:

Hold on!
at /usr/lib/prey/versions/1.2.4/node_modules/getset/lib/backends/file.js:66:20

[tomas]

Holy shmoly! Thanks for the heads up. Did you upgrade from a previous version, or is this a clean install?

You can also do the linking process from the command line, by running:

sudo /usr/lib/prey/current/bin/prey config account setup

[tomas]

My guess is that the linking logic is not working, specifically the part where the agent gathers system data. What happens if you run this?

sudo /usr/lib/prey/current/bin/prey -r "get_specs" -D

[sergiobenrocha2]

sudo /usr/lib/prey/current/bin/prey -r "get_specs" -D[sudo] password for gleise:
critical Fri, 26 Sep 2014 14:15:25 GMT UNCAUGHT EXCEPTION: Cannot read property '1' of undefined
debug Fri, 26 Sep 2014 14:15:25 GMT TypeError: Cannot read property '1' of undefined
at run_from_command_line (/usr/lib/prey/versions/1.2.4/lib/agent/index.js:170:47)
at Object.run (/usr/lib/prey/versions/1.2.4/lib/agent/index.js:70:12)
at Object. (/usr/lib/prey/versions/1.2.4/lib/agent/cli.js:139:16)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3
info Fri, 26 Sep 2014 14:15:30 GMT Gracefully shutting down. Will self-destruct in 5 secs.
debug Fri, 26 Sep 2014 14:15:30 GMT Unloading plugins.
debug Fri, 26 Sep 2014 14:15:30 GMT Stopping actions.
debug Fri, 26 Sep 2014 14:15:30 GMT Unloading hooks.
info Fri, 26 Sep 2014 14:15:30 GMT [hooks] Unregistering hooks.
debug Fri, 26 Sep 2014 14:15:30 GMT Canceling reports.
debug Fri, 26 Sep 2014 14:15:30 GMT Unwatching triggers.
debug Fri, 26 Sep 2014 14:15:30 GMT Cleaning up temporary files.
info Fri, 26 Sep 2014 14:15:35 GMT Time's up, shutdown forced. Have a jolly good day sir.

[sergiobenrocha2]

It's a clean install.

[sergiobenrocha2]

sudo /usr/lib/prey/current/bin/prey config account setup
Error! Account already set up! Run with -f/--force to continue anyway.

I didn't understand... the account was already configured? Well, for me it's fine now, i think, i used -f parameter after.

Thanks!

[sergiobenrocha2]

Humm, i don't sure if it worked

sudo /usr/lib/prey/current/bin/prey config account setup -f

Do you already have a Prey account?

• yes/no: [yes] yes
  Well hello old friend!
  Please type your account's email address.
• email: xxxxx
  Well played. Now enter your password.
• pass: ********
  Credentials verified.
  Linking device...
  EXCEPTION! Object 353162524428 has no method 'trim'
  TypeError: Object 353162524428 has no method 'trim'
  at setup_keys (/usr/lib/prey/versions/1.2.4/lib/agent/plugins/control-panel/setup.js:87:28)
  at Object.exports.start (/usr/lib/prey/versions/1.2.4/lib/agent/plugins/control-panel/setup.js:125:3)
  at Object.exports.enabled (/usr/lib/prey/versions/1.2.4/lib/agent/plugins/control-panel/index.js:170:9)
  at invoke (/usr/lib/prey/versions/1.2.4/node_modules/wink/index.js:77:22)
  at Object.invoke (/usr/lib/prey/versions/1.2.4/node_modules/wink/index.js:98:14)
  at Object.exports.enabled (/usr/lib/prey/versions/1.2.4/lib/agent/plugin.js:135:16)
  at Object.exports.link (/usr/lib/prey/versions/1.2.4/lib/conf/shared/panel.js:41:13)
  at /usr/lib/prey/versions/1.2.4/lib/conf/account.js:128:20
  at /usr/lib/prey/versions/1.2.4/node_modules/getset/lib/index.js:186:11
  at /usr/lib/prey/versions/1.2.4/node_modules/getset/lib/backends/file.js:66:20

If i have prey installed both in windows and ubuntu, how my device will appear in the website? As only one or 2 devices?

[tomas]

Hi Sergio,

Bug found! (Thanks to your last comment). I'm unable to get it fixed today, but on Monday I'll push a new version that addresses this so you can install Prey without a problem. I'll let you know once the update is available.

Thanks by the way!

[sergiobenrocha2]

But if a burglar take my laptop until monday ? :'(

Hehe, ok, thanks!

[tomas]

Hi Sergio,

Just pushed a new release that should fix this issue. You can download the package from:

https://s3.amazonaws.com/prey-releases/node-client/1.2.6/prey_1.2.6_amd64.deb
https://s3.amazonaws.com/prey-releases/node-client/1.2.6/prey_1.2.6_i386.deb

Please try it out and let me know how it goes!

[sergiobenrocha2]

It seems it works now, but i got these things:

sudo /usr/lib/prey/current/bin/prey config account setup -f
[sudo] password for xxxx:
Do you already have a Prey account?

• yes/no: [yes] yes
  Well hello old friend!
  Please type your account's email address.
• email: xxxxxx
  Well played. Now enter your password.
• pass: **********
  Credentials verified.
  Linking device...
  EXCEPTION! Cannot read property '1' of null
  TypeError: Cannot read property '1' of null
  at /usr/lib/prey/versions/1.2.6/lib/agent/providers/hardware/linux.js:79:54
  at Array.forEach (native)
  at /usr/lib/prey/versions/1.2.6/lib/agent/providers/hardware/linux.js:71:46
  at done (/usr/lib/prey/versions/1.2.6/node_modules/sudoer/lib/index.js:40:5)
  at process._tickCallback (node.js:419:13)

And in the GUI, i got a message too...

[tomas]

Hmm, interesting. You're getting different values on dmidecode -t 17. Can you run that command and send over the output? Feel free to redact any serial numbers or ID's if you want.

[tomas]

Sergio,

I think I nailed it this time:

https://s3.amazonaws.com/prey-releases/node-client/1.2.7/prey_1.2.7_amd64.deb
https://s3.amazonaws.com/prey-releases/node-client/1.2.7/prey_1.2.7_i386.deb

Basically you're getting a different output from dmidecode that the one I get on the systems I've tested. This version handles correctly that scenario.

[tomas]

Closing this one for the time being. Feel free to reopen if any problems persist.