I'm experiencing a similar problem when I run IDL from the command line after upgrading to Mac OS 12 Monterey. I get the same error when I query the screen size from the graphics device:

> DEVICE,GET_SCREEN_SIZE=s
Error: Unresolved inheritance operation

The strange thing is that I don't get the error when I use IDL's native development editor.

I assumed it was an issue with XQuartz, but after installing several versions, I still got the same error. I decided to see if anything odd was reading out onto the Mac console log and found the following at the time of the error:

idl MacOS error: -67061
idl MacOS error: -67061
idl Entering exit handler.
idl Exiting exit handler.

After a ton of searching, I found that MacOS error: -67061 is a security exception under the following description: "invalid signature (code or signature have been modified)." The problem seems to originate from Apple's codesigning framework for developers. Somehow, it seems that Monterey has blocked command line IDL from accessing information from the graphics device through this framework. I tried several actions to sidestep this security block: granted IDL, the terminal, and XQuartz full-disk access, allowed apps downloaded form anywhere to run, and allowed the terminal to locally run code that doesn't meet the system's security policy. All of those actions failed to resolve the error. I guess I'll just use the development editor for now, although it is really cumbersome for what I need to do.

Anybody have any further insight into what could be going on?

We are aware of the issue impacting IDL graphics on Mac OS 12 Monterey. IDL Command Line cannot create graphics due to a security change Apple made in the latest update, but IDLDE should work fine in most cases.

We have not fully tested this but it does appear to be security related and disabling System Integrity Protection (SIP) on Mac OS may resolve the issue. We can't recommend that, however, so do so at your own risk.

Alternatively, we have tested older versions of IDL and they render graphics from Command Line fine. As a temporary work-around for those in need of IDL Command Line graphic, revert to using an IDL version 8.7.2 or older.

Thanks for the reply, Ben. It's reassuring to see L3Harris staff respond on these forum pages. FWIW, I ran command line IDL (v. 8.8.0) after disabling SIP and the same error popped up. The only thing that I've found that gets rid of the error is booting into safe mode. I'll stick to using IDLDE for now until there's a fix.

No problem Chad. There actually is a work-around for this issue now. You can more about it in this Help Article: https://www.l3harrisgeospatial.com/Support/Self-Help-Tools/Help-Articles/Help-Articles-Detail/ArtMID/10220/ArticleID/24127/ENVI-56-and-IDL-88-are-not-compatible-with-MacOS-12-Monterey-but-here%e2%80%99s-a-work-around

Hopefully a future release of IDL will resolve this issue.

Hi, Ben. The recommended workaround worked perfectly. Thanks a ton!

[quote]
Hopefully a future release of IDL will resolve this issue.
[/quote]
New Macs are now released with Monterey = no OS choice.
You wrote "Hopefully" at the begin of your last sentence. Let me start my next one with "seriously".
Seriously, how is it possible that IDL crashes with every version of macOS?
Do you really believe that I'll be moving to Windows or Linux workstations just because of Harris? or do you think there are more chances that I will be porting my codes to another software/language?
Let me give Harris one last advice : "think twice".

IDL 8.8.2 now includes support for Mac OS Monterey out of the box and XQuartz 2.8.x. The mentioned work-around provided in a prior reply is no longer needed.

I have been using IDL 8.8.2 on a new MacBook Pro running Monterey 12.5.1, but last night mistakenly 'upgraded' to 12.6 and now IDL won't start.

I exclusively use the IDL command line interface (never IDLDE) within XQuartz 2.8.2. Now when I try to start it the IDL command line window briefly flashes up and then disappears, leaving XQuartz just with a terminal window.

What can I try?

My problem turned out to be a licensing issue, related to which MAC Address was used. After a few false leads, it was solved in quick time by Ben Castellani, for which many thanks.

Thanks for the update, Ben. Glad we were able to help with the issue.