Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't use prey on Manjaro Linux #45

Closed
irodriguez-moreno opened this issue Oct 4, 2014 · 44 comments
Closed

Can't use prey on Manjaro Linux #45

irodriguez-moreno opened this issue Oct 4, 2014 · 44 comments

Comments

@irodriguez-moreno
Copy link

Hi, and sorry the bad english
Downloaded the prey node client 1.2.7 version via NPM. First GUI doesn't open, so i chose CLI option. When i configure my account:

Do you already have a Prey account? 
 - yes/no: [yes] 
Well hello old friend!
Please type your account's email address. 
 - email: [email protected]
Well played. Now enter your password. 
 - pass: **********
Credentials verified.
Linking device...
Error! Invalid os:  does not exist.

Then i start prey:

PREY 1.2.7 spreads its wings!
Current time: Sat Oct 04 2014 13:31:06 GMT-0300 (CLST)
Running under Node v0.10.32 with PID 8865 on a x64 linux system as username

info Sat, 04 Oct 2014 16:31:06 GMT [triggers] Watching: connection, network, power
info Sat, 04 Oct 2014 16:31:06 GMT [actions] Starting trigger: connection
info Sat, 04 Oct 2014 16:31:06 GMT [actions] Running: connection
info Sat, 04 Oct 2014 16:31:06 GMT [actions] Starting trigger: network
info Sat, 04 Oct 2014 16:31:06 GMT [actions] Starting trigger: power
info Sat, 04 Oct 2014 16:31:06 GMT [actions] Running: network
info Sat, 04 Oct 2014 16:31:06 GMT [actions] Running: power
info Sat, 04 Oct 2014 16:31:07 GMT [control-panel] Gathering device data...
info Sat, 04 Oct 2014 16:31:07 GMT [reports] Gathering specs report.
error Sat, 04 Oct 2014 16:31:07 GMT [reports] Unable to get storage_devices_list: TODO!
info Sat, 04 Oct 2014 16:31:07 GMT [reports] Report gathered: specs
error Sat, 04 Oct 2014 16:31:08 GMT [control-panel] Unable to register device: Invalid os:  does not exist.
error Sat, 04 Oct 2014 16:31:08 GMT Error: Invalid os:  does not exist.
info Sat, 04 Oct 2014 16:31:09 GMT 1 plugins loaded with 1 errors.
critical Sat, 04 Oct 2014 16:31:09 GMT UNCAUGHT EXCEPTION: Invalid os:  does not exist.
info Sat, 04 Oct 2014 16:31:14 GMT Gracefully shutting down. Will self-destruct in 5 secs.
info Sat, 04 Oct 2014 16:31:14 GMT [actions] Stopping: connection
info Sat, 04 Oct 2014 16:31:14 GMT [actions] Stopping: network
info Sat, 04 Oct 2014 16:31:14 GMT [actions] Stopping: power
info Sat, 04 Oct 2014 16:31:14 GMT [hooks] Unregistering hooks.
info Sat, 04 Oct 2014 16:31:19 GMT Time's up, shutdown forced. Have a jolly good day sir.

I think prey doesn't recognize manjarolinux distro. Please make it so!! 🙏

@tomas
Copy link
Contributor

tomas commented Oct 5, 2014

Thanks for spotting this one! Actually today I was wondering about this bug, and then I found out it was because of an unknown distro name trying to get registered. Why is the GUI not showing up? What desktop environment are you using?

@irodriguez-moreno
Copy link
Author

Dont know why GUi doesnt open. Just nothing happens, and no console output either. I am using KDE.

@tomas
Copy link
Contributor

tomas commented Oct 8, 2014

Can you run the following command and see what happens?

python /usr/local/lib/node_modules/prey/lib/conf/gui/linux/prey-config.py

(Assuming that the global npm install path is /usr/local/lib/node_modules. You may also find it under /usr/lib/node_modules).

@irodriguez-moreno
Copy link
Author

Traceback (most recent call last):
File "/usr/lib/node_modules/prey/lib/conf/gui/linux/prey-config.py", line 19, in
import pygtk
ImportError: No module named 'pygtk'

