Capture One unlocks locked image files

Thomas Kyhn

• March 12, 2024 12:10
• Edited

In order to prevent accidental renaming of image files from within Capture One, I've locked all the image files referenced in Capture One. So far this has worked, but apparently Capture One is now able to unlock locked files. I'm not sure what version brought this change, but I've only noticed it with the latest version (16.3.6.6).

I've previously made a request for an option to prevent files from being renamed from within Capture One: Option to prevent files from being renamed.

Locking image files using macOS's Terminal has been the only workaround I knew of (for details see this post).

0

• 

  Thomas Kyhn

  • March 11, 2024 13:40
  • Edited

  

  I contacted support about this, and it's reproducible, but the company has "chosen not to prioritize resources into a fix at this point in time" – i.e. they've introduced a very inconvenient bug and aren't going to waste resources fixing it.

  Any suggestions for an alternative workaround?

  1
• 

  Marcin Mrzygłocki

  • March 14, 2024 14:33
  • Edited

  

  Maybe take permissions away? Lock, chmod and chown using the same script pattern.

  Edit: I don't know if "locking" is somehow related to "setting immutable flag", but you may look the other one up. Speaking as a Linux user, so there is a risk this feature won't be available to you.

  Edit 2: Google tells me that

  chattr +i

  is equivalent to the following on Mac

  chflags schg

  So you should pull permissions out and show who is the boss...

  1
• 

  Thomas Kyhn

  • March 14, 2024 14:40

  

  Marcin Mrzygłocki

  Thanks for the suggestion. I'll give that a try and see if it works.

  1
• 

  Thomas Kyhn

  • March 14, 2024 15:19
  • Edited

  

  With "sudo" it works:

  sudo chflags schg

  I just tried with one file so far. When I try to rename it in Capture One, I get this:

  

  Thanks for your help!

  1

Please sign in to leave a comment.