-
Notifications
You must be signed in to change notification settings - Fork 13
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
BetterDiscord installation fails #5
Comments
This seems to be an issue with Node. Try this. |
What distribution are you using, and how did you install Node? As for cleaning out the shell of BD and getting Discord running again, try |
Also, we may want to look into more checks for failure, as painful as bash may make them. :/ |
We could add individual checks after the node-related commands that seem to fail a lot, or do something with ERR or DEBUG. On second thought, maybe we should just check if |
Issue fixed by uninstalling everything very thoroughly and then reinstalling again using BetterDiscordCTL method, following exact instructions word for word. I'd been trying the main method and then the BetterDiscordCTL method haphazardly, switching to one when the other failed, and I think that must have muddled things up. Lesson, don't mix the two, if one fails then uzninstall BetterDiscrod, Node and NPM completely before trying again with the other. |
We can make a new issue for better error checks. Glad to see it's working for you now! |
* Bunch of bugfixes - Replace `readarray` with `read` for backwards compatibility (#3, #4) - Show a proper error when core extraction fails (#5) - Fix Snap path - Fix killing Discord processes * Set flavor when scanning is skipped Otherwise, uninstall will fail for PTB/Canary * Improve Snap dir detection
I can install BetterDiscordCTL, and it seems to have installed, at least there it is in usr/local/bin, but when I put in "betterdiscordctl install -s /usr/share", I get this:
When I try to load Discord, it doesn't load, unless it's just updating really slowly - it's been hanging at the updater stage (the one that says "Readying the felines..." :-D ) for half an hour now. Any advice, please?
The text was updated successfully, but these errors were encountered: