What do I do next to get Lightroom running? I've attached the error reports from both Apple and Adobe to this thread (from both 12.3 and 12.4). I was told by Adobe Support that I don't have full admin priviliges on my main user account, but this is the only user account on the device and has admin access. I tried running v12.3 with the same results. This did not work, although it is the only method of running it that I've found will reliably generate an error report.ĥ. Running Lightroom with superuser priviliges via Terminal. This did work, but I need to be able to run the program on my main admin account to access my synced OneDrive files, as this is where my Lightroom catalogs are located.Ĥ. Running lightroom while signed in as the root user. Resetting Lightroom preferences, both by renaming the preferences file and by pressing and holding option+shift when launching the program.ģ.
The file did not exist at the location specified on other Support Community threads ( /Users//Library/Caches/Adobe/Lightroom/metrics.json)Ģ. On my own, and while working with Adobe support, I have tried the following solutions:ġ. This is a new laptop, and I have never tried to run Lightroom on it until yesterday.
It does not appear in Activity Monitor after this. When I want to start Lightroom I copy the old autentication files over the broken ones and start Lightroom.When opening Lightroom Classic 12.4 on MacOS 13.2.1, I briefly see a splash screen before the program closes. My workaround was to restore the authentication file from backup and make a copy of them. It turned out that after application starts it tries to execute the 32-bit autentication binaries and breaks the authentication files. Since it started once after restore I was curious about why that was and ended up analyzing what changed after first application start. Next time it refused to start so I started using google finding responses that I had to upgrade my Lightroom to a subscription model. It came with Catalina and I restored my backup to it and started Lightroom. I was so lucky that I finally had the opertunity to upgrade my machine to a newer one. So I did find a workaround, it's not pretty but it works.
0 kommentar(er)
