-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
[webOS 2.x, non-rooted] An error occured during installation: Unable to exec luna-send-pub: Error: Failed to call getIDs #110
Comments
Even with version 0.5.1 I get same error (on same webos version). |
i have to this error with version 0.5.1 |
Same problem. :( |
I'm not sure what you mean. There's no "root option" to set in Homebrew Channel; you need to root the TV and run the |
Fixed by f77b075, which will be included in the next version. |
I read it with sadness. :( |
When is the new version expected to be released? |
Before making a release I would like to finish support for adding certificates to the Node.js store on webOS <5. But a new Homebrew Channel release, by itself, will not help you root your TV anyway. What are you saying is "solvable (and simple)"? Finding vulnerabilities and writing exploits for them that are usable by the general public? If you're feeling impatient, you can root webOS 1 TVs by modifying the NVM right now. |
I meant that even an average person can solve it with a few clicks under Windows. In other words: I hope it will be user-friendly, and I hope it won't require any special knowledge to complete the task. Thanks for the link, it seems very complicated at first, I'll wait for your new version, trusting that I will be able to solve it. |
Hello.
I cannot install any application from it. Every try ends with:
"An error occured during installation: Unable to exec luna-send-pub: Error: Failed to call getIDs"
What can I do?
I have WebOS 2.0, No root.
I installed Homebrew Channel from Webosapp.club/online
Its version is 0.4.0
And I cannot update it, because of the same error as above.
What can I do?
The text was updated successfully, but these errors were encountered: