Open pyorot opened 2 weeks ago
Its funny, I've been 'reproducing' this bug for a few days now and pulling out may hair in the process.
I agree, that there should be some indication on the external library, or on the file. Maybe even gray out the options so the user knows whats going on. The silent fail felt very random.
I'm just glad its not me 😄. I am going to try and loosen the permissions on the folder and see if it solves the issue for me.
EDIT: It did.
The bug
This has been discussed several times before, but there is an unintuitive behaviour where if a user edits metadata of an asset in an external library that's mounted as read-only (say by forgetting it's read-only or believing the edit would be stored in the database or generated files) then the edit silently fails.
A simple solution that came up in discussion is to issue a generic asynchronous popup to the client saying "failed to save metadata for \<asset filename>: file system is read-only" or similar (and the log should mention "read-only" too).
The OS that Immich Server is running on
Debian 12
Version of Immich Server
v1.106.3
Version of Immich Mobile App
n/a
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
Additional information
No response