Skip to main content
Inspiring
March 17, 2016

P: Won't start. Ask to change permission of folders, but that doesn't solve.

  • March 17, 2016
  • 54 replies
  • 1930 views

After the Lightroom 2015.5 (march 2016) update, Lightroom doesn't work anymore. Ask to change permission of folders in library manually. I did as told and it still doesn't work...

This topic has been closed for replies.

54 replies

Inspiring
March 21, 2016
After trying to fix this for 2 days i finally found you! I followed your steps and within a minute, if at all, it worked! I can't thank you enough; you're amazing!!!
Inspiring
March 20, 2016
worked for me, thank you!
Inspiring
March 19, 2016
Well - if so, there is a nice little improvement for a future .6 update:
in Preferrences make a button and let people chose to switch it on or off.
That simple.
Adobe Employee
March 19, 2016
Thanks Stefan.

Some Lightroom CC 2015.4 customers (https://feedback.photoshop.com/photoshop_family/topics/lr-6-4-mac-os-x-10-11-3-hangs-freezes-crashes...) were hit with the same underlying permission issue as well. Lightroom CC 2015.4 does not check for user folder permissions at all. As a result, customers could experience crashes, hangs on launch or other mysterious symptoms. The other customers might just get lucky without noticing they still have the underlying folder permission issues. It just did not affect Lightroom.

The difference in CC 2015.5 is that we start to check and detect for these folder permission issues, in an attempt to steer the customer clear of the mine field and also have a chance to address the issue. But as I mentioned above, we could have done better in after thoughts.
Inspiring
March 19, 2016
It worked for me! Can't thank you enough!
Inspiring
March 19, 2016
Hi Simon - it ́s a very specific error. Didn ́t have something like this before - EVER.
And - it was not happening with CC2015.4
So I "guess" it is very likely, there was a change in permission management from .4 to .5 .
Other than that, the software runs nicely as far as I can say.
Next week I will ask a friend of mine who is an OSX programmer and specialized in Databases and networking about this, Maybe he has a good explanation about why a prog can go so berserk on a formerly working file and permission structure.

Regards
Stefan Steib
Adobe Employee
March 19, 2016
I want to thank customers *Stefan Stein here, *Dirk Müller and *Andrei Frolov from the other related thread https://getsatisfaction.com/photoshop_family/topics/lightroom-cc-2015-5-lightroom-6-5-camera-raw-dng-converter-9-5-now-available to help sort through this maze of Mac OS X file permission issues. The root cause of the issue is different for each customer. It is historical and culprits could be Adobe installers, or 3rd party plug-in developers, Mac OS X upgrade (https://support.apple.com/en-us/HT204899) and maybe even user errors at some point.

Lr 6.5 release has just exposed this can of worms and unfortunately it does not offer an escape hatch to ignore it and continue. It should have allowed customers to fix the issue at their own timing. This will be fixed in the next Lightroom update.

However, it is important to address these file permission issues on your system sooner than later. You don't know how these file permission issues will manifest themselves as bugs as you use the products.
Inspiring
March 19, 2016
None of the options described 1-3 worked for me (including the script for terminal) and I felt that setting up a new admin account just to run Lightroom is ridiculous. 

So I uninstalled Lightroom using AppCleaner, rebooted computer, installed Lightroom 6.0, opened it and updated it to 6.5 - it worked just fine for me.

Thanks,
Boris
Inspiring
March 19, 2016
Hi Simon,

I tried everything. NOTHING worked EXCEPT YOUR SCRIPT DID WORK!

You just made my day - THANK YOU SO VERY MUCH!

I can't believe Adobe gave us this bug in the latest update and their solution DOESN'T WORK except creating a new admin on my machine (which I don't want).

Million THX you're the best!

Florin Harrison T.
Adobe Employee
March 19, 2016
@Johannes Thanks for the feedback. I've updated the shell script at the same shared link to require a 'sudo' to run the chown command, in case the circumstance needs it.