I have 'pygtk' package installed.

EDIT: I tried running the command with python2, and GUI showed up, however, the same error pops up (invalid os name). This has to do with archlinux default python is python3

@tomas
Copy link
Contributor

tomas commented Oct 8, 2014

Have you tried installing the python3-gtk package? Or is it already installed?

@irodriguez-moreno
Copy link
Author

does not exist.

@irodriguez-moreno
Copy link
Author

still prey doesn't recognize manjarolinux :( 👎

@tomas
Copy link
Contributor

tomas commented Dec 10, 2014

Ok mister. I'm fixing this bug right now (sorry about the delay).

What output do you get when running lsb_release -a?

@irodriguez-moreno
Copy link
Author

thank you!! :)

lsb_release -a

LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 0.8.11
Codename: Ascella

@JotaRandom
Copy link

for the record there is the ArchLinux one
LSB Version: 1.4
Distributor ID: Arch
Description: Arch Linux
Release: rolling
Codename: n/a
As you can see the Codename is missing and the LSB version is present, in contrast to the Manjaro one, so I thing there is only Dristributor ID and Release the only things that look consistent (cause the description are... far to descriptive).
I raise this because the Release name is not recogniced (rolling) in the old interface.

@tomas
Copy link
Contributor

tomas commented Dec 12, 2014

Perfect. Already commited the fix to our servers. It should be up in production in a snap!

@irodriguez-moreno
Copy link
Author

Thank you very much!
Don't know if it is ready yet, but i will try again tomorrow :)

@cyrinux
Copy link

cyrinux commented Dec 15, 2014

Hi,
Could you please support Fedora 21 ?
➜ lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: Generic
Description: Generic release 21 (Generic)
Release: 21
Codename: Generic

Regards,

@tomas
Copy link
Contributor

tomas commented Dec 15, 2014

What output does cat /etc/issue render? What about /etc/redhat_release?

@irodriguez-moreno
Copy link
Author

Tried today, still get the message

"Error! Invalid os: does not exist."

@tomas
Copy link
Contributor

tomas commented Dec 29, 2014

That's weird. Our list of supported OS distros includes Manjaro:

Ubuntu Debian Redhat Fedora Centos Suse Arch Gentoo Mint Elementary Manjaro

What does lsb_release -a show?

@boris
Copy link

boris commented Dec 30, 2014

This is what 0.8.11 shows:

Manjaro

@irodriguez-moreno
Copy link
Author

Today an email was sent to me, about my notebook being registered on Prey.

:) I supose this bug is fixed, thank you very much!!!!

@nieldk
Copy link

nieldk commented Feb 24, 2015

Please add the Jolla phone, It works quite well if I fake Debian release. But spits out wrong OS by default:
{~]$ lsb_release -ri
Distributor ID: Mer
Release: 0.2011

@shackra
Copy link

shackra commented Mar 19, 2015

Man, this bug is ridiculous, you know how many GNU/Linux distros there exists, right?

In any case:

LSB Version:    n/a
Distributor ID: Parabola
Description:    Parabola GNU/Linux-libre
Release:    rolling
Codename:   n/a

I really want to have my laptop protected ASAP...

@mauricioschneider
Copy link
Contributor

@shackra This is actually not a bug, but a feature. We offer official support for the most widely used distros, and add other distros on a on-demand basis. You can expect Parabola GNU/Linux to be added by tomorrow.

@shackra
Copy link

shackra commented Mar 19, 2015

Well, thank you.

Instead of Error! Invalid os: does not exist. something more verbose should
be put in place thought

El 19 de marzo de 2015 a las 03:29 PM Mauricio Schneider
[email protected] escribió:

@shackra This is actually not a bug, but a feature. We offer official support
for the most widely used distros, and add other distros on a on-demand basis.
You can expect Parabola GNU/Linux to be added by tomorrow.


Reply to this email directly or view it on GitHub:
#45 (comment)

