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

Cant open workspace #8275

Open
2 of 4 tasks
nomeaning25 opened this issue Jan 6, 2025 · 2 comments
Open
2 of 4 tasks

Cant open workspace #8275

nomeaning25 opened this issue Jan 6, 2025 · 2 comments
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer

Comments

@nomeaning25
Copy link

Expected Behavior

When I click on my collection the app should open my colection.

Actual Behavior

When I click on my collection I get an error:

Error: EACCES: permission denied, open '.../snap/insomnia/299/.config/Insomnia/insomnia.WorkspaceMeta.db' at async open (node:internal/fs/promises:639:25) at async writeFile (node:internal/fs/promises:1219:14) at async Persistence.persistNewStateAsync (/snap/insomnia/299/resources/app.asar/node_modules/@seald-io/nedb/lib/persistence.js:168:5) at async Datastore._updateAsync (/snap/insomnia/299/resources/app.asar/node_modules/@seald-io/nedb/lib/datastore.js:1005:5)

If I try to reload the app the same error appeares. I also get the same error if I logout and log in again. I also get the error.
I also get the same error even if I want to use the Skratch pad.

Reproduction Steps

No response

Is there an existing issue for this?

Which sync method do you use?

  • Git sync.
  • Insomnia Cloud sync.
  • Local only

Additional Information

No response

Insomnia Version

10.2.0

What operating system are you using?

Ubuntu

Operating System Version

Ubuntu 24.04.1 LTS

Installation method

snap

Last Known Working Insomnia version

10.2.0

@nomeaning25 nomeaning25 added B-bug Bug: general classification S-unverified Status: Unverified by maintainer labels Jan 6, 2025
@nomeaning25
Copy link
Author

After system restart the issue is resolved... but this kind of issues make me want to switch to a different solution.

@godfrzero
Copy link
Contributor

@notjaywu This seems similar to issues we've seen in the past, let's try to find a permanent solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer
Projects
None yet
Development

No branches or pull requests

2 participants