"Internal error occurred"

[edrudolph]

Lightroom Version Number

12.2.1

Operating System

1. macOS 12 Monterey

When you get this error message a few times...
_________

An internal error has occurred.
?:0: attempt to index a nil value

________

...what does it indicate?

 

[Woodbutcher]

I got that a few times after my last import and cull. It wasn’t happy about me trying to edit a photo right after I had deleted rejected photos. I had to move to another image and try again to get it to let me edit. New error with 12.2.1 maybe? I’m on the same os version as you also.

 

[johnrellis]

What particular operations were you doing when the error appeared?

"attempt to index a nil value" is a generic programming error that can arise in many different situations.

 

[edrudolph]

Deleting a file

 

[johnrellis]

That error is often caused by the presence of the Logioptions plugin, which gets silently installed when you install Logitech's utilities for pointing devices. Do File > Plug-in Manager, scan the list of plugins for Logioptions, and if present, select it, and click Disable in the Status panel on the right. Restart LR.

 

[Woodbutcher]

Thanks John, that's probably my problem. I just got a new mouse. Hopefully that fixes the original posters problem too. I'll go remove that plug-in cuz I doubt it really did much for me.

 

[edrudolph]

Thanks from me too, John. Although I don't have that plug-in. I'm attaching a screenshot of plug-in manager, should you know of any other culprits.

 

[Woodbutcher]

Well, I had the logioptions in Photoshop, but didn't see it in Lightroom Classic. I did see something in the install about it so I'm going to dig more.

 

[Woodbutcher]

I'm still getting the error and haven't found the Logitech plugin for Lightroom within LR plug in manager. I did get rid of the PS one though. I thought about uninstalling the Logitech Options+ and see if that solves it.

 

[johnrellis]

If there's no Logioptions plugin in LR's File > Plug-in Manager, then that's not causing the error. You could try temporarily disabling all the installed LR plugins and restarting LR, to see if another one might be causing the error.

 

[Woodbutcher]

I wish I could roll back to LR 12.2, but looks like I have to go back to 12.1. It started after 12.2.1 got installed also, but I also install the new mouse at the same time.

I might just rip out all the Logi software and start again. Kind of unhappy the new mouse uses their Bolt dongle instead of the Unifying dongle my other two mice use.

 

[Woodbutcher]

I wish I could roll back to LR 12.2, but looks like I have to go back to 12.1. It started after 12.2.1 got installed also, but I also install the new mouse at the same time.

I might just rip out all the Logi software and start again. Kind of unhappy the new mouse uses their Bolt dongle instead of the Unifying dongle my other two mice use.

Okay, curmudgeon mode kicked in. I just uninstalled the new logitech software so only the old stuff is there. Then I ordered a new mouse that is the same model as the old one that is dying instead of using the new model that needs the new dongle. Hopefully that works.