Lightroom CC 2015.5/Lightroom 6.5 | Camera Raw/DNG Converter 9.5 now available

  • 4
  • Announcement
  • Updated 2 years ago
  • (Edited)
We are happy to announce the release of Lightroom 6.5/CC 2015.5, Adobe Camera Raw/DNG Converter 9.5.

To update Lightroom to 6.5, choose Help > Updates

To update Lightroom to CC 2015.5, Click "Update" in the Creative Cloud desktop application next to Lightroom. 

Lightroom update details (blog)

What’s New 



To update Camera Raw, either choose Help > Updates within a Camera Raw compatible application, or by clicking "Update" from within the Creative Cloud desktop application. 

Camera Raw update details

Camera support policy for CS6

Cameras supported by Camera Raw
Photo of Pete Green

Pete Green, Customer Advocate

  • 700 Posts
  • 126 Reply Likes
  • Thankful

Posted 2 years ago

  • 4
Photo of Csaba Pálos

Csaba Pálos

  • 1 Post
  • 0 Reply Likes
Cannot update Lightroom 6.4 to 6.5.
Help > Updates does not work.
The latest update listed on the download page is 6.4.
Photo of Dirk Müller

Dirk Müller

  • 5 Posts
  • 0 Reply Likes
After updating suddenly LR complains about wrong folder permissions. It worked before (2015.4) and I have not touched permissions. OS X 10.11.3. The help page https://helpx.adobe.com/lightroom/kb/lightroom-cc-2015-4-lightroom-6-4-crashes-on-launch.html seems to be 2015.4 specific where the issue did not appear. Checked permissions again, they're ok so the information on that page don't help. Please advise. :-) Thanks!
Photo of Dirk Müller

Dirk Müller

  • 5 Posts
  • 0 Reply Likes
I just deleted LR and installed it again, didn't help. LR runs under my user id.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
When you follow the KB doc to correct the permission issue manually, please make sure that you follow Apple’s help doc https://support.apple.com/kb/PH21997?locale=en_US&viewlocale=en_US to make sure you correct the permission on the folders AND all their enclosed items folders. 
From Apple help:



Apply permissions to all items in a folder or a disk
  1. Select a folder or a disk, then choose File > Get Info.

  2. Click the lock icon  to unlock it, then enter an administrator name and password. 

  3. Click the Action pop-up menu , then choose “Apply to enclosed items.”

(Edited)
Photo of Dirk Müller

Dirk Müller

  • 5 Posts
  • 0 Reply Likes
Everything in ~/Library belongs to me, all directories are user rwx and all other relevant files are at least user rw:
Dirks-MBP:~ dirk$ find ~/Library -type d ! -perm -u=rwx -exec ls -ald {} \;
Dirks-MBP:~ dirk$ find ~/Library ! -type d ! -perm -u=rw -exec ls -ald {} \;
-r--------  1 dirk  staff  0 21 Mai  2014 /Users/dirk/Library/Keychains/.fl0D1D1BA9
-r--r--r--  1 dirk  staff  0 20 Mai  2014 /Users/dirk/Library/Keychains/.fl62323D2F
-r--r--r--  1 dirk  staff  0 26 Mai  2015 /Users/dirk/Library/Keychains/.fl8D2DFA3E
Dirks-MBP:~ dirk$ find ~/Library ! -user dirk -exec ls -ald "{}" \;
Dirks-MBP:~ dirk$
Photo of Rainer Menes

Rainer Menes

  • 6 Posts
  • 0 Reply Likes
Have the same issue. LR CC 2015.5 does start up on OS X 10.11.3 after updating. I check all permissions used hard drive repair to fix any potential issue but nothing helped. Then remove LR CC 2015.5 and reinstalled it but it hang in the middle but I was able to start the original LR CC 2015 all came just fine. After a short time I was asked to upgrade but again LR CC 2015.5 is not coming up!
Photo of Rainer Menes

Rainer Menes

  • 6 Posts
  • 0 Reply Likes
The upgrade for PS CC 2015.5 just works fine by the way. Please look into LR CC 2015.5
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Please follow https://helpx.adobe.com/lightroom/kb/lightroom-cc-2015-4-lightroom-6-4-crashes-on-launch.html to make sure you have read/write permissions to the folders and all its subfolders. If the automatic repair does not fix it for you. Please follow Apple’s help doc https://support.apple.com/kb/PH21997?locale=en_US&viewlocale=en_US to make sure you correct the permission on the folders AND all their enclosed items. From Apple help doc:

