Yesterday and today, when deleting rejected files from my disk, I've received the following error: "an internal error occurred: ?:0: attempt to index a nil value." What's going on? This catalog seems OK, Lightroom CC Classic is working, but this is a new twist. What causes this, and what can I do to fix it? I'd rather not do anything that will destabilize my catalog, it's got 13 years of photos and data for a long term research project on harbor seals. Suggestions please!
I realized that the error will only come up if I deleted rejected photos (ctrl+backspace) while I was viewing/selected a rejected photo in loupe view. No issues while viewing an unflagged/picked image or when in grid view. So if this is a problem that ocurrs when deleting rejected photos then use grid view or make sure you're not viewing a rejected photo when you delete all rejected photos because this will bring up the error.
Copy link to clipboard
Just had same error using Smugmug. Syncing now seems to have fixed the problem.
This happens to me all the time, too. I delete a photo, LR gets 'lost' and doesn't know where it is in the grid anymore and displays this silly message. I feel that all that's needed to resolve this is a line of code that tells LR to simply move to the 'next' photo in the grid. Shouldn't be too difficult, right?
I am no longer able to send email via Lightroom Classic 10. I have no idea how to fix this.
I found the identical issue today with LR 10. Any solution for this so far ?
I've been patiently waiting but have not heard a word about how to fix this.
Maybe they fix it in LR 15 😉
Same problem in my mac when trying to mail photos. Using 10.0 release of lightroom classic. This is new.
Re sending email from LR: LR 10 broke this, and Adobe has acknowledged the bug:
The only known workaround is to roll back to LR 9.4, which could be painful if you've done a lot of work in 10.0 you don't want to lose.
Please add your constructive opinion to the bug report, and be sure to click Like and Follow at the bottom of the first post. That will make it a little more likely that Adobe will prioritize a fix, and you'll be notified when the bug's status changes.
[Use the blue reply button under the first post to ensure replies sort properly.]
I'm having the same problem with "internal error, ? 0:attempt to index field font (a nil value)", error message occurs everytime I try to email photos from Lightroom CC Classic. Previously it worked fine and now, unable to email directly from Lightroom. What gives?
I'm having this same issue, but the error is being thrown before I get to the choice of which client to use... This just started after the lastest drop of Lightroom CC - Release 10 and under DNG Converter 13
oops, had to log in to include a pic:
?:0: attempt to index field 'rootFile' (a nil value)
I am having this same problem on 5/23/2021 when trying to delete photos from my LRC catalog.
Please copy and paste here the first ten lines from the menu command Help > System Info.
I only recently started seeing the same error message, but in a different context from previous posts:
I get this message when using Tethered Capture, but only when I try to use it the second time. The only way I can start another session of tethered capture is to exit Lightroom and restart. Then it works fine, but only if I keep the session active. I am using Lightroom Classic version 10.3, Windows 10, the Fujifilm Tethered Capture plug-in. I have used this plug-in for several years with no hiccups, but recently I have experienced this annoying behavior, requiring me to exit Lightroom and start over if I want to resume tethered capure.
"I am using Lightroom Classic version 10.3, Windows 10, the Fujifilm Tethered Capture plug-in."
The cause of this problem could be a bug introduced in recent versions of LR, or it could be a bug in the plugin that's only recently triggered by recent versions of LR.
For better or worse, I think it's very unlikely Adobe will pay much attention to such problems unless Fujifilm themselves talk with Adobe. So your best bet is to contact Fujifilm support. (I'm speaking as a plugin developer with 11 years of experience with LR.)
Thanks for the reply -- I'll do that. Just to complete the picture, today I discovered that there was an update for the Fujifilm Tether plug-in. I downloaded it, but no change in the behavior reported above. Again, I appreciate your help.
Copy link to clipboard
I have been receiving this same message when trying to export my finished images. I tried many of the fixes listed in these threads. However, in my case, it turned out to be the catalog that had a problem. I was able to export the images by creating a NEW CATALOG, then importing the images from the original catalog into it, to then export it. Hopefully my sharing this will help someone else. Here are the steps.
File > New Catalog > (name it) Create > the new catalog will then open...
File > Import From Another Catalog > (find original catalog) Double Click to open or click Choose > (check box) Import.
Once the images have completed the import, you may export as you normally would.