Works fine on Apple Silicon!

[VltKpr]

I just wanted to say thanks for this! I was able to transfer my copy of Lightroom 6.14 from my High Sierra MacBook to my new 2020 Mac Mini with the M1 processor in it that's running Big Sur. It appears to be running quite snappy with Rosetta 2.

[VltKpr]

I guess my praise was a little premature. It appears that upon restarting my Mac Mini, the program just ends up crashing on start. Running your script again makes it launch again but it hangs when you try to quit it again. Oh well, it was worth a shot anyway!

[animaux]

Damn, this sounds so close :)

[krema]

hi, thanks for the feedback!
Freezing on exit is quite common but it has no negative effects and is no cause to concern. The crashing on startup is a problem and shouldn't happen. What do the log files say?

~/Library/Logs/amt3.log
~/Library/Logs/Adobe
/tmp

[VltKpr]

It looks like Lightroom is deleting my license after opening it for the first time on my new Mac. My application.xml file appears to have some mentions of a trial and I am starting to think that it didn't fully activate on my old Mac before I ran your script. I don't have access to the old Mac anymore so I can't test to see if it was actually activated or not. Lightroom does run on the first instance after restoring the files to my new Mac, and running the script to restore the missing files again seems to allow it to run again, only to repeat the cycle over.

[animaux]

I’m eager to try this with my properly activated copy when my M1 arrives. On January 4th 😩.

[animaux]

M1 is there. I can verify the problems. Runs fine at first, crashes on exit, not able to run again, only after resyncing. :( @krema I can send you the amt3.log if you want?

[PaddyPat]

Solution for M1

Goto path:
/Library/Application\ Support/Adobe/SLCache

One .slc file must be write protected!
On my system when you start LR6, some .slc files in this path got changed.
One Vjd*.slc file (on my system - maybe it has another name on your system) permissions must be changed to "read only" only for me , than Lightroom 6 starts every time (close bug till exist)

To easy close Lightroom:
Create a .sh script and rename it to app - than you can move it to your taskbar.

cat CloseAdobeLightroom.app

#!/bin/sh
killall "Adobe Lightroom"

[fingertrouble]

Solution for M1

Goto path: /Library/Application\ Support/Adobe/SLCache

One .slc file must be write protected! On my system when you start LR6, some .slc files in this path got changed. One Vjd*.slc file (on my system - maybe it has another name on your system) permissions must be changed to "read only" only for me , than Lightroom 6 starts every time (close bug till exist)

To easy close Lightroom: Create a .sh script and rename it to app - than you can move it to your taskbar.

cat CloseAdobeLightroom.app

#!/bin/sh killall "Adobe Lightroom"

This worked for me.

Note if you make ALL the .slc files read only (I had cleaned off all the old Adobe stuff so knew it was just LR at that point) then the app won't start and claims it is damaged. But yes if you set read only to the files called Vjd.... in SLCache it works.

I also found that it was deleting the .lic files in SLStore, I did fiddle with making those read only, so that might have helped but I think it was just those few Vdj....files that did it.

Basically the process is for those who want to fix this or this doesn't work for them:

Use the rsync restore.
Run Lightroom
Exit
Run it again - it will fail.
Rsync again, it will only sync the files that have changed - which are JUST those files in SLStore and SLCache. Try making the Vdj... slc files read only in Finder (tried to do it in Terminal, didn't like that) for all users of the file. If not, try the others til the 'install damaged' popup goes away.

Also found something odd - initially it was showing Lightroom 2015 CC when I first reinstalled, but after this fix it was showing the correct LR 6.14.

Also I installed current LR as a trial, and I'm finding some of the menus in LR 6.14 look...a bit different? Jazzier? Not sure what that is...I hope when LR CC 2022 goes bye bye it doesn't nuke 6.14. It's definitely 6.14 though, it says so on all the About and other menus, and still has the issue with the white box in the top right of the photo area!

[Blatman]

Well this looked interesting as I still use LR 6.14 on High Sierra so did a restore of the Lightroom_Backup to an M1 MBP 2021 14" running Monterey 12.6.8

:: application.xml ::

add <Data key="EULADelay">-1</Data>

remove <Data key="NTL_WO_SN"/> (Not To Launch WithOut Serial Number?)

This allowed LR6 to launch again for first time.

Successive launches will fail due to changes in the SLCache and SLStore folders

Essentially if I reinstated the SLCache/SLStore folders from the backup LR would launch OK.

During the first launch the licensing is somehow checked and changes made to the Cache files. There are references to Trial versions etc but I think a genuine registration should add data that supercedes the earlier data but does not remove references to the trial versions. The restore procedure works OK on High Sierra but the later Silicon OS releases may change folder access permissions so upsetting the registration/licence process.

Looking at the amt3.log file it seems that the licence file is detected but the format appears invalid so LR then deletes the file and alters some cache files. The licence file is a binary type so not sure if the CPU type change affects matters here.
On a good High Sierra launch the licence file is found and parsed correctly.

So by reinstating the SLCache/SLStore folders before launching LR would launch every time however I noticed a few things that would not inspire confidence in using it.

Issue 1:

The folder structure on the import feature appeared to be a bit corrupt showing duplications and folders that should be hidden.

Issue 2:

Did a trial import of c. 1500 snaps and it processed them at a glacial pace (at least an hour if not longer!)

Looked so promising but a big disappointment that it wouldn't run on M1 very well. I like using LR 6.14 but not willing to be hostage to a subscription service to get the Classic version.

[fingertrouble]

Issue 1:

The folder structure on the import feature appeared to be a bit corrupt showing duplications and folders that should be hidden.

Issue 2:

Did a trial import of c. 1500 snaps and it processed them at a glacial pace (at least an hour if not longer!)

Looked so promising but a big disappointment that it wouldn't run on M1 very well. I like using LR 6.14 but not willing to be hostage to a subscription service to get the Classic version.

It still kind of works for me on my M1 Pro. I will tell you this DO NOT update to Ventura. I did by accident, and it still works but I get really weird flashes on 6.14, the UI goes odd for a while in Develop or any disk activity, but is fine if you let it do it's weird flashy flashy. But it does slow stuff down.

And no, disabling GPU doesn't help. Anyone have this?

I none of those issues you mention on Monterrey though. Just a few minor visual glitches. It was surprisingly stable and quite quick. I didn't try and import 1500 snaps but I use a small local catalogue then merge to the bigger one, it does that fine.