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

OS X: "Device protected" after install. No setup GUI is launched. Device is not registered (HS:node-no-gui-bug) #53

Closed
ghost opened this issue Dec 10, 2014 · 7 comments
Assignees
Labels

Comments

@ghost
Copy link

ghost commented Dec 10, 2014

sudo /usr/lib/prey/current/bin/prey config gui needs to be launched manually. Currently affecting Prey 1.3.3 on OS X 10.10.

@ghost ghost added the bug label Dec 10, 2014
@ghost ghost assigned tomas Dec 10, 2014
@ghost ghost changed the title OS X: "Device protected" after install. No setup GUI is launched. Device is not registered (HS:node-gui-bug) OS X: "Device protected" after install. No setup GUI is launched. Device is not registered (HS:node-no-gui-bug) Dec 10, 2014
@ghost
Copy link
Author

ghost commented Dec 11, 2014

Two different console logs for the installer, from two different users:

installer-01

installer-02

@tomas
Copy link
Contributor

tomas commented Dec 11, 2014

In both cases the installer failed to launch the GUI?

@ghost
Copy link
Author

ghost commented Dec 11, 2014

Yes. Both cases. Hopefully I'll be posting new console logs from other affected users.

@ghost
Copy link
Author

ghost commented Dec 12, 2014

I don't think that this could be the source of every issue, but what if:

  1. Prey was previously installed.
  2. The device was deleted from the user's Prey account.
  3. Prey wasn't unistalled from the system.
  4. You install Prey.

Should't the installer read the old prey.conf file and keep it? This means that the GUI wouldn't be launched, and the device wouldn't be created on the user's Prey account. These are the exact symptoms here, except for the few computes that didn't have Prey previously installed, according to the affected users.

Also, doesn't uninstalling Prey keep the old prey.conf file?

@ghost
Copy link
Author

ghost commented Dec 16, 2014

This just in! The user had never installed Prey before.

$ sudo rm /etc/prey/prey.conf && /usr/lib/prey/current/lib/conf/gui/mac/PreyConfig.app/Contents/MacOS/prey-config.py
2014-12-16 12:19:06.775 Python[20161:1107] <type 'exceptions.ValueError'>: No closing quotation
2014-12-16 12:19:06.776 Python[20161:1107] (
0 CoreFoundation 0x00007fff8ea3525c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff946cce75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8ea34e09 -[NSException raise] + 9
3 _objc.so 0x000000010ff80626 PyObjCFFI_MakeClosure + 2197
4 libffi.dylib 0x00007fff9329fa1f ffi_closure_unix64_inner + 509
5 libffi.dylib 0x00007fff9329f11e ffi_closure_unix64 + 70
6 AppKit 0x00007fff8c5930de -[NSControl sendAction:to:] + 86
7 AppKit 0x00007fff8c5dfc4d -[NSCell _sendActionFrom:] + 128
8 AppKit 0x00007fff8c5f9655 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 2316
9 AppKit 0x00007fff8c5f8a27 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 487
10 AppKit 0x00007fff8c5f813d -[NSControl mouseDown:] + 706
11 AppKit 0x00007fff8c579a58 -[NSWindow sendEvent:] + 11296
12 AppKit 0x00007fff8c5185d4 -[NSApplication sendEvent:] + 2021
13 AppKit 0x00007fff8c3689f9 -[NSApplication run] + 646
14 libffi.dylib 0x00007fff9329ef9c ffi_call_unix64 + 76
15 ??? 0x00007fd23ecbc810 0x0 + 140540973402128
)

I hope it helps.

@tomas
Copy link
Contributor

tomas commented Dec 29, 2014

This was fixed on the v1.3.4 release.

@tomas tomas closed this as completed Dec 29, 2014
@ghost
Copy link
Author

ghost commented Dec 29, 2014

Thanks for the good news. Affected users were notified 👍

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

No branches or pull requests

1 participant