Apply permissions to all items in a folder or a disk
  1. Select a folder or a disk, then choose File > Get Info.

  2. Click the lock icon  to unlock it, then enter an administrator name and password. 

  3. Click the Action pop-up menu , then choose “Apply to enclosed items.”

(Edited)
Photo of Rainer Menes

Rainer Menes

  • 6 Posts
  • 0 Reply Likes
I already check all my permissions! see above. It doesn't help to just repeat this stuff.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1366 Posts
  • 403 Reply Likes
Did you apply the permission to all enclosed items?
Photo of Rainer Menes

Rainer Menes

  • 6 Posts
  • 0 Reply Likes
Check all folder in this link again, no way to get it work
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1366 Posts
  • 403 Reply Likes
Can you try the nuclear option below to back up and manually remove the relevant Adobe folders? 
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
If you did that and it still does not work, I would suggest making a backup of the user folders mentioned in https://helpx.adobe.com/lightroom/kb/lightroom-cc-2015-4-lightroom-6-4-crashes-on-launch.html and try to delete them. You should have read/write permission to your own Adobe folders.
(Edited)
Photo of Dirk Müller

Dirk Müller

  • 5 Posts
  • 0 Reply Likes
Solved it, was a nasty ACL set on ~/Library/Preferences/Adobe/Lightroom/5.4/logs . Looks like it was a faulty recovery from a time machine backup in 2014. ACL present was
0: group:everyone deny add_file,delete,add_subdirectory,delete_child,writeattr,writeextattr,chown
The directory itself was empty but it had a + in ls -l. chmod -N fixed it.
Do you perform such checks now in 2015.5? I haven't touched anything there for years. If so a more reasonable information for the user would be great.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
@Dirk Oh cool. Thanks. Lightroom could have been more informative in logging the folder(s) that have such permission issues.

Yes, this folder permission check is new in Lr 6.5. What happens was that Lightroom customers reported mysterious crash on launch or other issues after upgrading to Lr 6.4 and Mac OS X 10.11 (El Capitan). We traced the issue to the folder permission issues on customer's own user folder. In order to surface such issues and bring customers' attention of such possible issues, Lightroom implemented this folder permission check in Lr 6.5. Good to hear in your case, there is indeed an issue and you are able to find it and fix it.
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
The dialog has a "Learn More..." button that will take you to this KB doc https://helpx.adobe.com/lightroom/kb/lightroom-cc-2015-4-lightroom-6-4-crashes-on-launch.html.

Have you tried any of the solution to see if it helps correct the permission issue in your user folders?
Photo of Michael Willems

Michael Willems

  • 4 Posts
  • 0 Reply Likes
Simon,

The tip did not work, since it did not explain that I should also change permissions for subfolders. See http://www.speedlighter.ca/2016/03/23/huge-adobe-bug/ for my version of the fix. 

I call it a bug because it stops the app from starting, and it's a mission critical app!
 
Photo of Michael Willems

Michael Willems

  • 4 Posts
  • 0 Reply Likes
I think the issue is: you KNEW this would cause many people's app to not start - while it is THE mission critical app. A CAUTION note might have been well advised, I'd think. Why add a feature that will cause people to not be able to start? How about a warning instead? Plus: the permissions thing was caused by the installer, no doubt. I have never messed with usernames or rights!
Photo of Michael Willems

Michael Willems

  • 4 Posts
  • 0 Reply Likes
...in other words: can I ever trust an Adobe upgrade again? Or will future upgrades ALSO contain features that will stop the app from starting if there's something not to your liking? Again: this IS my business, it's how I make a living. If I cannot run LR, I am out of business, it's as simple as that.

Also: What's the CC thing? I use LR as a standalone app: I do not want the online thing, where I depend on you to give me permission every time to launch my business... I don't mind paying what it's worth, which is a lot, I love Lightroom: but I cannot have a situation where I depend on Adobe to decide whether I can launch. Which means your database has to be good, I need to be online regularly, etc etc...
Photo of Andrei Frolov

Andrei Frolov

  • 10 Posts
  • 1 Reply Like
...can I ever trust an Adobe upgrade again?

