Obsidian Does indicate why it doesn't open a vault

Steps to reproduce

open obsidian. The system will load last folder
open obsidian again because I haven’t noticed it open on another desktop
open my vault

Did you follow the troubleshooting guide? [Y/N]

No. The issue involves opening two normal vaults. The sandbox vault indicates my changes would be lost and therefore two instances can’t exist. Restricted mode changes nothing.

Expected result

Obsidian to open again or indicate correctly why it didn’t open.

Actual result

1st result: Can not reproduce.
cachedCwd = rawMethods.cwd();

Error: ENOENT: no such file or directory, uv_cwd
at process.wrappedCwd [as cwd] (node:internal/bootstrap/switches/does_own_process_state:126:28)
at node:path:1082:24
at Object.resolve (node:path:1096:39)
at resolveMainPath (node:internal/modules/run_main:19:40)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:75:24)
at node:internal/main/run_main_module:23:47 {
errno: -2,
code: ‘ENOENT’,
syscall: ‘uv_cwd’

Node.js v18.14.0

2nd Result:
Popup message:
Failed to open. no permission to access folder. (sic)


OS: Gentoo Linux x86_64
Kernel: 6.1.41-gentoo
WM: Openbox
Installed through emerge and not AppImage.
Version 1.3.7

Additional information

I am assuming you would want to know about this user experience given the high level of polish of this application. It would be completely understandable and reasonable if you if you close this bug report for an unsupported OS that is reporting a nuisance issue.

Moved to help section

Regarding the underlying problem rather than the error message, it sounds like a filesystem problem unrelated to the sequence of vault openings. Is the vault on a network drive or something?

1 Like

I believed I was causing the underlying problem by having the application running and locking the file. I was incorrect about this and I appreciate the note for a double check. I have a read-only mounted folder deeper in the vault. It seems that obsidian needs read and write to open a vault. My testing of folders in the vault was causing more problems than solving them.

I deleted my previous comment about the change as reporting that folder level vault access needs to be read/write is more of a feature than a bug.

Thanks for your help CawlinTeffid

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.