-
Notifications
You must be signed in to change notification settings - Fork 859
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
Snap on Linux: EACCES: permission denied (..) .config/IPFS Desktop/config.json #1906
Comments
Sounds like a bug caused by Snap isolation (installing executable in different slots/dirs) breaking your setup. @2br-2b some questions and things to try:
lmk if any of this helped. |
I was using both because I wanted to use the CLI for IPFS in addition to IPFS Desktop. I wanted to do some bulk commands, plus I wanted to try it out. I had assumed they would store their data in the same place (so I could use IPFS Daemon to add files to IPFS Desktop), but when IPFS Daemon said it hadn't been initialized, I realized they didn't share storage, so having no further use for IPFS Daemon, I removed it. Uninstalling and reinstalling did the trick! It's now up and running again! As a note to anyone in the future, this will remove all pinned objects from IPFS! |
Thank you. Seems that Snap package isolates each install in the own sandbox, severely limiting its capabilities. If someone familiar with Snap intricacies has any suggestions how to solve this, it would be highly appreciated. Our current config for generating |
I requested safelisting ipfs-desktop snap to use When we get 👍 there I will flip ipfs-desktop/electron-builder.yml Line 67 in 3b13847
|
I had IPFS desktop running in my taskbar. I told it to show the status, and the app crashed. Now, it just says "IPFS has errored" and won't connect to the network.
Before the crash, I had the IPFS and IPFS Desktop snaps installed. I removed the IPFS snap and this happened soon after. I re-installed IPFS, but that hasn't fixed the problem
Specifications
Error
The text was updated successfully, but these errors were encountered: