Adobe Illustrator wont open on Sierra Anybody knows how to fix Adobe Illustrator CC 2014 on Sierra? The app just dont open anymore. I was using it on a clean install of El Capitan, but after Sierra, the app crash right after toolbars appear.

Things that I tried:


Set 755 (read/write permissions) on /Library/Application Support/Adobe, ~/Library/Application Support/Adobe.


Result: App crash.  

Path:                  /Applications/Adobe Illustrator CC 2014/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
Identifier:            com.adobe.illustrator
Version:               18.0.0 (18.0.0)
Code Type:             X86-64 (Native)
...
Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000068
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0x68:
--&gt; 
    __TEXT                 0000000100000000-00000001014ca000 [ 20.8M] r-x/rwx SM=COW  /Applications/Adobe Illustrator CC 2014/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_c.dylib               0x00007fffb20ad6c0 flockfile + 4
1   libsystem_c.dylib               0x00007fffb20af38f fread + 31
2   com.adobe.amtlib                0x0000000107ecd4d9 0x107ea0000 + 185561
3   com.adobe.amtlib                0x0000000107ec210b 0x107ea0000 + 139531
4   com.adobe.amtlib                0x0000000107ea2bf7 AMTPlugPlugRequest + 81
5   com.adobe.PlugPlugOwl           0x000000011da9e2ef int boost::_bi::bind_t&lt;int, int (*)(char*, int), boost::_bi::list2&lt;boost::arg&lt;1&gt;, boost::arg&lt;2&gt; &gt; &gt;::operator()&lt;char*, int&gt;(char*&amp;, int&amp;) + 49
6   com.adobe.PlugPlugOwl           0x000000011da9cf01 boost::detail::function::function_obj_invoker2&lt;boost::_bi::bind_t&lt;int, int (*)(char*, int), boost::_bi::list2&lt;boost::arg&lt;1&gt;, boost::arg&lt;2&gt; &gt; &gt;, int, char*, int&gt;::invoke(boost::detail::function::function_buffer&amp;, char*, int) + 28



Start application with sudo.


Result: App wont open.
Log in Terminal The application with bundle ID com.adobe.illustrator is running setugid().


Reinstall software (Install only run with sudo).


Result: After install, first run with sudo, and App not even open after accepting the license. No logs, no crash.


Create another user (Edit 1).


Result: The app not even bounce on Dock,  


Illustrator CC 2015 Trial, Installer only with sudo. First run with sudo, then crash. Updated to 2015.2.1 again only with sudo. Now there two results (Edit 2).


Result 1: With sudo, The application with bundle ID com.adobe.illustrator is running setugid(), which is not allowed.

Result 2: Without sudo, maybe this is a big clue:

/Applications/Adobe\ Illustrator\ CC\ 2015/Adobe\ Illustrator.app/Contents/MacOS/Adobe\ Illustrator ; exit;
2016-10-10 12:37:18.454 Adobe Illustrator[2481:60401] AdobeCrashReporterInitialize: executionTime = 0.003444 seconds
2016-10-10 12:37:25.209 AdobeIPCBroker[2490:60500] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x1703, name = 'com.adobe.AdobeIPCBroker'
See /usr/include/servers/bootstrap_defs.h for the error codes.
Segmentation fault: 11
logout



Lastest version of Illustrator on CC, install only work with sudo, download ok.


Result: The app not even bounce on Dock.

Maybe it is a lost cause... for now moving to another app.
Was this a clean install of Adobe or an "restore" from a Time Machine backup?  I have personally had issues when going from one issue to the next (Mavericks to Yosemite and Yosemite to El Capitan) and migrating my software instead of clean installing it.  Doing a clean install fixed my issue each time.

So, first thing to do, is uninstall and do a clean installation of Illustrator.

At the time of this writing, Adobe wasn't experiencing any issues with Illustrator.  See macOS Sierra (10.12) compatibility FAQ | Creative Cloud

However, they do provide a link for people to report bugs.  If doing a clean install doesn't solve the problem I would report the problem.