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

Windows: EPERM %userprofile%\.ipfs-desktop\IPFS_PATH #1943

Closed
miyamotomusashi79 opened this issue Dec 28, 2021 · 1 comment · Fixed by #1948
Closed

Windows: EPERM %userprofile%\.ipfs-desktop\IPFS_PATH #1943

miyamotomusashi79 opened this issue Dec 28, 2021 · 1 comment · Fixed by #1948
Labels

Comments

@miyamotomusashi79
Copy link

Please describe what you were doing when this error happened.

Specifications

  • OS: win32
  • IPFS Desktop Version: 0.18.1
  • Electron Version: 13.6.3
  • Chrome Version: 91.0.4472.164

Error

Error: EPERM: operation not permitted, open 'C:\Users\tmpri\.ipfs-desktop\IPFS_PATH'
    at Object.openSync (fs.js:476:3)
    at Object.func [as openSync] (electron/js2c/asar_bundle.js:5:1846)
    at Object.writeFileSync (fs.js:1467:35)
    at Object.outputFileSync (C:\Program Files\IPFS Desktop\resources\app.asar\node_modules\fs-extra\lib\output\index.js:31:15)
    at writeIpfsPath (C:\Program Files\IPFS Desktop\resources\app.asar\src\daemon\index.js:130:6)
    at startIpfs (C:\Program Files\IPFS Desktop\resources\app.asar\src\daemon\index.js:50:7)
    at module.exports (C:\Program Files\IPFS Desktop\resources\app.asar\src\daemon\index.js:116:9)
    at run (C:\Program Files\IPFS Desktop\resources\app.asar\src\index.js:74:11)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
@miyamotomusashi79 miyamotomusashi79 added the need/triage Needs initial labeling and prioritization label Dec 28, 2021
@welcome
Copy link

welcome bot commented Dec 28, 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.

@hacdias hacdias changed the title [gui error report] Windows: EPERM %userprofile%\.ipfs-desktop\IPFS_PATH Jan 7, 2022
@hacdias hacdias added the area/windows Windows label Jan 7, 2022
@hacdias hacdias removed the need/triage Needs initial labeling and prioritization label Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants