Copy link to clipboard
Copied
Lightroom Classic ver. 12.2.1 does not open on my Mac mini M2 Pro - It was working today but would not sync all my photos (I experience this issue virtually every time I return from photo shoots) from Lightroom CC. When it wouldn't sync, I closed the application and then tried launching it again. It went through the motions of opening but did not complete it. I tried a couple of times and then deleted the app, turned the computer off and then back on and the reloaded it. Lightroom Classic still doens't launch. Does any one have a fix for this iss
Copy link to clipboard
Copied
I called Apple Tech support today and explained the issue. He had me go the Activity Monitor. Then under CPU I found Lightroom Classis was running, but not responding. I clicked on it and then chose the "Force Quit" option. I then chose "Disc" and looked for "Lightroom Classic" there but it wasn't. If it had been I would have clicked on it and "Force Quit" it there too. I then shut down the Activity Monitor. Then successfully launched Lightroom Classic.
Note, this is just a work around. The issue is not fixed but this gets around it. Hopefully Adobe is monitoring this chat and will take a look at what's the issue with LRC 12.2.1. I also need them to figure out why LRC doesn't sync with the cloud.
Copy link to clipboard
Copied
I'm having a similar problem. The Lightroom splash screen appears and then the Lightroom application stops responding. On another thread, I saw a link to this page: https://helpx.adobe.com/lightroom-classic/kb/lightroom-not-launching-after-splash-screen.html
On the page, it says to update to the lastest Mac OS and also try renaming the SLCache and SLStore files. I updated my OS, but that didn't solve the problem. Now I want to try the second solution, but I can't find those SL... files in the location stated on that page (System Library/Application Support/Adobe). Does anyone know where to find those files in Mac OS 13.3.1?
Copy link to clipboard
Copied
It may be that you're experiencing the same issue as described in below linked thread. Please check whether the solution provided in the pinned post near top of the thread helps.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now