Pax et bonum.
Jorge Araya Navarro.
ES: Diseñador Publicitario, Programador Python y colaborador en Parabola
GNU/Linux-libre
EN: Ads Designer, Python programmer and contributor Parabola GNU/Linux-libre
EO: Anonco grafikisto, Pitino programalingvo programisto kai kontribuanto en
Parabola GNU/Linux-libre
https://es.gravatar.com/shackra

@mauricioschneider
Copy link
Contributor

Thanks, I agree with your suggestion. I'll make sure to replace the message.
On Mar 19, 2015 6:52 PM, "Jorge Araya Navarro" [email protected]
wrote:

Well, thank you.

Instead of Error! Invalid os: does not exist. something more verbose
should
be put in place thought

El 19 de marzo de 2015 a las 03:29 PM Mauricio Schneider
[email protected] escribió:

@shackra This is actually not a bug, but a feature. We offer official
support
for the most widely used distros, and add other distros on a on-demand
basis.
You can expect Parabola GNU/Linux to be added by tomorrow.


Reply to this email directly or view it on GitHub:
#45 (comment)

Pax et bonum.
Jorge Araya Navarro.
ES: Diseñador Publicitario, Programador Python y colaborador en Parabola
GNU/Linux-libre
EN: Ads Designer, Python programmer and contributor Parabola
GNU/Linux-libre
EO: Anonco grafikisto, Pitino programalingvo programisto kai kontribuanto
en
Parabola GNU/Linux-libre
https://es.gravatar.com/shackra


Reply to this email directly or view it on GitHub
#45 (comment)
.

@shackra
Copy link

shackra commented Mar 21, 2015

@lemavri Parabola GNU/Linux isn't added, I still getting the error.

@mauricioschneider
Copy link
Contributor

@shackra I'm sorry for the delay. I'll fix it today. Thanks for adding a new issue for that, easier to track it that way.

EDIT: Parabola GNU/Linux support has been added!

@thanasisn
Copy link

LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:core-4.1-ia32:core-4.1-noarch:security-4.0-ia32:security-4.0-noarch:security-4.1-ia32:security-4.1-noarch
Distributor ID: Kali
Description: Kali GNU/Linux 1.1.0
Release: 1.1.0
Codename: moto

Please add support for Kali

@rebeccaadams1232
Copy link

Hi, can you please add Redhat workstation?

LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: RedHatEnterpriseWorkstation
Description: Red Hat Enterprise Linux Workstation release 6.6 (Santiago)
Release: 6.6
Codename: Santiago

@mauricioschneider
Copy link
Contributor

@natsis sorry for the delay. I just read your comment yesterday. We have added support for Kali, please feel free to try it out and let us know how it goes.

@mef
Copy link

mef commented Dec 12, 2015

Hi there, I know this issue is closed but I have the same problem on my linux distro (bunsenLabs, debian based)

The Error! Invalid os: does not exist. error message shows up both on node.js cli and gui config.

$ lsb_release -a
No LSB modules are available.
Distributor ID: BunsenLabs
Description:    BunsenLabs GNU/Linux 8.1 (Hydrogen)
Release:    8.1
Codename:   Hydrogen
$ cat /etc/issue
Debian GNU/Linux 8 \n \l

prey version: 1.4.2

It would perhaps be more sustainable to have a dynamic way of identifying linux distributions, instead of a hard-coded list...

@Chejone
Copy link

Chejone commented May 28, 2016

Hello, can you please add Jolla Tablet? :)

Mer release 0.2011 (Mer)
BUILD: Jolla-2.0.0.10-tbj-i486

[nemo@Jolla ~]$ lsb_release -a
LSB Version: :core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:desktop-3.1-ia32:desktop-3.1-noarch:desktop-3.2-ia32:desktop-3.2-noarch:desktop-4.0-ia32:desktop-4.0-noarch
Distributor ID: #Thisfileiscopiedashw-release(analogoustoos-release)
Description: # This file is copied as hw-release (analogous to os-release)
Release: n/a
Codename: analogoustoos-release

[nemo@Jolla ~]$ lsb_release -ri
Distributor ID: #Thisfileiscopiedashw-release(analogoustoos-release)
Release: n/a