Short answer is no. Not specifically directed at Adobe as such. You generally should not screw around with production copy of mission critical software. Install a second copy, test the new branch thoroughly, only then migrate. Of course, that should have been done on Adobe side as well. It looks to me as this permission checking patch did not receive much testing (if at all) in house before being shipped out. Welcome to the brave new CC world, where you are the primary code tester...

Now watch how long it takes Adobe to ship the patched version out, and weep. It is a one-line code change to change error to warning, but that's not the way it is going to roll, I predict.
Photo of Rainer Menes

Rainer Menes

  • 6 Posts
  • 0 Reply Likes
For me I can't find anything except going to all the n folder one by one. Can Adobe please release a version which maybe tells in the alert box which path it is worrying. For a normal customer it is impossible to so. Thx!
Photo of Dirk Müller

Dirk Müller

  • 5 Posts
  • 0 Reply Likes
@Rainer in a terminal you could try
chmod -RN "~/Library/Preferences/Adobe"
If that doesn't work try the other folders "~/Library/Application Support/Adobe" and "~/Library/Caches/Adobe" as well.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1088 Posts
  • 257 Reply Likes
I've summarized the known workarounds (Thanks the tip from Dirk) in this thread

https://feedback.photoshop.com/photoshop_family/topics/lightroom-2015-5-wont-start-ask-to-change-per...
Photo of Rainer Menes

Rainer Menes

  • 6 Posts
  • 0 Reply Likes
I found my issue but seriously which normal customer can do this? Some where deep im my path a lightroom module was installed which made all folders owned by root so everyone like me had only r access. sudo chown -R user dir fixed it.

I would recommend Adobe to do the following: Provide a script which finds out what file or directory is the issue. Idea would be like this ls -leR path | sed ... (correct regular expression to filter only those files and directories which need a fix and write them to a file) > logfile. Next give recommendations what to do.

Even better report the files during startup. If Lightroom is able to say something is wrong hey it should be able to at least tell what is wrong.
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1088 Posts
  • 257 Reply Likes
That is a good idea. We're going to add extra logging to the console summarizing the problematic folders, and provide an option to skip the checking if the customer chose to do so (potential problem is still there, but at least customer can take their chances :-).
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1088 Posts
  • 257 Reply Likes
Photo of Stan Burman

Stan Burman

  • 21 Posts
  • 4 Reply Likes
I continue to have difficulty with downloading and installing updates for Photoshop CC 2015 and Lightroom CC 2015. Attempted downloads and installs have repeatedly "failed." Past attempts at Adobe tech support have been unsatisfactory. I have resorted to getting updates from ProDesign Tools.

And the latest update patch for LR CC 2015.5 failed to install on my MacBook Pro running OS X 10.11.3.

I was able to uninstall and reinstall Lightroom CC 2015 via the Creative Cloud panel. The separately downloaded LR CC 2015.5 patch then installed correctly.

I appreciate the Adobe folks helping us out, but at some point I would appreciate it if Photoshop and Lightroom applications and updates could just be normally downloaded and installed by us mere mortals. Creative Cloud has really been a nightmare.

End of rant.
Photo of Andrei Frolov

Andrei Frolov

  • 10 Posts
  • 1 Reply Like
Have the same problem. Checked all Adobe directories, everything owned by me, read and write permissions set, all ACLs recursively cleared. Still Lightroom 6.5 bums out. You guys have a bug in your brand-spanking new "permission check" code. Do you even test before you ship out? Had not have a single update which installed without problems since I don't remember when.

Don't act retarded and pretend it did not happen, go and fix it already. Jeez...
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Yes. It will check on the symbolic link as well.

Lr checks for r/w permission only on the specific set of folders:

~/Library/Application Support/Adobe/ and the first level subdirectories beneath it.
~/Library/Application Support/Adobe/Lightroom/ and the first level subdirectories beneath it.
~/Library/Caches/Adobe/.
~/Library/Caches/Adobe/Lightroom and the r/w permission for the first level subdirectories beneath it.
~/Library/Preferences/Adobe/.
~/Library/Preferences/Adobe/Lightroom/ and the r/w permission for the first level subdirectories beneath it.

It is possible one of the check failed for unknown reasons.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Photo of Andrei Frolov

Andrei Frolov

  • 10 Posts
  • 1 Reply Like
OK, re-implementing your check script in Swift:

#!/usr/bin/env swift

import Foundation

