Skip to main content
Inspiring
September 21, 2023
Question

lightroom permissions on Mac OS not fixing issues (opening or using it at all)

  • September 21, 2023
  • 3 replies
  • 9411 views

first I'm on an M1 Macbook pro 64bg ram, OS 13.0.1 Ventura,

   I havne't used lightroom in a while (since I had an older computer) but installed them both and the "regular" one works ok, I just don't know it very well. But Classic just always gives me a prompt that permissions aren't set right and it can't operate without that. Yes I did already give permissions to both in the settings and then I even went into library and gave permissions to a ton of files there (user>application support>Adobe>lightroom,  something like those as all the tutorials and 'fixes' say to do, I went and gave permissionss to SO many of those, and still doesn't work. It literally tells me where it doesn't have permissions in the lightroom prompt when I open it and I can go to that folder and see that it has read/write permission so it's basically wrong/lying about it. anyone have any idea what this could mean? I really l wanted to use lightroom again and not do 10 tutorials before I edit some pics in the stupid "cloud" version or whatever that is. 

This topic has been closed for replies.

3 replies

JohanElzenga
Community Expert
Community Expert
September 22, 2023

Please post a screenshot of the dialog you are getting. There are different permissions problems, so we need to know exactly what Lightroom is telling you. Lack of 'full disk access' usually does not give an error dialog, so that is probably not the one.

 

-- Johan W. Elzenga
Inspiring
September 29, 2023

Here is a screen of the prompt. I've deleted some plugins and things, still broken every time. Idk what else to do. pretty annoying.

Participant
August 31, 2024

I got it! I found this YouTube clip that talks you through running an Adobe Script. Although i did everything above manually this script sorted it. Everything you need is in the details of the post. Thanks for the help anyway 🙂

https://www.youtube.com/watch?v=LPysUb1TNHk


Thank you, gents

 

I also run into this problem on Lightroom CC, did all above and still pop up shows up. Sadly, this is a real pain and takes me right away from the buggy software. Classic seems to work fine. 

 

It seems like a terrible idea that we're expected to be IT specialists when using photo editing software. Currently I'm using Lightroom at home on two different devices, but also we buy around 100 licenses for the design office we run.

 

Script did nothing new that wasn't done manually. I also changed the "import" folder and still the same.  

Inspiring
September 22, 2023

Well I didn't write out every single step like that but I thought paraphrasing was enough... I did all of that right off, it literally tells you to and I said I did it above. It did not work, which doesn't make sense to me either, I'm not new to giving programs permissions. But then the prompts even send you to an Adobe page that instructs you to go further and give permissions to like ALL the folders Adobe accesses in the library manually which is very weird advice but I even did that and still it thinks it can't write to them. 
and yes I did restart, re-open, and look it up alll over the place. No change. Pretty soon I'm going to start going through my computer and deleting extensions and plugins I don't use but it feels stupid that it should need that much poking into the library just to work (if it does work eventually). 

GoldingD
Legend
September 21, 2023

Reading your post, I am not sure if you accomplished the following:

 

"Go to MacOS 'System Settings - Security & Privacy' and add Lightroom Classic to "Full Disk Access". Click on the lock icon to unlock the settings (not needed in Ventura), then click on the plus icon to add Lightroom Classic if it isn't already listed. If it is listed, then just enable the checkbox (or the switch in Ventura).

 

See also:

Quick Tips: How to give Full Disk Access to Lightroom Classic on macOS

"

That from a reply (on a different posting) , re-ly byJohan W. Elzenga