Photoshop: I have a locked image. Everything about it is locked.

  • 2
  • Question
  • Updated 1 year ago
  • (Edited)
Something I did locked the image. I know this not because there are any lock icons or messages around, I determined it by trying many different tools and discovering that they are all ineffectual in use and greyed out on the menus. If there is some compelling reason for PS to do this, it should explain. Furthermore, since the image looks fine, there really ought to be a way to *UN*lock the image.

So, here's my question:  What can I do?
Photo of bruce.korb

bruce.korb

  • 6 Posts
  • 1 Reply Like
  • irritated

Posted 1 year ago

  • 2
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14049 Posts
  • 1735 Reply Likes
what is the exact message you're getting?
Photo of bruce.korb

bruce.korb

  • 6 Posts
  • 1 Reply Like
Were there a message, I'd have had it in my message. The only indications of any sort of problem is that no selected tool works and menu items that effect change are greyed out. I started over and re-did my work in about an hour, but I still have the .tif that still fails -- even after re-opening. The image is locked. There is no explanation.
Photo of David

David, Official Rep

  • 2701 Posts
  • 361 Reply Likes
Howdy Bruce,

I'm not seeing any problems editing the document you shared with me.  I seem able to change everything I want.  Is this the only file with this problem?  Are you sure this isn't a system rights issue AND that you have enough room on your scratch drive?  If you want to send me another version, I'm game to try that too, but at this point, I'm not seeing a problem.

Thanks,
David
Photo of David

David, Official Rep

  • 2701 Posts
  • 361 Reply Likes
One last thought, Bruce.

To confirm my understanding, the file you sent me is locked for you.  Have you tried rebooting your OS, launching PS, and just opening that open document?  Is it locked then?

I have an idea, but it's just a hunch...
Photo of Bruce

Bruce

  • 13 Posts
  • 0 Reply Likes
Ok, I confess. I "merely" closed and re-opened the TIFF file. I did not close PS and did not reboot until this morning -- when I booted up twice due to some internal (likely OS/X) error.

SO: after a reboot, I can now edit the file -- except I finished already using a fresh start, so I will abandon it.

Another RFE: under the "Help" menu, add an option to cause PS to do some self-diagnosis so next time, ....
Photo of David

David, Official Rep

  • 2701 Posts
  • 361 Reply Likes
Yeah, I'd be willing to bet that you ran out of scratch drive space, particularly given the file's size.  At that point, much like a starving animal, Photoshop probably misbehaved a bit cuz it was starving for memory, but after relaunching the app (or OS in some cases) everything should be reset and you should be golden.
Photo of Bruce

Bruce

  • 13 Posts
  • 0 Reply Likes
Not terribly long ago, but seemingly very far away, I was tasked with fixing every allocation call to handle failures. Either an allocation had pre-allocations and could never fail, or there was a graceful response.  You can safely guess it was not easy.

Anyway, given that I was able to re-stack and re-do the layering without exiting Photoshop, it is not completely clear that that was the issue. But any smoking guns disappeared with the reboot.  I'll never know for sure.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14049 Posts
  • 1735 Reply Likes
What OS are you on? What version of Photoshop are you using?
Photo of Bruce

Bruce

  • 13 Posts
  • 0 Reply Likes
OS/X latest public release (aka "Sierra" or 10.12.4).
PSC 2017.1.0 aka 20170309.r.207 x64
This is now the real account I use.  I had to wait around and wait around and wait around for some wierdo "verification code" to come through.
Photo of John Maguire

John Maguire

  • 397 Posts
  • 83 Reply Likes
Is there any chance the file got marked as read only or write denied by the OS? Just spit-balling it here.

Photo of Bruce

Bruce

  • 13 Posts
  • 0 Reply Likes
Thanks, no cigar:

-rwx------@ 1 bkorb  owner  1432660332 Apr 27 12:46 ph-019-Edit.tif

P.S. I use command line tools and have for 40 years. :)
Anyway, I was happily editing the file and I did something
that triggered no alert and still left the image immutable.

Extended attributes:


$ ls -@l ph-019-Edit.tif

-rwx------@ 1 bkorb  owner  1432660332 Apr 27 12:46 ph-019-Edit.tif

com.apple.FinderInfo         32
(Edited)
Photo of John Maguire

John Maguire

  • 397 Posts
  • 83 Reply Likes
wait a sec. Is the file on a networked drive, "-rwxrwxrwx 1 goflex users 0 Apr 28 11:58 foyer-lw-3.jpg,

If so, copy it to your system drive and try to edit. I read somewhere that PS doesn't play well with networked drives. I have a goflex also.
Photo of Bruce

Bruce

  • 13 Posts
  • 0 Reply Likes
Um, "Wait a sec. [...] I read somewhere"? A) If true, Adobe needs to detect network drives and give warnings in 36 point red letters. In this day and age, NFS/CFS file systems are to be presumed. B) Adobe programmers need to fix it, and C) I started over and merged the images just fine on that NAS device. Now that I have the image merged, I confess to not getting excited about debugging software. I spent my career doing that. I seem to be good at finding Photoshop boundary cases, but I'm retired now. If that 1.4 GB image works for you, then you can presume it was an Adobe-doesn't-get-along-with-NFS problem. Otherwise it is an Adobe-gets-lost-and-won't-tell-anyone-why problem.  Either way, ...
Photo of David

David, Official Rep

  • 2701 Posts
  • 367 Reply Likes
I believe somewhere in the Help files, like Word, Excel, and most other apps, Photoshop "suggests" that you run locally rather than over a network.  It's actually a fairly common "official" limitation.  But I don't think that was the problem.  See my earlier comment...