Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
4974 Discussions

Vtune 2021.40/50 not launching on Mac 10.15.7

Ceezeh
Beginner
550 Views

Hi,

 

Vtune version 2021.40/50 both do not seem to launch on my mac. Do you have any ideas why? I have attached some messages from the mac console:


default 11:46:35.109265+0100 loginwindow -[PersistentAppsSupport applicationReady:] | App: Intel oneAPI VTune Profiler 2021.5.0, ready, updating active tracking timer
default 11:46:35.148380+0100 tccd -[TCCDAccessIdentity staticCode]: static code for: identifier com.intel.vtune, type: 0: 0x7fad1ae08bf0 at /opt/intel/oneapi/vtune_profiler/2021.5.0/Intel oneAPI VTune Profiler 2021.5.0.app
error 11:46:35.160479+0100 tccd Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for ACC:{ID: com.intel.vtune, PID[1313], auid: 502, euid: 502, binary path: '/opt/intel/oneapi/vtune_profiler/2021.5.0/Intel oneAPI VTune Profiler 2021.5.0.app/Contents/MacOS/vtune-gui'}, REQ:{ID: com.apple.appleeventsd, PID[313], auid: 55, euid: 55, binary path: '/System/Library/CoreServices/appleeventsd'}
default 11:46:35.236980+0100 vtune-gui SetFrontProcess: asn=0x0-0x51051 options=1
default 11:46:35.256747+0100 vtune-gui SetFrontProcess: asn=0x0-0x51051 options=1
default 11:46:35.293016+0100 VTune Helper (GPU) XPC connection invalidated (daemon unloaded or disabled)
default 11:46:35.293049+0100 VTune Helper (GPU) MessageTracer: Falling back to default whitelist
default 11:46:35.293124+0100 VTune Helper (GPU) Can't open default search tree file: Operation not permitted
default 11:46:35.336359+0100 VTune Helper (GPU) GVA info: preferred scaler idx 1
default 11:46:35.348402+0100 VTune Helper (GPU) MessageTracer: Falling back to default whitelist
default 11:46:35.348480+0100 VTune Helper (GPU) Can't open default search tree file: Operation not permitted

0 Kudos
1 Solution
Ceezeh
Beginner
539 Views

I solved by fixing the permission for the chmod u+x /Users/<username>/.intel/ folder to allow non-root read-write access.

View solution in original post

0 Kudos
2 Replies
Ceezeh
Beginner
540 Views

I solved by fixing the permission for the chmod u+x /Users/<username>/.intel/ folder to allow non-root read-write access.

0 Kudos
JananiC_Intel
Moderator
523 Views

Hi,


Thanks for reaching out and glad to know that your issue is resolved. If you need any additional information, please submit a new question as this thread will no longer be monitored.


Regards,

Janani Chandran


0 Kudos
Reply