@WolfangAukang
Copy link

WolfangAukang commented Aug 5, 2016

Hey guys, I can't install it on Korora. This is my lsb_release:

Distributor ID: Korora Description: Korora release 22 (Selina) Release: 22 Codename: Selina

@PaveEvil
Copy link

PaveEvil commented Jan 3, 2017

Hi, can you please add Parrot

No LSB modules are available.
Distributor ID: Parrot
Description: Parrot Security 3.4 - CyberFrigate
Release: 3.4
Codename: cyberfrigate

@javo
Copy link
Contributor

javo commented Jan 4, 2017

Hey @PaveEvil, we've just added Parrot parrot try again please and let me know if it's working fine

@PaveEvil
Copy link

PaveEvil commented Jan 4, 2017

@javo All good
screenshot at 2017-01-04 15-57-14

@matthew-nm
Copy link

Hi! Same issue for me, but I'm running OpenSUSE 42.2 Leap.

I found an .rpm someone had made before, ran the gui, and it recognized my system and even showed under "Devices" on the Prey web app, but it didn't actually function (it would never find my location or send a message). So I uninstalled that version of Prey and installed the node version via npm. Currently, the gui doesn't launch from the console, and the command-line account setup gives me the same error others have had in this thread.

If OpenSUSE could be added to the list of supported distros, that would be great!

@javo
Copy link
Contributor

javo commented Mar 15, 2017

Hi @matthew-nm, we haven't fix this issue yet, for now please follow this instructions and it should be work fine #249 (comment).

@matthew-nm
Copy link

Thanks for the response, @javo!

I followed your directions in thread #249, except my index.js file was located in /usr/local/lib/node_modules/prey/node_modules/linus/index.js.

I was able to run through the command-line account setup (I needed to force it with -f), and it seemed that everything went well. However, my device is still not appearing on the web app.