let fm = NSFileManager.defaultManager()

let home = "/Users/frolov/"

let dirs = [
	"Library/Application Support/Adobe/",
	"Library/Application Support/Adobe/Lightroom/",
	"Library/Caches/Adobe/",
	"Library/Caches/Adobe/Lightroom/",
	"Library/Preferences/Adobe/",
	"Library/Preferences/Adobe/Lightroom/"
]

for d in dirs {
	let path = home + d
	
	for subpath in try fm.subpathsOfDirectoryAtPath(path) {
		let f = path + subpath
		
		guard (fm.fileExistsAtPath(f)) else { continue }
		
		if let type = try fm.attributesOfItemAtPath(f)[NSFileType] {
			guard (type as! String == NSFileTypeDirectory) else { continue }
			
			print("Checking \(f) for write access... ", fm.isWritableFileAtPath(f))
		}
	}
}
and running it

./test.swift | grep false
I get a single fail point:

Checking /Users/frolov/Library/Application Support/Adobe/Lightroom/Scripts for write access...  false
On closer inspection, this is owned by root, and does not have global write access. chown'ing to my userid, Lightroom now runs. This means a previous version of Lightroom  installer (file is dated Jan 13 16:43) created this at elevated privileges, and did not chown properly. So the bug is found - not in the checker code, but in the installer instead.
Photo of Andrei Frolov

Andrei Frolov

  • 10 Posts
  • 1 Reply Like
TL;DR: Lightroom installer circa 2016 Jan 13 fucks up ownership of one of the directories it creates (~/Library/Application Support/Adobe/Lightroom/Scripts), and when Lightroom CC 2015.5/6.5 gets around to check it it fails catastrophically. chown to your user id to solve the problem.
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Wow. You're a genius! Nice catch. I missed that when checking your PERMISSION dump earlier (I guess grep -v frolov ./PERMISSIONS did not quite work as I would have hoped.) 

I don't know what happened to the ownership ~/Library/Application Support/Adobe/Lightroom/Scripts. Why it is 'root' in your case, but under the correct uid in my installation. I'll check with our installer team to see if they can make any sense of it.

Glad this resolve for you. Thank you for your patience and persistence.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
@Andrei Went back to your PERMISSION dump, there are a few other folder/file entries that have the 'root' as the owner. Might want to correct those as well.


10816224        8 lrwxr-xr-x    1 root             staff                  53 Sep  9  2015 /Users/frolov/Library/Preferences/Adobe/Adobe Media Encoder/8.0 -> /Users/frolov/Documents/Adobe/Adobe Media Encoder/8.0

10816229        0 drwxrwxrwx    3 root             staff                 102 Sep  9  2015 /Users/frolov/Library/Preferences/Adobe/Common/AME/8.0

10816230        8 lrwxr-xr-x    1 root             staff                  61 Sep  9  2015 /Users/frolov/Library/Preferences/Adobe/Common/AME/8.0/Presets -> /Users/frolov/Documents/Adobe/Adobe Media Encoder/8.0/Presets

43792226       32 -rw-rw-rw-    1 root             staff               15251 Mar 18 11:14 /Users/frolov/Library/Application Support/Adobe/AAMUpdater/1.0/CSUTracker.xml

40854974        8 -rwxr-xr-x    1 root             staff                 329 Feb 25 14:34 /Users/frolov/Library/Application Support/Adobe/Lightroom/External Editor Presets/photoFxLab.lrtemplate

27366563       16 -rwxr-xr-x    1 root             staff                4471 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/ExportServiceProvider.lua

27366564        8 -rwxr-xr-x    1 root             staff                1886 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/Info.lua

27366565       56 -rwxr-xr-x    1 root             staff               27564 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/LightroomPlugin_mac

27366566        8 -rwxr-xr-x    1 root             staff                  87 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/PluginDisable.lua

27366567        8 -rwxr-xr-x    1 root             staff                  87 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/PluginEnable.lua

27366568        8 -rwxr-xr-x    1 root             staff                2005 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/PluginInit.lua

27366569        0 drwxr-xr-x    4 root             staff                 136 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/Presets

27366570        8 -rwxr-xr-x    1 root             staff                1426 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/Presets/JPG.lrtemplate

27366571        8 -rwxr-xr-x    1 root             staff                1505 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/Presets/TIFF16.lrtemplate

