Skip to content

IPFS failing to start on linux #1249

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

Closed
Lazerbeak12345 opened this issue Nov 15, 2019 · 8 comments
Closed

IPFS failing to start on linux #1249

Lazerbeak12345 opened this issue Nov 15, 2019 · 8 comments

Comments

@Lazerbeak12345
Copy link

When I compile from source on the master branch, the app opens to a blank screen. I just tested commit ba2c88b but I recall ones as far back as around v0.9 ish had this issue as well.

I'm aware of issue #1244, but upon further inspection, I don't believe that this is the cause for the issue I have found.

Here's a screenshot containing all error messages in the debugger tool:

Screenshot_20191115_132946

My build environment is Fedora 31, npm 6.12.1 (removed node_modules dir before npm i and it still failed). Runtime is the same, running KDE Plasma 5.16.5.

Please tell me if you need any more info, and great work so far on the project!

@Lazerbeak12345
Copy link
Author

Oh, I would like to note that it does, in fact still start the ipfs daemon

@Lazerbeak12345
Copy link
Author

Oops. Closed it. Still broken.

@hacdias
Copy link
Member

hacdias commented Nov 17, 2019

Hey @Lazerbeak12345! Could you try running:

npm run clean:webui && npm run build:webui

please?

It seems to be something related to the Web UI. If that does not solve the problem, I will try on a VM as soon as I can!

@Lazerbeak12345
Copy link
Author

Simply running that and then clicking "status" on the menu didn't work. I'll update you after a re-build.

@Lazerbeak12345
Copy link
Author

Oh, and it was the exact same error, just so you are aware. (And I didn't do a git pull either)

@Lazerbeak12345
Copy link
Author

Great news! After running that command earlier, followed by running rm -r node_modules && npm install && npm run build && npm run start it worked!

@Lazerbeak12345
Copy link
Author

I personally feel like this issue is resolved, but I'll leave it up to you to close it @hacdias

@hacdias hacdias closed this as completed Nov 19, 2019
@hacdias
Copy link
Member

hacdias commented Nov 19, 2019

Thanks!

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

2 participants