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

[gui error report] #2229

Closed
funk11 opened this issue Aug 16, 2022 · 2 comments
Closed

[gui error report] #2229

funk11 opened this issue Aug 16, 2022 · 2 comments
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@funk11
Copy link

funk11 commented Aug 16, 2022

Please describe what you were doing when this error happened.

Specifications

  • OS: win32
  • IPFS Desktop Version: 0.16.2
  • Electron Version: 13.1.7
  • Chrome Version: 91.0.4472.124

Error

Error: EPERM: operation not permitted, open 'C:\Users\gstew\.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)
@funk11 funk11 added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Aug 16, 2022
@welcome
Copy link

welcome bot commented Aug 16, 2022

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
Copy link
Member

hacdias commented Sep 1, 2022

Please update to the most recent IPFS Desktop version: https://github.com/ipfs/ipfs-desktop/releases/tag/v0.23.0

This was fixed in #1948

@hacdias hacdias closed this as completed Sep 1, 2022
Repository owner moved this from To do to Done in IPFS-GUI (PL EngRes) Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
No open projects
Archived in project
Development

No branches or pull requests

2 participants