27366572        8 -rwxr-xr-x    1 root             staff                 216 Dec  1 05:36 /Users/frolov/Library/Application Support/Adobe/Lightroom/Modules/AutopanoGiga42.lrplugin/TranslatedStrings_fr.txt

33611855        0 drwxr-xr-x    2 root             staff                  68 Jan 13 16:43 /Users/frolov/Library/Application Support/Adobe/Lightroom/Scripts

Photo of Stan Burman

Stan Burman

  • 21 Posts
  • 4 Reply Likes
I rest my case.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Hi,

I wrote a shell script that automates the restoration of ownership, read/write permission and the removing of ACL from the set of Adobe user folders and its subfolders. I've shared the zipped shell script at my Creative Cloud sync folder http://adobe.ly/22tjZX8 . Here is how you will use the script:

1. Download the zip from the above shared link. Unzip it by select and double-clicking the zip file using the mouse. There will appear a shell script file named "LightroomCorrectPermission.sh" sitting next to the zip file that you have just downloaded, which typically is located at /Users/your login user name/Downloads/LightroomCorrectPermission.zip.

2. Type "Terminal" in the Spotlight search box and launch Mac OSX's Terminal app

3. From the Finder, drag-n-drop the uncompressed shell script file "LightroomCorrectPermission.sh" at step 1 onto the Terminal window. You will typically see the following in the Terminal window, press Enter to run the shell script:

/Users/your login user name/Downloads/LightroomCorrectPermission.sh

When prompted, enter your Mac OS X login password (assume it is an account with admin privilege). If everything works well, you should be able to launch Lightroom successfully.

Hope this helps.

Simon
(Edited)
Photo of Léo Li

Léo Li

  • 1 Post
  • 0 Reply Likes
I run this script but still can't lanch Lightroom, this is the result of script.

$ sudo ./LightroomCorrectPermission.sh
=== Sat Mar 19 18:13:36 CET 2016
----------------------------------
Process folder: /Users/AJ/Library/Preferences/Adobe/
Restore owner: sudo chown -R root /Users/AJ/Library/Preferences/Adobe/
Restore read/write permission: chmod -RL +rwX /Users/AJ/Library/Preferences/Adobe/
Remove ACL: chmod -RN /Users/AJ/Library/Preferences/Adobe/
----------------------------------
Process folder: /Users/AJ/Library/Caches/Adobe/
Restore owner: sudo chown -R root /Users/AJ/Library/Caches/Adobe/
Restore read/write permission: chmod -RL +rwX /Users/AJ/Library/Caches/Adobe/
Remove ACL: chmod -RN /Users/AJ/Library/Caches/Adobe/
----------------------------------
Process folder: /Users/AJ/Library/Application Support/Adobe/
Restore owner: sudo chown -R root /Users/AJ/Library/Application Support/Adobe/
Restore read/write permission: chmod -RL +rwX /Users/AJ/Library/Application Support/Adobe/
Remove ACL: chmod -RN /Users/AJ/Library/Application Support/Adobe/
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
No need to specify the 'sudo' at the command line. 

$ ./LightroomCorrectPermission.sh

would do since the script would prompt for password if needed.

So there was not hint of errors when running the script.

Are you able to follow Andrei's steps above to dump out the PERMISSIONS, XATTRS, ACLS and share them somewhere online for us to see?

If you're tech savvy enough, Andrei's swift program could also pin-point the problematic folder.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Photo of Joe Boxer

Joe Boxer

  • 17 Posts
  • 1 Reply Like
(Windows) Lens data is not written to the catalog upon import with version 6.5. I had to rollback to 6.4 with Camera Raw 9.4 and re-import my images.  Posts by other users confirm the problem in 6.5/9.5
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
@Joe This might help https://helpx.adobe.com/lightroom/kb/lens-metadata-hidden-on-some-cameras-in-lightroom-6-5.html. You should be able to make the lens metadata available again in the next Lr update. Stay tuned.
Photo of Matt Horv

Matt Horv

  • 1 Post
  • 0 Reply Likes
Dear Simon
After several tries it looks like your trick helped out! ...is that the future that after one month of having the problem Adobe is "unable" to fix that problem?!? I'm quite astonished about that! Errors can happen, BUT is it that difficult to fix it?!? ...It seem not, otherwise, S. Chen couldn't do it... Once again THANK YOU A LOT Mr. Chen... and only Thank you...