When I run prey -p I get error: option `-p, --path <path>' argument missing.

And when I run prey -D at first I got

The Prey agent is running. Good job!
It has been live for 0.050 minutes, under process ID 19576.
To trigger actions or retrieve information, log in to your Prey account at https://preyproject.com
For additional configuration options, please run `prey config`.

but subsequent prey -D gave me

  ████████████████ ████████████████ ████████████████ ██            ██
  ██            ██ ██               ██            ██ ██            ██
  ██            ██ ██               ████████████████ ██            ██
  ██            ██ ██               ██               ██            ██
  ████████████████ ██               ████████████████ ████████████████
  ██                                                               ██
  ██                                                 ████████████████

  PREY 1.6.6 spreads its wings!
  Current time: Wed Mar 15 2017 10:11:18 GMT-0700 (PDT)
  Running with PID 19889 as matthew over Node.js v4.6.1 on a x64 linux system (undefined)

     info Wed, 15 Mar 2017 17:11:18 GMT [control-panel] Gathering device data...
 critical Wed, 15 Mar 2017 17:11:18 GMT UNCAUGHT EXCEPTION: Cannot read property 'replace' of undefined
    debug Wed, 15 Mar 2017 17:11:18 GMT TypeError: Cannot read property 'replace' of undefined
    at done (/usr/local/lib/node_modules/prey/node_modules/linus/index.js:54:52)
    at /usr/local/lib/node_modules/prey/node_modules/linus/index.js:63:5
    at /usr/local/lib/node_modules/prey/node_modules/linus/index.js:26:14
    at memorized (/usr/local/lib/node_modules/prey/node_modules/linus/node_modules/memorize/index.js:53:17)
    at get_distro_info (/usr/local/lib/node_modules/prey/node_modules/linus/index.js:24:3)
    at Object.exports.name [as get_os_name] (/usr/local/lib/node_modules/prey/node_modules/linus/index.js:57:3)
    at get_device_data (/usr/local/lib/node_modules/prey/lib/agent/plugins/control-panel/setup.js:51:16)
    at link_device (/usr/local/lib/node_modules/prey/lib/agent/plugins/control-panel/setup.js:13:3)
    at /usr/local/lib/node_modules/prey/lib/agent/plugins/control-panel/setup.js:135:9
    at Object.exports.set (/usr/local/lib/node_modules/prey/lib/agent/plugins/control-panel/api/keys.js:48:9)
     info Wed, 15 Mar 2017 17:11:18 GMT [reports] Gathering specs report.
    debug Wed, 15 Mar 2017 17:11:18 GMT [providers] Fetching processor_info
    debug Wed, 15 Mar 2017 17:11:18 GMT [reports] [4/5] Got processor_info
    debug Wed, 15 Mar 2017 17:11:18 GMT [providers] Fetching firmware_info
    debug Wed, 15 Mar 2017 17:11:18 GMT [providers] Fetching network_interfaces_list
    debug Wed, 15 Mar 2017 17:11:18 GMT [providers] Fetching ram_module_list
    debug Wed, 15 Mar 2017 17:11:18 GMT [providers] Fetching storage_devices_list
    error Wed, 15 Mar 2017 17:11:18 GMT [reports] Unable to get storage_devices_list: TODO!
    debug Wed, 15 Mar 2017 17:11:18 GMT [reports] [3/5] Got storage_devices_list
    debug Wed, 15 Mar 2017 17:11:18 GMT [reports] [2/5] Got firmware_info
    debug Wed, 15 Mar 2017 17:11:18 GMT [reports] [1/5] Got network_interfaces_list
    debug Wed, 15 Mar 2017 17:11:18 GMT [reports] [0/5] Got ram_module_list
     info Wed, 15 Mar 2017 17:11:18 GMT [reports] Report gathered: specs
     info Wed, 15 Mar 2017 17:11:23 GMT Gracefully shutting down. Will self-destruct in 5 secs.
    debug Wed, 15 Mar 2017 17:11:23 GMT Unloading plugins.
    debug Wed, 15 Mar 2017 17:11:23 GMT Stopping actions.
    debug Wed, 15 Mar 2017 17:11:23 GMT Unloading hooks.
     info Wed, 15 Mar 2017 17:11:23 GMT [hooks] Unregistering hooks.
    debug Wed, 15 Mar 2017 17:11:23 GMT Canceling reports.
    debug Wed, 15 Mar 2017 17:11:23 GMT Unwatching triggers.
    debug Wed, 15 Mar 2017 17:11:23 GMT Cleaning up temporary files.
     info Wed, 15 Mar 2017 17:11:28 GMT Time's up, shutdown forced. Have a jolly good day sir.

@javo
Copy link
Contributor

javo commented Mar 15, 2017

Hmmm ok, you have an error when you're running the client, that's why your device isn't appearing.
Try uninstalling the npm version and install prey using the .deb package. After the install is done do what it's says in the thread i gave you.
Let me know how it goes :)

@matthew-nm
Copy link

Well, OpenSUSE uses the Redhat package system and not Debian, so I can't install .deb packages directly. The next best thing to do is install it from source, but I don't know how to do that. Is the source available? If so, I'm sure I can figure it out.

@ricqas
Copy link

ricqas commented Feb 14, 2019

Hello
I get the message os does not exist

Distributor ID: antiX
Release: 17.2.1

Is there anyway to add this?
Does this matter with the api key?

@javo
Copy link
Contributor

javo commented Feb 14, 2019

Hi @ricqas, I made the request to add antiX into our distro list, should be available soon, I'll let you know :)

@ricqas
Copy link

ricqas commented Feb 15, 2019

Hello
Will this work on all antix distros any version? Also were you able to add?

Thanks

@javo
Copy link
Contributor

javo commented Feb 15, 2019

Hi, antix distro is already added, could you try again @ricqas ? Should work with every version

@brokencog
Copy link

Hello, old thread here, but I'm wondering if Slackware could be added to the "accepted" distros. I can manually tweak lsb_release output to "Ubuntu and prey will accept that, but ... that doesn't seem right. Slackware doesn't have lsb_release by default, however the file /etc/slackware-version always exists with OS name and version number.

Anyway, hope this can be accomodated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests