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

fail to start #1761

Closed
Matthiasc opened this issue Feb 18, 2021 · 3 comments
Closed

fail to start #1761

Matthiasc opened this issue Feb 18, 2021 · 3 comments
Assignees
Labels
need/analysis Needs further analysis before proceeding

Comments

@Matthiasc
Copy link

installing IPFS-Desktop-Setup-0.13.2 successfully and starting the app right after.

Specifications

  • OS: win32
  • IPFS Desktop Version: 0.13.2
  • Electron Version: 9.3.2
  • Chrome Version: 83.0.4103.122

Error

Error: spawn UNKNOWN
    at ChildProcess.spawn (internal/child_process.js:394:11)
    at spawn (child_process.js:549:9)
    at execFile (child_process.js:233:17)
    at module.<computed> (electron/js2c/asar.js:163:31)
    at C:\Users\Matthias\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\ipfs-on-path\index.js:85:5
    at new Promise (<anonymous>)
    at runWindows (C:\Users\Matthias\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\ipfs-on-path\index.js:84:10)
    at run (C:\Users\Matthias\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\ipfs-on-path\index.js:108:12)
    at firstTime (C:\Users\Matthias\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\ipfs-on-path\index.js:79:21)
    at module.exports (C:\Users\Matthias\AppData\Local\Programs\IPFS Desktop\resources\app.asar\src\ipfs-on-path\index.js:56:3)
@welcome
Copy link

welcome bot commented Feb 18, 2021

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@jessicaschilling
Copy link
Contributor

@Matthiasc - suggesting that it may be better to take this issue to the forums at discuss.ipfs.io for more active troubleshooting, as core team members are diverted at the moment and may not be able to troubleshoot quickly. Thank you!

@aschmahmann aschmahmann added the need/analysis Needs further analysis before proceeding label Feb 22, 2021
@lidel
Copy link
Member

lidel commented Feb 23, 2021

I am afraid the only fix here is to find IPFS Desktop/config.json and manually set:

"ipfsOnPath": false,

We will be deprecating this feature (#1768), if you want ipfs on your PATH follow https://docs.ipfs.io/install/command-line/

@lidel lidel closed this as completed Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/analysis Needs further analysis before proceeding
Projects
None yet
Development

No branches or pull requests

4 participants